[gentoo-user] Re: Transferring an existing install to new disk
Neil Bothwick [EMAIL PROTECTED] writes: On Wed, 12 Nov 2008 09:51:12 -0600, Harry Putnam wrote: So boot your existing Gentoo setup as usual, then follow the handbook to install on the new disk. You do not have to boot from a live CD to install Gentoo, and suitable working Linux environment will do the job, and an existing Gentoo installation is more than suitable. There still seems to be some misunderstanding. I want to build up a fresh install somewhere besides my existing desktop OS (gentoo). Leave the existing setup alone for now. Which is what a chroot install does. Get the fresh install up to speed so it is a fresh and new approximation of my desktop OS. Ditto. And finally overwrite the desktop OS with the newly built one. Overwrite? Where does the new disk come into it then? New as in new to the built up install. Perhaps a better choice would have been `different disk' It sounds like what you are describing is just a new install using an exiting gentoo os instead of install disk. But the result would be a new install with nothing setup... on the desktop which is not what I want. Obviously, you would set everything up, but it would be made easier by the fact you are running on the target machine, and everything is in place. There's no copying entire systems over, just change the bootloader config when it's ready. Ok, I see where your going here remove the notion of `new' disk. I don't have room for a new disk on the target machine, hence the idea of overwriting. But just talking about this much seems to indicate I'd be better off braving up and trying to clean up my existing install. Note a different thread where I've started on that mission: Subject: How to fix a hefty (emerge) blocking problem To be posted shortly
[gentoo-user] Re: How to fix a hefty (emerge) blocking problem
Dan Wallis [EMAIL PROTECTED] writes: The blocks regarding sys-fs/e2fsprogs, sys-libs/e2fsprogs-libs, sys-libs/ss and sys-libs/com_err were discussed recently on this list. Basically you need to: emerge -f e2fsprogs e2fsprogs-libs emerge -C com_err ss e2fsprogs emerge -1 e2fsprogs I'm not sure about the others, but fixing these should get you closer to an up-to-date system. :) That did clean those up... thanks
[gentoo-user] Re: How to fix a hefty (emerge) blocking problem
Volker Armin Hemmann [EMAIL PROTECTED] writes: [...] Many thanks for the other useful info I've snipped [blocks b ] x11-drivers/xf86-video-nsc (x11-drivers/xf86-video-nsc is blocking x11-base/xorg-server-1.5.2) [blocks b ] x11-drivers/xf86-video-vga (x11-drivers/xf86-video-vga is blocking x11-base/xorg-server-1.5.2) [blocks b ] x11-drivers/xf86-video-imstt (x11-drivers/xf86-video-imstt is blocking x11-base/xorg-server-1.5.2) [blocks b ] x11-drivers/xf86-video-cyrix and you need all the videodrivers? I am sure not. So remove them and set VIDEO_CARDS in makec.conf. A light just went off over my head. For mnths, maybe yrs... I've wondered why so many x11 drivers would get installed. OK, but a quick google on `site:gentoo.org VIDEO_CARDS' didn't turn up a way to determine what card is on the machine. At least not a recognizable hit I can see is about that. I'm pretty sure I can get that info without opening the cover but I'm drawing blanks about how.
[gentoo-user] Re: How to fix a hefty (emerge) blocking problem
Dirk Heinrichs [EMAIL PROTECTED] writes: [...] thanks for the other useful info I've snipped 4) update world with the ignore blocks option turned on (don't know which that is, since I use paludis). a quick grep of man emerge and man portage on `ignore' and on `block' didn't turn up such an option. I am updated to latest portage (sys-apps/portage-2.2_rc14)
[gentoo-user] Re: How to fix a hefty (emerge) blocking problem
Dirk Heinrichs [EMAIL PROTECTED] writes: Am Mittwoch, 12. November 2008 20:11:33 schrieb Harry Putnam: a quick grep of man emerge and man portage on `ignore' and on `block' didn't turn up such an option. As I said, I use paludis. I was only told that emerge also has this option, just last week (or was it the week before?) on this list. Sorry, didn't mean to jam you about it... I posted the grep info hoping someone else would insert some info about it... thanks again.
[gentoo-user] Re: How to fix a hefty (emerge) blocking problem
Harry Putnam [EMAIL PROTECTED] writes: and you need all the videodrivers? I am sure not. So remove them and set VIDEO_CARDS in makec.conf. A light just went off over my head. For mnths, maybe yrs... I've wondered why so many x11 drivers would get installed. OK, but a quick google on `site:gentoo.org VIDEO_CARDS' didn't turn up a way to determine what card is on the machine. At least not a recognizable hit I can see is about that. I'm pretty sure I can get that info without opening the cover but I'm drawing blanks about how. Never mind. lspci is my friend
[gentoo-user] Re: How to fix a hefty (emerge) blocking problem
Andrey Falko [EMAIL PROTECTED] writes: lspci should show you what video card you have. Look for VGA or something like that. For example on my system: Thanks... I didn't see your post in time and posted a never mind after banging away with google and unearthing that info.
[gentoo-user] Re: How to fix a hefty (emerge) blocking problem
Dirk Heinrichs [EMAIL PROTECTED] writes: From the output you gave, I would suggest that you 1) update portage to the latest (evantually keyword masked) version. This should be able to ignore blocks. 2) Adjust your VIDEO_CARDS, I don't think you have that many cards plugged into your machine. 3) There seem to be blocks between monolithic and splitted kde/qt (kde*-meta) ebuilds. Decide which ones to use and remove the others. qt you need to eventually update separatedly, i.e. emerge qt. 4) update world with the ignore blocks option turned on (don't know which that is, since I use paludis). 5) emerge --depclean (-p) to remove the cruft. What if I ran the --depclean before updating world. Would that help me get rid of some junk before updating it with `world'?
[gentoo-user] Is equery depends still viable
With recent changes in portage in the last few mnths, is equery in general and `equery depends' in particular still reliable?
[gentoo-user] Re: How to fix a hefty (emerge) blocking problem
Volker Armin Hemmann [EMAIL PROTECTED] writes: Just install the latest portage. It has a block breaking function. Then upgrade e2fsprogs like described a few douzend times on this ml and in the forums. Remove all the acient video drivers you don't need anyway. After that, most blocks should be gone. Got that part fixed what about this: From emerge -vuDNpt system [...] [nomerge ] x11-base/xorg-server-1.5.2 [1.4.2] [nomerge ] x11-libs/libpciaccess-0.10.5 USE=-debug -minimal [0] [blocks b ]x11-base/xorg-server-1.5 (x11-base/xorg-server-1.5 is blocking x11-libs/libpciaccess-0.10.5) [ebuild U ] x11-base/xorg-server-1.5.2 [1.4.2] [ebuild N] x11-libs/libpciaccess-0.10.5 USE=-debug [...] I may have trimmed that down too much .. there was a very long line of stuff after the xorg-server entries. I tried installed emerge -v x11-base/xorg-server and x11-libs/libpciaccess separately by themselves without the -uDN part but that fails too. Not too easy to see how to get around this.
[gentoo-user] Re: How to fix a hefty (emerge) blocking problem
Volker Armin Hemmann [EMAIL PROTECTED] writes: Just install the latest portage. It has a block breaking function. Then upgrade e2fsprogs like described a few douzend times on this ml and in the forums. Remove all the acient video drivers you don't need anyway. After that, most blocks should be gone. Thanks again, and it appears to be working with at least `system' at this moment. After cleaning up the x11 drivers, and emerge -C 7-8 things I really don't need anymore. Even with a blocker in there, the emerge is running along just like you said it would nice. Hopefully the world part may be as easy too. I was really reluctant to take too this mess but with yours, Andreys', Dirks', Marks' and Dans' input it appears I may get this done by tomorrow. All and all, much easier than my first thought of building up a fresh gentoo install somewhere else and using that to overwrite my current install.
[gentoo-user] Re: Is equery depends still viable
Alan McKinnon [EMAIL PROTECTED] writes: On Wednesday 12 November 2008 22:04:52 Harry Putnam wrote: With recent changes in portage in the last few mnths, is equery in general and `equery depends' in particular still reliable? I use it fairly often still, but do notice I get a lot of null output. So I no longer trust it fully. At least it doesn't give false positives - what's in the putput really is a valid depend. Do you know off hand if there are any alternatives?
[gentoo-user] Re: Is equery depends still viable
Daniel Pielmeier [EMAIL PROTECTED] writes: With recent changes in portage in the last few mnths, is equery in general and `equery depends' in particular still reliable? I use it fairly often still, but do notice I get a lot of null output. So I no longer trust it fully. At least it doesn't give false positives - what's in the putput really is a valid depend. Do you know off hand if there are any alternatives? emerge -pv --depclean atom I realize cryptic answers are the ultimate in cleverness and show massive sophistication but how is this used to show dependencies to some specific package. Maybe a little more detail would keep my little pea brain from smoking under the load ;)
[gentoo-user] Re: Is equery depends still viable
Iain Buchanan [EMAIL PROTECTED] writes: Do you know off hand if there are any alternatives? dep from app-portage/udept just got recommended to me, but I don't know it's trustworthiness either. Looks promising .. thanks
[gentoo-user] tools currently available for update of etc files after updates
I remember discussion of one or more fairly new tools designed to ease the update of etc files following updates. Can anyone say what tools are currently available.
[gentoo-user] stumpwm users .. need help with failed emerge
Attempting to install stumpwm-cvs I run into an emerge failure with on of the dependencies; dev-lisp/cmucl. Below is a snippet from the end of the emerge of dev-lisp/cmucl-l-19d_p2. Can anyone see what might be the problem? [...] i686-pc-linux-gnu-gcc -O2 -march=i686 -pipe -rdynamic -Wstric -g -DGENCGC -DLINKAGE_TABLE -D__NO_CTYPE -I. -I../../src/lisp nclude -DGENCGC -DLINKAGE_TABLE -c -o lisp.o ../../src/lisp/ cc1: note: obsolete option -I- used, please use -iquote inste In file included from /usr/include/sys/syscall.h:25, from ../../src/lisp/Linux-os.h:24, from ../../src/lisp/os.h:41, from ../../src/lisp/lisp.c:23: /usr/include/asm/unistd.h:2:25: error: unistd_32.h: No such f ../../src/lisp/lisp.c: In function 'sigint_handler': ../../src/lisp/lisp.c:45: warning: unused variable 'code' ../../src/lisp/lisp.c: In function 'default_cmucllib': ../../src/lisp/lisp.c:182: warning: assignment discards quali target type ../../src/lisp/lisp.c: In function 'main': ../../src/lisp/lisp.c:417: warning: implicit declaration of f ../../src/lisp/lisp.c:512: warning: implicit declaration of f ections' gmake: *** [lisp.o] Error 1 src/tools/load-world.sh: line 17: build-2/lisp/lisp: No such Failed to build build-2! * * ERROR: dev-lisp/cmucl-19d_p2 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2116: Called die * The specific snippet of code: * src/tools/build.sh -C -o bin/lisp -core lib/cmuc tch -noinit -nositeinit || die * The die message: * (no error message)
[gentoo-user] Re: tools currently available for update of etc files after updates
Lots of good input... thanks. I did try `cfg-update' but I thought it was really slow. Ditto for etc-update which I tried some time ago. What made me ask about this was that I was beginning to think my home made perl script was too slow and wondered if there was something a little more sophisticated and fast. Mostly because I'm used to using it I suppose, but the homely little script seems much faster and convenient to me. Here is what it does: 1) finds the new config files when fed a directory 2) presents them to the user like this: -- 8 -- 8 -- 8 -- [...] snipped other built in explanatory dialog Incoming /etc/._cfg_wgetrc Shall we install it as described; overwriting the existing one? Anything but y will rename the new conf listed above to /etc/START_STOP/NOUSE._cfg_wgetrc-111508_165416 for reference **Take a look at the diffs before deciding if you need to** diff /etc/._cfg_wgetrc /etc/wgetrc [y/n] -- 8 -- 8 -- 8 -- So the program itself does no work on comparing and simply presents a ready made diff command to be used in a separate terminal. 3) if you say `y' then the old config is overwritten, but first backed up like this: STOP-USE_whois.conf-111508_104703 (= my own file dating system) [date +%m%d%y_%H%M%S] (Of course the date is arrived at a little differently in perl) And the incoming new config is also backed up like: START-USE._cfg_whois.conf-111508_104703 The backups all go into a directory `START_STOP' created by the program in whatever directory the config is in. [ so I do end up with that directory sprinkled around in a few places ] If you say `n' the new config is dated and stored like: NOUSE._cfg_syslog.conf_010107_202225 4) There is also a routine for when there is no old config. This script is probably as poorly written as humanly possible since I'm far from a perl programmer, and it is not sophisticated at all. I wrote it quite a good while back and revised it a little a few times. So I've used it quite a lot, and so far it hasn't eaten `/' or leveled all /etc configs I find that the majority of new configs are either the `*.example' variety or else a diff shows the changed lines are all commented in both old or new, so a simple yes and move on. A three pane merge in xxdiff like cfg-update does by default, seems really clunky and somewhat overkill. Not to mention painfully slow. With configs that need intervention, I'm usually able to get it done with a simple diff and some hand work carried out in a different xterm or if in text mode I'll be using `screen' and switch to a different terminal to do the hand work, or even break out emacs and use its `ediff' tools on the two files. The perl script will have made backups of both for the advent of mistakes. Others here probably have vastly more complicated config files than me, but with this little perl script I'm usually able to blaze thru 15-20 new configs in very short order. I may have to do something by hand with 2-3 and occasionally I'll skip a complicated one and deal with it after disposing all the easy ones. I'm too embarrassed to post the script, but if someone really wants to try it I will make it available. Be advised though that I haven't paid much attention to security or other dangers...
[gentoo-user] excess x11 drivers
I posted some output in anther thread concerning update world (Subject: How to fix a hefty (emerge) blocking problem) Someone noticed I had too many x11 drivers installed and suggested I set the /etc/make.conf VIDEO_CARDS variable (which I never have set before) I figured out I have an nvidia card so set VIDEO_CARDS=nv Now with my emerge -vuDN @system @world complete I'm unable to start X. (More on that later in a separate thread) But a little peek with eix -Ic |grep x11-drivers I still see a hefty mess of them: [I] x11-drivers/xf86-input-evdev ([EMAIL PROTECTED]/13/08): Generic Linux input driver [I] x11-drivers/xf86-input-keyboard ([EMAIL PROTECTED]/12/08): Keyboard input driver [I] x11-drivers/xf86-input-mouse ([EMAIL PROTECTED]/29/08): X.Org driver for mouse input devices [I] x11-drivers/xf86-video-apm ([EMAIL PROTECTED]/29/08): Alliance ProMotion video driver [I] x11-drivers/xf86-video-ark ([EMAIL PROTECTED]/12/08): X.Org driver for ark cards [I] x11-drivers/xf86-video-chips ([EMAIL PROTECTED]/12/08): Chips and Technologies video driver [I] x11-drivers/xf86-video-cirrus ([EMAIL PROTECTED]/12/08): Cirrus Logic video driver [I] x11-drivers/xf86-video-dummy ([EMAIL PROTECTED]/12/08): X.Org driver for dummy cards [I] x11-drivers/xf86-video-fbdev ([EMAIL PROTECTED]/12/08): video driver for framebuffer device [I] x11-drivers/xf86-video-glint ([EMAIL PROTECTED]/12/08): GLINT/Permedia video driver [I] x11-drivers/xf86-video-i740 ([EMAIL PROTECTED]/12/08): Intel i740 video driver [I] x11-drivers/xf86-video-mach64 ([EMAIL PROTECTED]/12/08): ATI Mach64 video driver [I] x11-drivers/xf86-video-mga ([EMAIL PROTECTED]/12/08): Matrox video driver [I] x11-drivers/xf86-video-neomagic ([EMAIL PROTECTED]/12/08): Neomagic video driver [I] x11-drivers/xf86-video-nv ([EMAIL PROTECTED]/13/08): Nvidia video driver [I] x11-drivers/xf86-video-rendition ([EMAIL PROTECTED]/12/08): Rendition video driver [I] x11-drivers/xf86-video-s3 ([EMAIL PROTECTED]/12/08): X.Org driver for s3 cards [I] x11-drivers/xf86-video-s3virge ([EMAIL PROTECTED]/12/08): S3 ViRGE video driver [I] x11-drivers/xf86-video-savage ([EMAIL PROTECTED]/12/08): S3 Savage video driver [I] x11-drivers/xf86-video-siliconmotion ([EMAIL PROTECTED]/12/08): Silicon Motion video driver [I] x11-drivers/xf86-video-tdfx ([EMAIL PROTECTED]/29/08): 3Dfx video driver [U] x11-drivers/xf86-video-tga ([EMAIL PROTECTED]/29/08 - (~)1.2.0): X.Org driver for tga cards [I] x11-drivers/xf86-video-trident ([EMAIL PROTECTED]/12/08): Trident video driver [I] x11-drivers/xf86-video-tseng ([EMAIL PROTECTED]/12/08): Tseng Labs video driver [I] x11-drivers/xf86-video-v4l ([EMAIL PROTECTED]/12/08): video4linux driver [I] x11-drivers/xf86-video-vesa ([EMAIL PROTECTED]/12/08): Generic VESA video driver [I] x11-drivers/xf86-video-voodoo ([EMAIL PROTECTED]/12/08): Voodoo video driver Whats all that for? Checking dependancies on a few I see: dep -l x11-drivers/xf86-video-voodoo: ! x11-base/xorg-x11-6.9 on all I checked. What can this mean?
[gentoo-user] Re: tools currently available for update of etc files after updates
Dirk Heinrichs [EMAIL PROTECTED] writes: Am Sonntag, 16. November 2008 00:05:56 schrieb Harry Putnam: I did try `cfg-update' but I thought it was really slow. Slow? For me it's blazingly fast. Just to install it requires 3 pkgs to be installed: Just to install, it wants three packages unless I USE=-kde (in my case). And even then it still cries about xxdiff. Looking at the other possible editors in /etc/cfg-update.conf... I don't have a single one of them installed... so still more install is required. Using xxdiff is pretty clunky and slow I thought. I would not describe it as blazingly fast. It may be possible to customize to the point where its faster but it would take some doing. Or maybe just by experience in using the tool it would get handier and faster I've not encountered a single conf file where a 3 screen merge was required to get it right. But as I mentioned, my conf files are probably way less complicated than a power users.
[gentoo-user] Re: tools currently available for update of etc files after updates
Dirk Heinrichs [EMAIL PROTECTED] writes: Or maybe just by experience in using the tool it would get handier and faster Just doing the automatic stuff, where no user intervention is involved _is_ blazingly fast. How fast you are in running the diff/merge tool of _your_ choice is, well, up to you. Maybe, but as you know it defaults to xxdiff. That of course is not to say it cannot be changed but by default the merge tool is slow and clunky. Using xxdiff is pretty clunky and slow I thought. I would not describe it as blazingly fast. You were not talking about xxdiff, you wrote that cfg-update was slow. You seem to imply that cfg-update is independent of a diff tool. It does not appear to be able to merge anything on its own. So to speak of cfg-update minus a diff tool as fast/slow seems a little off the mark. I suspect you are a much more accomplished user than I am so I'll defer to your judgement... I'm curious about the backup setup. Have you had occasion to go back into the database to pull out an old config? And if so I wondered if that part worked to your liking? It might allow me to quit putting all my configs under cvs control. That can get to be a bit of a hassle at times..
[gentoo-user] Re: stumpwm users .. need help with failed emerge
[EMAIL PROTECTED] (Johám-Luís Miguéns Vila) writes: Harry Putnam [EMAIL PROTECTED] writes: Attempting to install stumpwm-cvs I run into an emerge failure with on of the dependencies; dev-lisp/cmucl. Below is a snippet from the end of the emerge of dev-lisp/cmucl-l-19d_p2. Can anyone see what might be the problem? [...] Hi. First of all, It's not encouraged to use stumpwm-cvs ebuild as it's obsolete [1]. Its probably another bug that that fact is not included in the portage desc statement. And regarding cmucl build error, there's a bug report on b.g.o. with a patch that seems to fix it [2]. I've downloaded that but not used it yet. But I seem to recall that when you change an ebuild, you can't just install it then ... but have to create a new ebuild or some such? Emacs, n.: A slow-moving parody of a text editor. - This message may be digitally signed: GPG KeyID:0x9D2FD6C8 || FNMT SSL cert Damn! Of course, signature statements are not shared by poster... :( Gack, you were almost caught in print disparaging the `One True Editor'
[gentoo-user] Re: excess x11 drivers
Jorge Peixoto de Morais Neto [EMAIL PROTECTED] writes: I am not only concerned about the problem reported in this thread; I also want to give opinion on his larger update a very outdated system task. Just for the record... I seem to have gotten things under control and did set VIDEO_CARDS=nvidia. I ran into a problem somewhere in the compile of the x11 drivers that brought up where some file (I didn't keep the name) was not available in the most recent kernel sources. Rather than keep pounding away, I backed off to uname -r 2.6.25-gentoo-r9 I didn't test any of the releases in between, since I was pretty sure something in the ...25 series would work since my last kernel (prior to updating to ...27* was ..25-r6. Those sources appear to supply everthing needed. I also discovered that none of the kernel based NVIDIA modules were necessary. And finally as advised here in another thread recently I ran --depclean after successful update @system @world and many of those x11-drivers were dumped. Now I get a clean slate there: $ eix -Ic |grep x11-driver [I] x11-drivers/nvidia-drivers [...] [I] x11-drivers/xf86-input-evdev[...] [I] x11-drivers/xf86-input-keyboard [...] [I] x11-drivers/xf86-input-mouse[...] And X works fine. I don't tax a video card much in my usage of linux. It's my main desktop but my semi-professional video-editing is all done on windowsXP machines for access to the first rate adobe tools. Opening the occasional graphics file in mail is about it on my gentoo desktop. Many thanks to all for the generous help. I guess I'll have to take the final step and setup some cron based update method that happens a lot more frequently...
[gentoo-user] Nots and bolts of creating an ebuild
After looking at: http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2chap=1#doc_chap2 [ Ebuild HOWTO ] Reading only partially so far but this looks really complicated. I thought I remembered a more nuts and bolts howto somewhere more appropriate for someone getting started who is ..er intellectually challenged. I really just want to add an epatch line to an existing ebuild but it appears some protocols need to be followed to generate the manifest and probably lots of other stuff. Can anyone point me to something? I've see it said here a few times that creating an overlay and a custom ebuild is `easy' but I suspect that only applies if you already know how its done.
[gentoo-user] Re: Nots and bolts of creating an ebuild
David Relson [EMAIL PROTECTED] writes: On Sun, 16 Nov 2008 19:16:26 -0600 Harry Putnam wrote: [ Ebuild HOWTO ] Reading only partially so far but this looks really complicated. I thought I remembered a more nuts and bolts howto somewhere more appropriate for someone getting started who is ..er intellectually challenged. I really just want to add an epatch line to an existing ebuild but it appears some protocols need to be followed to generate the manifest and probably lots of other stuff. Can anyone point me to something? I've see it said here a few times that creating an overlay and a custom ebuild is `easy' but I suspect that only applies if you already know how its done. I've created a couple of patch ebuilds, so can provide some (non-expert) info. I don't recall all the steps I took to get educated in this process, but I remember looking at a variety of ebuilds, the patterns in their names (what's legal), and the commands used within them. For system/package (for example mail-filter/bogofilter) one would 1) create directory /usr/local/portage/system/package and copy /usr/portage/system/package/* to it. 2) put the patch file in /usr/local/portage/system/package/files/ 3) create a new ebuild (with updated version) and an epatch line in src_install() 4) update the manifest file with ebuild system/package/package-version.ebuild digest Obviously these instructions are somewhat minimal. You'll likely need to run emerge package more than once to get the details right. Thanks, it was a lot of help. However I never did get the pieces right. My patch (really a [EMAIL PROTECTED] contributors) fails once I finally did get enough of it lined up to process that far. After some 40-50 or so attempts I just went ahead and pre patched the main ebuild, ran digest on that... and emerge worked, at least its compiling right now. I realize that way will miss the good side of emerge in the future and get overwritten. But I want to try this package out so maybe I'll get it right later.
[gentoo-user] Re: Nots and bolts of creating an ebuild
Daniel Pielmeier [EMAIL PROTECTED] writes: [...] Create an overlay and within that use the same structure as in the portage tree like /path/to/overlay/category/yourpackage/ [...] Nice walkthru... and just what I needed... Thanks to you and other posters who have provide some of the details.
[gentoo-user] Getting rid of all kde components
I've decided to stop using KDE after yrs of use... given that gentoo
compiles everything from scratch, its just getting to much time lost
jacking around with kde during upgrades.
But also I'd forgotten what the oldtime linux desktops were like.
fvwm was the main one in use when I started circa 1997.
I see blackbox is even a bit more stark... but since I am mainly
command line oriented it doesn't present a problem.
But cutting to the chase here, I'm getting rid of KDE but I see
kde-base/arts shows lots of dependencies. Even now that I've changed
my USE flag `kde' to `-kde'
qdepends -C kde-base/arts|awk '{gsub(/ /,\n);print}'
kde-base/arts-3.5.10:
x11-libs/qt:3
=dev-libs/glib-2
media-libs/alsa-lib
media-libs/libogg
media-libs/libvorbis
media-sound/esound
media-libs/libmad
media-libs/audiofile
dev-util/pkgconfig
=sys-devel/automake-1.9*
=sys-devel/autoconf-2.61
sys-devel/libtool
sys-devel/make
dev-util/pkgconfig
dev-lang/perl
I'm pretty sure at least some of this doesn't actually depend on
kde-base/arts but not quite sure what to make of the output.
[gentoo-user] Re: Getting rid of all kde components
Alan McKinnon [EMAIL PROTECTED] writes: I'm pretty sure at least some of this doesn't actually depend on kde-base/arts but not quite sure what to make of the output. You have it the wrong way round. Those packages do not depend on arts, instead arts depends on them. They are needed to either run or to build arts. Egad, of course. And I've used several of the depends commands for quite some time now yet every once in a while I get to thinking backwards with it. Thanks for the friendly nudge instead of a nasty whack with a 2x4.
[gentoo-user] Re: Getting rid of all kde components
Dirk Heinrichs [EMAIL PROTECTED] writes: Am Dienstag 18 November 2008 07:14:02 schrieb ext Harry Putnam: I've decided to stop using KDE after yrs of use... given that gentoo compiles everything from scratch, its just getting to much time lost jacking around with kde during upgrades. Hmm, you already complained about installation (or compile) time in the cfg- update thread. Why did you choose Gentoo, if you don't like compiling stuff? BTW: I run KDE updates in the night. You seem hell bent on picking a fight with me. But I'm not biting. You are obviously far to sophisticated and knowledgeable for me. Or at least you clearly think so. And yet it slipped right over your head that I'm clearly juggling things around that are bothersome to compile so that I can continue to run Gentoo, like I've been doing long before I ever saw your name on this list. That huge intellect has told you to read that as a complaint.. and who am I to argue. So I'll just leave it that its not really up to you what I do or don't like to compile or what OS I run. PS- This is just a thought, but have you considered restricting your responses to the subject at hand instead of finding something in a query to suit your need to showoff that towering intellect?
[gentoo-user] Re: Getting rid of all kde components
Dirk Heinrichs [EMAIL PROTECTED] writes: Am Dienstag 18 November 2008 09:06:20 schrieb ext Harry Putnam: You seem hell bent on picking a fight with me. But I'm not biting. Wow, calm down. I was just curious. Not buying Dirk. Hmm, you already complained about installation (or compile) time in the cfg- update thread. Why did you choose Gentoo, if you don't like compiling stuff? That is not the way someone who is `just curious' phasing things. The subject was Getting rid of all kde components. If you aren't going to talk about that then the normal thing is to start a new thread or hold you piece.
[gentoo-user] Re: Getting rid of all kde components
Volker Armin Hemmann [EMAIL PROTECTED] writes: But why attacking Dirk for his valid question? The OP has complained in two threads about compiling. If you don't like compiling, gentoo is not for you. If Dirk wants to ask a question about why people should not use gentoo if they don't like to compile KDE, let him start a thread about it. Don't hijack a thread about getting rid of the various components. (and what was the other complaint you mention?) And anyway a moments thought would have given him the answer. There is no mystery there, That someone finds gentoo worthwhile even though they don't like the time sink involved in compiling kde is not mysterious or hard to understand. It wasn't an innocent `gosh I'm just interested' question. OP wrote: I've decided to stop using KDE after yrs of use... given that gentoo compiles everything from scratch, its just getting to much time lost jacking around with kde during upgrades. Armin, That is not a complaint. Just a statement of fact. And let me repeat. Not liking to compile lengthy things does not make gentoo wrong for me. It's not up to you to decide that for me. Armin wrote: besides, he is one of the more knowledgeable persons on this list - you shall not fight with them, you loose to many helpfull answers that way. That's true and god knows I've needed plenty of help over the yrs, but there comes a point where wiseass, off subject, putdowns need to be dealt with. Dirks style is to pull out some piece of a query and then take off on that instead of dealing with the subject. It derails the thread as you've seen I've gotten lots of good answers from you about a host of subjects and I thank you for it. They've been well appreciated. I don't recall any of your responses asking pointless questions not on subject that derail the thread either. They've been short and to the point. Usually cutting right to the chase. But it seems people here have a sore point about compiling. Any mention of it being time consuming or a right pain in the butt, brings out commentary about how gentoo is not for that person. You may like the advantages compiling from scratch holds for you... so you do it gladly. Does not mean you have to like it. Do you actually like compiling?... You like taking hours and hours to get a current system if you fall behind? I really doubt that. So you make adjustments to deal with it. Compiling at night, ditching hefty items that are not really that useful, etc etc. Kde no longer holds enough useful advantages for me to put up with the compiling. Simple as that... no underlying dig about gentoo there. No need to respond that gentoo is not for me. I have a good idea of what gentoo is about, You might have seen my name here for yrs now. Its still a pain in that butt to loose hours and hours to compile KDE. So I ditched it. Finding all I need in blackbox. You may not have seen the first post, but I gave a clear reason as to what I was up to in the very first message: OP wrote: I've decided to stop using KDE after yrs of use... given that gentoo compiles everything from scratch, its just getting to much time lost jacking around with kde during upgrades. But also I'd forgotten what the oldtime linux desktops were like. fvwm was the main one in use when I started circa 1997. I see blackbox is even a bit more stark... but since I am mainly command line oriented it doesn't present a problem. [...] And then on to the question about getting rid of kde-base/arts. Its completely obvious there what is going on. I'm moving to a desktop more in keeping with my mostly commandline way of working. Yrs ago I started using KDE for what seems a small reason. You could pull stuff around in the pager. A feature I was used to from using fvwm. But fvwm was falling out of use in redhat about that time. Gnome and KDE were the desktops easiest to get working then. (Gentoo didn't exist yet at that time ( I don't think ) Not even Enoch was available yet.) But in the early days of GNOME its pager did not have that capability. You had to change to the other desktop to move an application or xterm so I chose kde because I liked the pager better. After that I just got used to using kde. When I moved to gentoo several yrs ago I stayed with kde Now I'm rediscovering the simplicity of a desktop like blackbox. (And you can move stuff around in its pager to boot)
[gentoo-user] Re: Getting rid of all kde components
Daniel da Veiga [EMAIL PROTECTED] writes: It doesn't seem like a complain, if you read it like you would really answer it. It wast just a comment to justify the question. I don't see a reason to question his comment. Gentoo is about choice (not just compiling), and this thread is about Getting rid of all KDE components. Someone goes off-topic and all of a sudden the OP feels attacked (I would feel the same). If you're not going to answer the question, don't send it to the list. [...] Thank you... and for the nice outline I've snipped
[gentoo-user] Re: Back up a server in real-time
Mark Somerville [EMAIL PROTECTED] writes: On Sat, Nov 15, 2008 at 07:45:04PM +, Mick wrote: Without gentoo-wiki my knowledge level is rather poor (just like my memory!) What would you use to back up a running server without taking it off line? I like rdiff-backup, which gives incremental backups over rsync. I just started playing with rdiff-backup. If you are familiar with rsnapshot maybe you'll know if rdiff-backup is better in some way. I've been using rsnapshot for quite a while but haven't had to do a serious restore (knock on wood). The small scale restores I've needed seemed to be something of a pita. I guess you have to search the rsnapshot created hardlinks for the version you want manually. At least that is what I ended up doing. There may be better ways but rsnapshot doesn't supply any help in that regard far as I know. Other than the biggest part of having created the file you need that is.
[gentoo-user] Re: tools currently available for update of etc files after updates
Dirk Heinrichs [EMAIL PROTECTED] writes: Am Sonntag, 16. November 2008 00:05:56 schrieb Harry Putnam: I did try `cfg-update' but I thought it was really slow. Slow? For me it's blazingly fast. I opened this thread back up to eat a little crow. Now that some of my config files have been thru cfg-updates process once. I see new updates processed literally in the blink of an eye. So I now agree that `blazingly' is quite appropriate.
[gentoo-user] Display all global Use flags in force
Is there a command that will display all global USE flags? I can see whats in /etc/make.conf and my 2008.0 profile at make.defaults and the profiles package.use. Are there more?
[gentoo-user] startx fails with config/hal error
I'm having what appears to be a problem starting X, that produces no a single error clear at the end of Xorg.0.log: [...] (II) Mouse0: Setting mouse protocol to ExplorerPS/2 (II) Mouse0: ps2EnableDataReporting: succeeded (EE) config/hal: couldn't initialise context: (null) ((null)) (II) UnloadModule: mouse (II) UnloadModule: kbd It appears to have something to do with loading mouse and kbd but I cannot identify anything else in that log that looks like trouble to me. I tried compiling xorg and xorg-server with the hal USE flag set to negative (-hal). Starting X still fails in much the same way but there are no errors whatever produced in Xorg.0.log in that case. (Xorg.0.log is included at the end) X actually starts and the wm (fluxbox) starts and displays the desktop background for a hot second, then crashes. Its an Nvidia gforce 5700 card. I've tried setting both nvidia and nv in /etc/make.conf and in xorg.conf. With nvidia set it fails the same with same error config/hal. The only difference I see is the nvidia logo comes up for a hot second. Apparently all drivers are present and accounted for. Here is what is currently installed from (eix -Ic|grep drivers): [I] x11-drivers/nvidia-drivers ([EMAIL PROTECTED]/20/08): NVIDIA X11 driver and GLX libraries [I] x11-drivers/xf86-input-evdev ([EMAIL PROTECTED]/13/08): Generic Linux input driver [I] x11-drivers/xf86-input-keyboard ([EMAIL PROTECTED]/12/08): Keyboard input driver [I] x11-drivers/xf86-input-mouse ([EMAIL PROTECTED]/29/08): X.Org driver for mouse input devices [I] x11-drivers/xf86-video-nv ([EMAIL PROTECTED]/19/08): Nvidia video driver Searching google has dug up a confusing array of possible help. and search.gmane.org on this group as well. Apparently the search engine at gmane cannot accept the string config/hal and sees it as `confg and hal' or `config or hal' depending on your settings but not config/hal. So naturally it turns up piles of unrelated stuff even with other words like `xorg' thrown in. But I think it has something to do with activity expected from hal that is not happening. And I have no idea how to adjust that. === Xorg.0.log X.Org X Server 1.5.2 Release Date: 10 October 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.25-gentoo-r9 i686 Current Operating System: Linux reader 2.6.25-gentoo-r9 #1 SMP Sun Nov 16 00:23:08 CST 2008 i686 Build Date: 20 November 2008 08:49:59PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Fri Nov 21 08:16:43 2008 (==) Using config file: /etc/X11/xorg.conf (==) ServerLayout X.org Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (==) Automatically adding devices (==) Automatically enabling devices (==) Including the default font path /usr/share/fonts/misc/,/usr/share/fonts/TTF/,/usr/share/fonts/OTF,/usr/share/fonts/Type1/,/usr/share/fonts/100dpi/,/usr/share/fonts/75dpi/. (**) FontPath set to: /usr/share/fonts/misc/, /usr/share/fonts/TTF/, /usr/share/fonts/OTF, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/, /usr/share/fonts/misc/, /usr/share/fonts/TTF/, /usr/share/fonts/OTF, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/ (==) ModulePath set to /usr/lib/xorg/modules (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory) (II) No APM support in BIOS or kernel (II) Loader magic: 0x81c5b80 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 4.1 X.Org XInput driver : 2.1 X.Org Server Extension : 1.1 X.Org Font Renderer : 0.6 (II) Loader running on linux (--) using VT number 8 (--) PCI:*([EMAIL PROTECTED]:0:0) nVidia Corporation NV36 [GeForce FX 5700LE] rev 161, Mem @ 0xfd00/0, 0xc000/0, BIOS @ 0x/131072 (II) System resource ranges: [0] -1 0 0x - 0x (0x1) MX[B] [1] -1 0 0x000f - 0x000f (0x1) MX[B] [2] -1 0 0x000c - 0x000e (0x3) MX[B] [3] -1 0 0x - 0x0009 (0xa) MX[B] [4] -1 0 0x - 0x (0x1) IX[B] [5] -1 0 0x - 0x (0x1) IX[B] (II) extmod will be loaded. This was enabled by default and also specified in the config file. (II) dbe will be loaded. This was enabled by default and also specified in the config file. (II) glx
[gentoo-user] Re: startx fails launching KDE 4
Andrey Vul [EMAIL PROTECTED] writes: Result of startx xlog; cat xlog : hostname: Host name lookup failure I'm not sure how much this may help you problem. But have you made changes to your /etc/hosts file recently. You might post the first line of it here.
[gentoo-user] Re: startx fails launching KDE 4
Andrey Vul [EMAIL PROTECTED] writes: On 2008-11-21, Harry Putnam [EMAIL PROTECTED] wrote: Andrey Vul [EMAIL PROTECTED] writes: Result of startx xlog; cat xlog : hostname: Host name lookup failure I'm not sure how much this may help you problem. But have you made changes to your /etc/hosts file recently. You might post the first line of it here. First line: 127.0.0.1 localhost Note: this is the first line on both the computer currently running KDE 4 and the one failing to run KDE 4. Do the contents of /etc/conf.d/hostname and /etc/conf.d/domainname have similar kind of information on both machines?. I once had quite a lot of trouble with sendmail and a helpful poster here told me to fix /etc/hosts like this: 127.0.0.1 reader.local.lanreader localhost 192.168.0.4reader.local.lanreader [...] The advice pertained to the first line above. The second was my own addition. Below is a note from my hosts file showing the origin of the tip. # From: Heinz Sporn [EMAIL PROTECTED] # Subject: Re: Why does sendmail think its hosts name is `localhost' # Newsgroups: gmane.linux.gentoo.user # Date: Tue, 07 Feb 2006 07:37:08 +0100 # Message-ID: [EMAIL PROTECTED] # [HP 02/07/06 02:37 Trying a tip from Heinz Sporn - switching ## 127.0.0.1 localhost reader to ## 127.0.0.1 reader localhost .. I think he's on to ## something... we'll see.] # 127.0.0.1localhost reader I haven't had a host lookup issue for quite a long time as you can see by the date in the post. But this may not be very helpful for your current problem. However host lookup trouble can be quite hard to diagnose.
[gentoo-user] Re: startx fails launching KDE 4
Andrey Vul [EMAIL PROTECTED] writes:
Host lookup has nothing to do with this.
Last time I checked, kde doesn't do anything with dnsdomainname.
Also, I don't even have /etc/{init.d,conf.d}/domainname .
It must have some amount to do with it:
hostname: Host name lookup failure
Was the first line of the log. It may not be a significant issue or
the reason kde is balking but apparently there is a host lookup
involved. Sorry its not what you needed.
[gentoo-user] Re: startx fails launching KDE 4
Harry Putnam [EMAIL PROTECTED] writes:
Andrey Vul [EMAIL PROTECTED] writes:
Host lookup has nothing to do with this.
Last time I checked, kde doesn't do anything with dnsdomainname.
Also, I don't even have /etc/{init.d,conf.d}/domainname .
It must have some amount to do with it:
hostname: Host name lookup failure
Was the first line of the log. It may not be a significant issue or
the reason kde is balking but apparently there is a host lookup
involved. Sorry its not what you needed.
I see now that the host lookup is only to insert information into the
log so indeed does not have bearing on the problem.
Sorry to have wasted your time.
[gentoo-user] dual booting 2 gentoo installations
I'm just having second doubts about how to dual boot 2 gentoo installations. Can I just edit grub from the original install and add the appropriate kernal line like: title=kernel-2.6.27-r3-0x31a-1280x1024 root (hd0,0) kernel /kernel-2.6.27-r3 root=/dev/hda5 vga=0x31A video=vesafb:mtrr,ywrap ## add this for new install title=kernel-2.6.27-r4-0x31a-1280x1024 root (hd1,1) kernel (hd1,1)/boot/kernel-2.6.27-r4 root=/dev/hdb2 vga=0x31A video=vesafb:mtrr,ywrap I didn't want to just try it in case there is something I've forgotten that is likely to get screwed up. I'm not asking if the addressing is right, just asking if in general this can be done with no problems.
[gentoo-user] Re: dual booting 2 gentoo installations
Alan McKinnon [EMAIL PROTECTED] writes: On Monday 24 November 2008 23:04:54 Harry Putnam wrote: I'm just having second doubts about how to dual boot 2 gentoo installations. Can I just edit grub from the original install and add the appropriate kernal line like: title=kernel-2.6.27-r3-0x31a-1280x1024 root (hd0,0) kernel /kernel-2.6.27-r3 root=/dev/hda5 vga=0x31A video=vesafb:mtrr,ywrap ## add this for new install title=kernel-2.6.27-r4-0x31a-1280x1024 root (hd1,1) kernel (hd1,1)/boot/kernel-2.6.27-r4 root=/dev/hdb2 vga=0x31A video=vesafb:mtrr,ywrap I didn't want to just try it in case there is something I've forgotten that is likely to get screwed up. I'm not asking if the addressing is right, just asking if in general this can be done with no problems. You have the right idea. Make sure your paths are correct when you install. I see you have different conventions on the two drives. Don't get confused :-) Thanks but I'm not sure what you mean by conventions... do you mean differences like that boot is not a separate partition? And the install is already largely done but still from a chrooted shell with the original Installation booted.
[gentoo-user] pager independant of window manager
Can anyone tell me if there is a desktop pager that can be run regardless of window manager? I suspect the kde (kpager) might do it but I'm not willing to fuss with the kdelibs and qt-3.3 pkgs required to install it. Browsing through portage, It appears there is not such a critter.
[gentoo-user] Re: pager independant of window manager
Dirk Heinrichs [EMAIL PROTECTED] writes: Am Samstag, 29. November 2008 18:32:34 schrieb Rodrigo Lazo: I think he mean a pager like this: http://fluxbox.sourceforge.net/fbpager/ Aargh, stupid me. Yes, there's two meanings of pager. He he... caught you in a dumb move... since you make very few of them... I'll have to make the most of this one I hoped by using `desktop pager' it would avoid this very comment. Nah nah na na naaa
[gentoo-user] Re: pager independant of window manager
Rodrigo Lazo [EMAIL PROTECTED] writes: [...] http://fluxbox.sourceforge.net/fbpager/ Yeah, I knew about that one and have tried it but its no more aware than bbpager (blackbox). By that I mean, clicking inside the pager does not transport you to that desktop. At least I did not see that happen here. However I've since found that in blackbox one can use the mouse scroll wheel to quickly navigate to any desktop and bbpager supplies the quick visual reference. So I think with a little usage, clicking in the pager will not be my first thought when needing to change desktops. One other missing ingredient though is that you cannot tell what the windows displayed inside the pager are. I'm used to seeing what they are ala kde. But again the mouse scroll is so quick, that may not matter much either. So far I can never remember which way to scroll. but with only 4 desktops I actually ever use... it still is very quick to mouse scroll until you find the right one.
[gentoo-user] Re: pager independant of window manager
Joshua Murphy [EMAIL PROTECTED] writes: Well... (pulling from http://fluxbox.sourceforge.net/fbpager/ ) in ~/.fluxbox/fbpager set: fbpager.icons: true fbpager.changeWorkspaceButton: 1 and in the case of bbpager (which doesn't support icons), in ~/.bbtools/bbpager.bb and ~/.bbtools/bbpager.nobb set: bbpager.desktopChangeButton: 1 bbpager.windowMoveButton: 3 Ahh there you go.. yes. I just hadn't dug into the files enough.
[gentoo-user] Re: pager independant of window manager
brigante [EMAIL PROTECTED] writes: exist a pager , independent and more usefull than the traditional f/bbpafger , is ipager... ...go here [http://www.useperl.ru/ipager/index.en.html] Thanks... yes looks interesting.
[gentoo-user] [OT] Other repositories
I've seen it discussed here about how to access other repositories besides the default ones shown on the mirrors link at gentoo.org. But am completely drawing blanks now trying to remember how I might go about accessing other repos... also could use a word of advice as to which are reliable or whatever.
[gentoo-user] Re: [OT] Other repositories
Etaoin Shrdlu [EMAIL PROTECTED] writes: On Thursday 4 December 2008, 23:16, Harry Putnam wrote: I've seen it discussed here about how to access other repositories besides the default ones shown on the mirrors link at gentoo.org. But am completely drawing blanks now trying to remember how I might go about accessing other repos... also could use a word of advice as to which are reliable or whatever. If by other repositories you mean overlays, see this: http://www.gentoo.org/proj/en/overlays/userguide.xml I see yes, but how do you tell what the member overlays are about? Those with names like `Apache' `perl' `VMware' etc are obvious enough but what about things like `Sunrise Gentoo User Overlay' or the ones just named after developers? layman -L just shows the source address. http://overlays.gentoo.org/ Shows little more Is there no handy way to get an idea what you might encounter in the different overlays? There doesn't seem to be any descriptions anywhere.
[gentoo-user] modules in use
How can I tell which modules of those listed by `lsmod' are actually being used? In the situation during an install when the livecd has loaded every module known to man... how can I tell which are actually being use for my hardware? The network is easy enough since only one is loaded but there must be 30 sound related modules loaded. Further... this is a vmware with gentoo as guest being installed. It shows a SVGA driven display during boot. I can't tell if any of the many modules loaded are related to that. The newest kernel doesn't appear to have a choice related to SVGA.
[gentoo-user] Re: modules in use
Paul Hartman [EMAIL PROTECTED] writes: [ ... ] (good input, thanks posters) Paul wrote: Yes, I think the only real solution is to remove things and see what breaks. So is there consensus here that Pauls' comment above is right? »Q« choose the example of his wireless module I see the same kind of thing, using alsa instead of oss. But Whatever the 0's mean, the output of lsmod won't be enough to help the OP, who really wants to be able to tell what modules are *needed*. Does that same thing apply to any network driver module? If I have started eth0; will the `0' in lsmod come and go as its used?
[gentoo-user] Re: modules in use
»Q« [EMAIL PROTECTED] writes: I see the same kind of thing, using alsa instead of oss. But Whatever the 0's mean, the output of lsmod won't be enough to help the OP, who really wants to be able to tell what modules are *needed*. $ lsmod | grep iwl iwl4965 185000 0 mac80211 112076 1 iwl4965 It's certainly possible that my wireless driver is not being used by anything at any given microsecond, but this post won't get off my computer without that driver being used. I see something in lsmod that really is confusing: lsmod Module Size Used by [...] ipv6 220812 16 [...] And I have ipv6 set negative (-ipv6) in /make.conf So very unlikely anything but other non-used modules make up the 16.
[gentoo-user] Re: modules in use
Harry Putnam [EMAIL PROTECTED] writes: I see something in lsmod that really is confusing: lsmod Module Size Used by [...] ipv6 220812 16 [...] And I have ipv6 set negative (-ipv6) in /make.conf So very unlikely anything but other non-used modules make up the 16. s/un// whooopps should have said likely
[gentoo-user] boot to console (text) mode
Sorry for the lamer question but apparently things have changed since the days when putting default 3 in /etc/inittab would make the OS boot to text (console) mode. I'm running a vmappliance of gentoo-2008.0 from June and attempting to bring it up to date. Its setup to run xfce on boot. Looking at the output of rc-update I saw xdm set for boot. Removed xdm from any runlevel and went to set inittab to default to runlevel 3 but find it already is and has been id:3:initdefault But still on a reboot it goes to xfce desktop. What have I overlooked?
[gentoo-user] Ridiculous nagging problem unable to ping
I've had this silly problem for mnths and have posted on it here some time ago. I've thoroughly exhausted my meager knowledge and attempted any fixes suggested here. I'm running an uptodate 2008.0 (not the vmware I posted about in another thread) my main desktop at home. I have simple assigned IPs throught home lan with 5 regular machines and several experimental vmwares running in windows XP machines. All sitting behind a netgear FVS-318 None and I mean absolutely none of those other machines have any trouble pinging out to the internet. I'm at a loss now as to what else to check. The machine itself has no firewall setup at all. The router is something of a firewall but no other machines have this problem. I've checked and rechecked for any kind of blocking on the Netgear for outbound and there simpley is none in place. So it must be something peculiar about this one machine. It seems there would be some diagnostic or several that would pinpoint this problem but again I'm at a loss. basic network setup from netstat -nr: Kernel IP routing table Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 127.0.0.1 255.0.0.0 UG0 0 0 lo 0.0.0.0 192.168.0.200.0.0.0 UG0 0 0 eth0 What else can I do to uncover the blockage?
[gentoo-user] Re: boot to console (text) mode
Dale [EMAIL PROTECTED] writes: You may want to check /etc/rc.conf and make sure it is not starting there. I'm assuming you want to boot to the default level but just not wanting the GUI to start. You may want search for softlevel and add that to your boot loader. Thanks... yes /etc/rc.conf was the culprit What I see about softlevel, using google ,it appears to be more involved than what I need. It must be a tool in a larger package since eix doesn't know about it on up to date portage, but I see mention of it with google. This sort of depends on why you are doing this and if it is a often used thing or just once in a blue moon. It's been my practice for many years to boot into text mode since more often than not, what I need to do can be done comfortably there. So I've always choosen to use startx as needed. That will now be possible since I can now control what happens with ~/.xinitrc. Another old practice I've clung to.
[gentoo-user] Re: Ridiculous nagging problem unable to ping
Neil Bothwick [EMAIL PROTECTED] writes: On Sat, 06 Dec 2008 15:35:34 -0600, Harry Putnam wrote: All sitting behind a netgear FVS-318 None and I mean absolutely none of those other machines have any trouble pinging out to the internet. Can you ping the other machines on your LAN? Does iptables -L show anything? No and no... I tried to answer some of those kind of questions in my OP, sorry it wasn't that clear.
[gentoo-user] Re: Ridiculous nagging problem unable to ping
Norberto Bensa [EMAIL PROTECTED] writes: Quoting Harry Putnam [EMAIL PROTECTED]: Destination Gateway Genmask Flags MSS Window irtt Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 127.0.0.0 127.0.0.1 255.0.0.0 UG0 0 0 lo 0.0.0.0 192.168.0.200.0.0.0 UG0 0 0 eth0 192.168.0.20 is really your gateway? Yes Its a Netgear FVS-318 router at the head of my home lan between lan and internet cable modem. what's iptables-save output? Iptable is turned off as mentioned in OP iptables-save: iptables-save v1.4.2: Unable to open /proc/net/ip_tables_names: No such file or directory ping is the thing you can't do? Yes. Again its like this: I can ping inside the lan no problem I cannot ping outside the lan but all other lan machines can. All machines are gatewayed to the same router. The router config shows no indication of blocking any part of the lan. Router logs show nothing but anyway, logging only occurs in bound.
[gentoo-user] Re: Ridiculous nagging problem unable to ping
Neil Bothwick [EMAIL PROTECTED] writes: On Sun, 07 Dec 2008 16:30:05 -0600, Harry Putnam wrote: Yes Its a Netgear FVS-318 router at the head of my home lan between lan and internet cable modem. Can you ping the router? Yes, usually my first test during network hookups. Its just such a natural thing to ping outside for testing resolv.conf, that its quite aggravating every time I forget which machine I'm on and try it from the one where it won't work. Not only can I ping the router... but I can connect with tcp to anything I want to on the internet. Its just that I can't ping the internet. So its something I can live with for the most part but every so often the ingrained habit of ping testing something outside will cause me some aggravation. That would seem to indicate some sort of icmp blocking but again, I can not see any evidence of that on the router.
[gentoo-user] Re: Ridiculous nagging problem unable to ping
Neil Bothwick [EMAIL PROTECTED] writes: On Mon, 08 Dec 2008 00:44:35 -0600, Harry Putnam wrote: Not only can I ping the router... but I can connect with tcp to anything I want to on the internet. Its just that I can't ping the internet. I thought you couldn't ping the rest of the LAN either? No. I can ping anywhere on the home lan. Sorry if that was not clear. If the only box you can ping is the router,it sounds like a router setting somewhere. What happens if you plug the computer into a different port on the router? Does the router have any DMZ features turned on? I can ping any box inside the lan, including the router, but even then it still sounds like a router setting since any other lan box can ping out to internet with no problem. However I cannot find a router setting that would do that. And I have no special setting in place that I can find. About DMZ, yes the router has the capability to send to a DMZ but it is disabled. my network is simple and looks like (hope this survivs mail encoding): Cable modem to internet | | = Netgear FVS-318 gateway == | | | || mch1 mch2mch3 mch4 mch5 ^^ ^ ^ no ping to internet From above mch1 But it can ping any of the other mchs including router
[gentoo-user] Re: Ridiculous nagging problem unable to ping
Mark Knecht [EMAIL PROTECTED] writes: I agree with Neil. It sounds like a router issue. Possibly a DMZ setting in the router is the same as the IP of the machine that doesn't work correctly so the ping gets to the DMZ and the response is sent out to the Internet instead of back inside? I agree too. I once had a DMZ setting set up on the router long ago. The address was 192.168.0.19. It was an old home machine running openbsd with a pf firewall. Currently no machine on the lan has that address and the DMZ capability is disabled at the router anyway. (I just checked again for about the 10th time.) I don't think you stated how the problem box got its address. Is it fixed IP or something provided by the router? They are assigned by hand (by me) so static IPs. If the 5 internal machines have consecutive addresses, have you tried changing the IP address of the machine that doesn't work to something above #5? Maybe disconnect one of the other machines and give the problem box that IP address? No I haven't but I'll try it now... just ifconfigging up a new address. ifconfig eth0 down ifconfig eth0 192.168.0.27 =was 192.168.0.4 route add default gw 192.168.0.20 ping ftp.ucsb.edu PING ftp.ucsb.edu (128.111.24.43) 56(84) bytes of data. 64 bytes from ftp.ucsb.edu (128.111.24.43): icmp_seq=1 ttl=44 time=129 ms 64 bytes from ftp.ucsb.edu (128.111.24.43): icmp_seq=2 ttl=44 time=117 ms [...] Oh boy, we in the chips now. Yippeee I new there would be some simple common sense test I would have overlooked. Thanks. So that proves something is blocking that particular address 182.168.0.4 and that seems almost certainly to be something on the router. It must be a setting I cannot find and it must be for icmp only since I've been able to traceroute or any other kind of connect, right along. I could just change that machines address but it would mean changing all other machines hosts files and such not too big a deal I guess. Might be easier to reset the router to default factory condition and and then set it up for my needs which wouldn't be much work either. It has a little hole where you press a pin and reset it. Is there any chance the blockage is coming from something on that machine and not the router?
[gentoo-user] [OT] gentoo vmware guest on winXP
I've been monkeying around with a vmware appliance of gentoo.2008.0 from July. Downloaded from bagvapp.com. It fired right up inside vmware running on winXP with no problems. But now updating I'm finding I cannot get a newer kernel compiled that will boot. The original kernel is 2.6.24-r8 and boot just fine. I attempted to compile a somewhat leaner meaner version. It appears the original was a `genkernel' creation. I paid close attention to SCSI settings in the original and any other settings having to do with disks. However my attempts consistently break out with the message: /dev/sda3 is an invalid device Of course the same /dev/sda3 is recognized fine if I boot from the original kernel. You'd think having a kernel on hand that works.. it would'nt be to tough to build a newer one using setting where possible from the old, but I'm finding it is proving to be quite difficult. Admittedly my skill level is rather low but still with one to plagiarize from seem like it should be a shoo-in. I've posted two horribly long configs here: http://www.jtan.com/~/reader/massive/ During menuconfig I ran a separate menuconfig in the old kernel directory so I had them both on screen trying to copy what seemed important. I've already tried many attempts here but still something I'm missing thats causing the kernel not to recognize /sda3 as a valid device. I hoped it would be something simple like SCSI_BUSLOGIC but that is not the case.
[gentoo-user] Re: Need to recover corrupt disk drive...
Mike [EMAIL PROTECTED] writes: So, I'm looking for advise. What should I try before I just blow it all away and start over? I REALLY would like to get my system restored/fixed, though. Any ideas would be most appreciated. I have'nt seen something like that happen before. You said grub could not identify fs on /dev/sda1/3. Can you post the out put or check it like this: grub I'm assuming sda1 is /boot find (hd0,0)/kerntab if you have something at /boot/kern* pressing TAB like shown above will complete the name and show that grub sees that partition. You could try (hd0,2)/something you know is there Like: find (hd0,2)/bin/attab Should complete to attr if grub sees the partition. You might get some kind of error too but check if the file name completed. If that stuff works, I'd try re-installing grub in the mbr of the /boot partition /sda1. In grub terms thats (hd0,0) So it would be: grub root (hd0,0) setup (hd0,0) grub outputs several lines of response quit Then reboot it and see what happens.
[gentoo-user] Re: [OT] gentoo vmware guest on winXP
Harry Putnam [EMAIL PROTECTED] writes: I've posted two horribly long configs here: http://www.jtan.com/~/reader/massive/ Sorry.. I screwed up the url. It should be: http://www.jtan.com/~reader/massive/ (no leading diag line before `reader') The page lists both the working 2.6.24-r8 working config and the 2.6.27-r5 non-working I hope someone with a similar vmware running gentoo on winXP can see what I've left out. Or maybe just supply a working config for 2.6.27*.
[gentoo-user] Re: [OT] gentoo vmware guest on winXP
Mark Knecht [EMAIL PROTECTED] writes: I will be no real help but I run the rt-sources kernel from the pro-audio overlay. (Not vmware - just a normal Gentoo machine) I have run a 2.6.24-rt version for a long time and it runs great. I recently tried the 2.6.27-rt version and I had to give up on it. It has problems for me on a normal box. I haven't paid any attention to what's going on with the kernel recently but I had to drop 2.6.26 and 2.6.26 in favor of 2.6.24. Thanks for the input... I have 2.6.27-4 running ok on at least 2 other machines so I guess it works ok on normal machines. I suspect its some little twit thing I keep overlooking.
[gentoo-user] Re: [OT] gentoo vmware guest on winXP
John J. Foster [EMAIL PROTECTED] writes: On Mon, Dec 08, 2008 at 12:56:39PM -0600, Harry Putnam wrote: I've been monkeying around with a vmware appliance of gentoo.2008.0 from July. Downloaded from bagvapp.com. It fired right up inside vmware running on winXP with no problems. But now updating I'm finding I cannot get a newer kernel compiled that will boot. The original kernel is 2.6.24-r8 and boot just fine. I attempted to compile a somewhat leaner meaner version. It appears the original was a `genkernel' creation. I paid close attention to SCSI settings in the original and any other settings having to do with disks. However my attempts consistently break out with the message: /dev/sda3 is an invalid device Try appending noapic (without the quotes, of course) to your kernel line in grub.conf. Doesn't make any difference here. I was having the same issues. So you are running gentoo inside a vmware on winXP? Can you send your /usr/src/*2.6.27-r4/.config? That is my real email address in the from field. Maybe I can find whats different .. if anything between mine and yours.
[gentoo-user] Re: [OT] gentoo vmware guest on winXP
John J. Foster [EMAIL PROTECTED] writes: Yeah, running 2.6.23-gentoo-r9 in vmplayer on XP. I was getting the same error till I read somewhere about trying the noapic option. Fired right up. Here's my grub.conf entry for the kernel in case it helps. title Gentoo Linux 2.6.23-r9 root (hd0,0) kernel /boot/kernel-2.6.23-gentoo-r9 root=/dev/sda3 noapic Thanks... that addition doesn't help me here but as you've seen I'm trying to run 2.6.27*. Something I found on line may help you at some point... in the same way you've used noapic some users have found doscsi to be helpful. From what I remember it causes any scsi scanning or loading to proceed earlier. If you'd like the .config even though it's a different kernel, just say so. No, I have earlier kernels working 2.6.24-r8, but thanks for the offer. I just want to upgrade but there is really nothing I'm after in a newer kernel. However I would like to know if there is some change since 2.6.24 that is making it so difficult to get a working config for 2.6.27* because at some point I will need to upgrade. I've successfully updated all other software on the vmware guest.
[gentoo-user] [OT] Anyone running 2.6.27* kernel as guest in vmware?
I hope I don't get torched for posting several OT threads recently but I'm really at my wits end with getting a newer kernel to work in gentoo guest on windows XP inside a virtual machine. I wondered if any kind sole who has a 2.6.27-* kernel working in that situation would mind sending me the .config file to plagiarize? I am using scsi virtual disks so if you are using ide it may make a difference but I'd still like to see the .config The `From:' address in my posts always contains my real email address so feel free to use it. That .config file is kind of large to post here.
[gentoo-user] kenel line in grub.conf when using initrd
I happen to be stuck with a machine using an initramfs. Every of attempt of mine to build a new kernel not using an initram (Or even with initram) has failed with the boot routine failing to recognize my /dev/sdb3 as root. Its a gentoo vmappliance running on windows xp pro. I'm not asking about getting the kernel right this time... I have in other threads. I just want to know more about invoking the intramfs. I know what needs to go in grub just by coping what is there originally in the vmware but I'm wondering: If you wanted to use something like vesa_fb... I know the incantations for the kernel line: Since that is how I boot my main gentoo desktop: /kernel bla-222 root=/dev/hda5 vga=0x31A video=vesafb:mtrr,ywrap On that machine I use no intramfs. But when booting from initramfs where would that kind of stuff go. Or is it made useless by booting from intramfs. Would the `vga=0x31A video=vesafb:mtrr,ywrap' go on the kernel line still or on the `initrd' line. As you see I don't really understand what is happening there. Reading that part of the handbook, it kind of skips over that. Gives direction for kernel and for initramfs but doesn't say what to do with VESA stuff if you boot from initrd.
[gentoo-user] How to tie module name to Kernel CONFIG
Summary: How can I tie a module name (tg3) to a kernel config line? Details: Usually its kind of obvious if you dig around in .config a bit, but now always. I find the module at /lib/modules/2.6.24*/: ../kernel/drivers/net/tg3.ko But I haven't been able to nail that to a kernel config line. Searches inside menuconfig on TG3 turn up nothing. grep -i tg3 of the .config file find nothing. I'm pretty sure it located between `# Protocols' (line 1139) and `# Wireless' (line 1327) I'm sure it could be different in different .config files but those two section headings should be there... maybe not on those line numbers. It is a section that covers many of the network drivers After scanning there I still am not sure where tg3 comes from or what it is.
[gentoo-user] Re: kenel line in grub.conf when using initrd
Dirk Heinrichs [EMAIL PROTECTED] writes: Am Mittwoch, 10. Dezember 2008 19:53:10 schrieb Harry Putnam: I happen to be stuck with a machine using an initramfs. Every of attempt of mine to build a new kernel not using an initram (Or even with initram) has failed with the boot routine failing to recognize my /dev/sdb3 as root. What is the error message you get? /dev/sdb3 is not a valid device [...] Thanks Why do you think you need an initramfs at all? It's usually only needed in very rare cases where either a driver for storage hardware is needed which is not part of the kernel itself or some user space things need to be done to even setup the root device before the system can be booted from it (i.e. when it's encrypted). I don't want it. I've never felt a need for initramfs before. However with this vmware appliance. I am just keeping the original setup because any of my attempts to compile a newer kernel and ditch the initramfs have failed in the way I mentioned. Apparently some basic driver or such had been missing in all my attempts. even running `make' using the same `.config' that works, has resulted in the same failure the boot routine sees the root /dev/sdb3 and an invalid device. If I boot from the original kernel and initrd... it works find. Same /dev/sdb3 rocks and rolls right along. I'm attempting piece by piece to track down what it is but I'll tell you .. it is a flat out pain in the butt has been extremely time consuming and aggravating I've compiled a different kernel at least 25 times now... I started out with the newewst and workied back a few versions then went to the exact same version 2.6.24-r8 and even there my compiled bzimage still failed. The original appears to have been compiled with genkernel so I tried that. Put the running config: zcat /proc/config.gz linux-2.6.24-r/.config into the exact same sources as the origina kernel and ran genkernel on it. That has also failed to produce a bootable kernel. However, to get a better understanding about initramfs and how it works, you should read Documentation/early-userspace/README in the kernel source tree. Thanks, that looks like a far more complete write up, than what I've seen so far. I haven't finished it yet... it will take some study. I'm starting to wonder now if the vmappliance creator has put something into the initrd that isn't the standard genkernel assembly. Some driver that makes the boot work. However during boot, the kernel I've built appears to fail after the initrd has already passed the torch on to the kernel. And in the case of the many attempted builds and booting with no initrd the message is worded a little different but says the same thing. Apparently the initrd has some different error language. I'll extract `exact' messages if you are willing to spend some time on this. But I suspect we should begin another thread with a subject that makes it clear this is about building a kernel for use inside a gentoo vmware appliance running on windows. Even if just for the sake of searchers who look here about getting gentoo running in vmware.
[gentoo-user] Re: How to tie module name to Kernel CONFIG
Alan McKinnon [EMAIL PROTECTED] writes: But help is at hand! The .config option you are looking for is CONFIG_TIGON3 My last notebook had one of those and I searched for ages before spotting one day that t, g and 3 all appeared in TIGON3. Sorry that I couldn't help with the more general question, at least you got an answer for the more specific case. Ahh haa, very good... thanks. As much mess as I've put myself thru on this kernel business having that answered is almost exciting Aha Aha ... a new avenue to try out. But I don't really hold out much hope for that being the missing ingredient When I boot from install cd it finds an SVGA type of display and a pcnet32 network requirement. But at least I was in the ball park on the section that critter is in. I haven't actually tried it yet so there is still hope hehe.
[gentoo-user] Re: kenel line in grub.conf when using initrd
Alan McKinnon [EMAIL PROTECTED] writes: You are running it in vmware right? Your disk type, disk adapters type and chipset in a vmware vm are NOT the same as these device on the physical hardware. vmware emulates a BX440 chipset, SCSI drives and LSI or BusLogic adapter. You must use those drivers, not the drivers for the physical hardware. Then everything should JustWork(tm) as the rest of your hardware is presented as-is via the hypervisor. Yes, and thanks but I had worked most of that out already. Having run a few vmware that I built. Particularly the BUSLOGIC module is important. But I've gone ahead and enabled most scsi stuff in one or another kernel build, in vain. I've used the original (bootable) kernels .config to establish the new build but still it fails. Each time I've attempted to disable a few of the settings since the running config has just about everthing imaginable enabled. Some 400+ modules installed at /lib/modules. du -sh /lib/modules/2.6.24-gentoo-r8/ 295M/lib/modules/2.6.24-gentoo-r8/ Thats a pretty unreasonable herd of modules. I haven't actually tried an actual mirror image of the running kernel... whats the point... But I do want to be able to move ahead in versions at some point. I don't need a newer kernels for any other reason than just keeping up at some point.
[gentoo-user] Tragic kernel building for vmware gentoo guest on WinXP
I've started a new thread on my kernel troubles. I thought the thread subject should be more indicative of the semi OT nature of the query. Also thought it might make the information that accrues here more findable for any future searchers. Here is the general setup and the general problem: vmware appliance made from gentoo-2008.0 I downloaded this appliance from a friendly sight that has all kinds. The appliance was built in July and so needed some updating. I www.bagvapp.com So cutting to the chase here. All software updated nicely but when I started fooling with the kernel I hit a brick wall. The original is 2.6.24-r8. Apparently built with genkernel as it has just about everthing possilbe enabled. The original setup was rigged to boot with an initrd (from grub) title=linux-2.6.24-gentoo-r8 root (hd0,0) kernel /kernel-genkernel-x86-2.6.24-gentoo-r8 root=/dev/ram0 init=/linuxrc ramdisk=8192 real_root=/dev/sdb3 initrd /initramfs-genkernel-x86-2.6.24-gentoo-r8 vga=0x317 And originally used /dev/sda3 for root. It worked just fine. But none of my attempts to bring the kernel up to date have worked. All failing with a error message something like: `/dev/sdb3 is not a valid device'. But of course it is because reverting to the original kernel allows a successful boot. You'll notice I've since moved root from /sda3 to sdb3... expanding everthing. That is not the cause of the problem though since the original kernel boots just fine with the edit to /dev/sdb3 as root. I will post exact error messages in a bit but I'd gotten rid of the extra sources.. and was about to give up messing with this. I'm redownloading the latest gentoo-source and will post what ever errors occur with it. I'll build using the old kernel config as basis. And ditch the initrd. (hours later) Looks like I fogot to mail the message above so even better... Now I have a screen shot of the messages. I've compiled 2.6.27-r5 using the config that works with 2.6.24-r8 as the basis. I did prune out a few things... all wireless some hid and most usb. This kernel fails as I expected and here is small screen shot of the error. It appears something is lacking that lets the kernel know that /dev/sda1 (boot) and /dev/sdb3 are valid /boot and / Here are the grub lines: title=/dev/sda1 hp 2.6.27-r5 NO INTITRD root (hd0,0) kernel /kernel-2.6.27-r5 root=/dev/sdb3 video=vesafb:mtrr3,ywrap vga=0x317 Screen shot of boot messages: attachment: bootshot-01.png
[gentoo-user] Re: How to tie module name to Kernel CONFIG
Geralt [EMAIL PROTECTED] writes: Hi, a generic way is: 1) Go to /usr/src/linux 2) grep tg3 $(find -name Makefile) Nice... I had come up with an even more shotgun approache. grep -r tg3 kernel-name I didn't have enough sense to know it would be in Makefiles
[gentoo-user] Re: Tragic kernel building for vmware gentoo guest on WinXP
Nikos Chantziaras [EMAIL PROTECTED] writes: Harry Putnam wrote: [...] It worked just fine. But none of my attempts to bring the kernel up to date have worked. All failing with a error message something like: `/dev/sdb3 is not a valid device'. According to your screenshot, you don't even have an sdb. All the kernel sees is one hard disk: sda. If you do have an sdb, check in VMWare that it's actually attached to the VM. Also, are you sure the VM you downloaded is for the version of VMWare you're actually using? Why not create the VM yourself instead of downloading it? You may have over looked this in the previous message: You'll notice I've since moved root from /sda3 to sdb3... expanding everthing. That is not the cause of the problem though since the original kernel boots just fine with the edit to /dev/sdb3 as root. So I have one kernel that will boot just fine, and discovers /dev/sdb3 with no problem... and had no problem with it. So the shortfall is in the kernel itself. Something I'm missing in the working kernel config that is not finding its way into the newer build . Look at `mount' ouput when I'm booted the working kernel-2.6.24-r8 rootfs on / type rootfs (rw) = /dev/sdb3 on / type ext3 (rw,noatime,data=ordered) /proc on /proc type proc (rw,nosuid,nodev,noexec) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec) udev on /dev type tmpfs (rw,nosuid) devpts on /dev/pts type devpts (rw,nosuid,noexec) shm on /dev/shm type tmpfs (rw,nosuid,nodev,noexec) rc-svcdir on /lib/rc/init.d type tmpfs (rw, [...] = /dev/sda1 on /boot type ext2 (rw) none on /dev/shm type tmpfs (rw) usbfs on /proc/bus/usb type usbfs (rw,noexec,no [...] securityfs on /sys/kernel/security type securi [...] debugfs on /sys/kernel/debug type debugfs [...]
[gentoo-user] Re: Tragic kernel building for vmware gentoo guest on WinXP
Nikos Chantziaras [EMAIL PROTECTED] writes:
Harry Putnam wrote:
[...]
It worked just fine. But none of my attempts to bring the kernel up
to date have worked. All failing with a error message something like:
`/dev/sdb3 is not a valid device'.
According to your screenshot, you don't even have an sdb. All the
kernel sees is one hard disk: sda. If you do have an sdb, check in
VMWare that it's actually attached to the VM.
Also, are you sure the VM you downloaded is for the version of VMWare
you're actually using? Why not create the VM yourself instead of
downloading it?
I downloaded one thinking it would be faster after spending several
days trying to get my own built and running. I had the same boot
problem with my own rendition.
And in fact it booted up absolutely painlessly. It was only when I
started trying to build a newer kernel that the troubles began.
About sdb3. In the following dmesg output (when booting with a
working kernel-2.6.24-r8 I wondered if anyone can determine what
driver is involved there. I couldn't really tell much from it other
than the kernel sees it with no problem:
==
[...]
mptbase: ioc0: Initiating bringup
ioc0: LSI53C1030 B0: Capabilities={Initiator}
scsi4 : ioc0: LSI53C1030 B0, FwRev=h, Ports=1, MaxQ=128, IRQ=16
scsi 4:0:0:0: Direct-Access VMware, VMware Virtual S 1.0 PQ: 0 ANSI: 2
target4:0:0: Beginning Domain Validation
target4:0:0: Domain Validation skipping write tests
target4:0:0: Ending Domain Validation
target4:0:0: FAST-40 WIDE SCSI 80.0 MB/s ST (25 ns, offset 127)
sd 4:0:0:0: [sdb] 44040192 512-byte hardware sectors (22549 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 5d 00 00 00
sd 4:0:0:0: [sdb] Cache data unavailable
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sd 4:0:0:0: [sdb] 44040192 512-byte hardware sectors (22549 MB)
sd 4:0:0:0: [sdb] Write Protect is off
sd 4:0:0:0: [sdb] Mode Sense: 5d 00 00 00
sd 4:0:0:0: [sdb] Cache data unavailable
sd 4:0:0:0: [sdb] Assuming drive cache: write through
sdb: sdb1 sdb3
sd 4:0:0:0: [sdb] Attached SCSI disk
sd 4:0:0:0: Attached scsi generic sg2 type 0
=
[gentoo-user] Re: Tragic kernel building for vmware gentoo guest on WinXP
Nikos Chantziaras [EMAIL PROTECTED] writes:
[...]
mptbase: ioc0: Initiating bringup
ioc0: LSI53C1030 B0: Capabilities={Initiator}
scsi4 : ioc0: LSI53C1030 B0, FwRev=h, Ports=1, MaxQ=128, IRQ=16
That's an LSI Fusion-MPT controller. Enable:
Device Drivers-[*] Fusion MPT device support-
* Fusion MPT ScsiHost drivers for SPI
Reboot. Have fun :P
I don't think thats the trouble... that has been enabled in every
kernel compile I've run trying to get a working config.
The original setup was rigged to boot with an initrd. How can I take
that initrd apart and see if there is some trick driver built into
it.
[gentoo-user] Re: Tragic kernel building for vmware gentoo guest on WinXP
[EMAIL PROTECTED] writes: My guess is tha while inside the initrd a kenrel module was loaded and it was something that you needed to read the boot volume. Are you statically or modulely including your sata drivers? Sent via BlackBerry from T-Mobile kyle, how can I discover what is in the intramfs. Can it be loop mounted or something. Is there someway to take it back apart?
[gentoo-user] Re: Tragic kernel building for vmware gentoo guest on WinXP
Nikos Chantziaras [EMAIL PROTECTED] writes:
Harry Putnam wrote:
Nikos Chantziaras [EMAIL PROTECTED] writes:
[...]
mptbase: ioc0: Initiating bringup
ioc0: LSI53C1030 B0: Capabilities={Initiator}
scsi4 : ioc0: LSI53C1030 B0, FwRev=h, Ports=1, MaxQ=128, IRQ=16
That's an LSI Fusion-MPT controller. Enable:
Device Drivers-[*] Fusion MPT device support-
* Fusion MPT ScsiHost drivers for SPI
Reboot. Have fun :P
I don't think thats the trouble... that has been enabled in every
kernel compile I've run trying to get a working config.
The original setup was rigged to boot with an initrd. How can I take
that initrd apart and see if there is some trick driver built into
it.
cp /boot/the-initrd-you-want ~/initrd.cpio.gz
gunzip ~/initrd.cpio.gz
Examine it's contents with mc or extract it with cpio.
But I don't think there's a trick driver or anything involved. You
don't even need an initrd if you compile the LSI driver in-kernel.
I just made in initrd for that kernel2.6.27-r5... and by god it
booted using the initrd so that initrd is loading the driver you
mentioned I guess.
I see now that even the original working kernel had LSI driver as
module ...so I'll try compiling into the kernel now as you've
suggested. Thanks...
[gentoo-user] Re: Tragic kernel building for vmware gentoo guest on WinXP
Nikos Chantziaras rea...@arcor.de writes:
Harry Putnam wrote:
Nikos Chantziaras rea...@arcor.de writes:
Harry Putnam wrote:
Nikos Chantziaras rea...@arcor.de writes:
[...]
mptbase: ioc0: Initiating bringup
ioc0: LSI53C1030 B0: Capabilities={Initiator}
scsi4 : ioc0: LSI53C1030 B0, FwRev=h, Ports=1, MaxQ=128, IRQ=16
That's an LSI Fusion-MPT controller. Enable:
Device Drivers-[*] Fusion MPT device support-
* Fusion MPT ScsiHost drivers for SPI
Reboot. Have fun :P
I don't think thats the trouble... that has been enabled in every
kernel compile I've run trying to get a working config.
The original setup was rigged to boot with an initrd. How can I take
that initrd apart and see if there is some trick driver built into
it.
cp /boot/the-initrd-you-want ~/initrd.cpio.gz
gunzip ~/initrd.cpio.gz
Examine it's contents with mc or extract it with cpio.
But I don't think there's a trick driver or anything involved. You
don't even need an initrd if you compile the LSI driver in-kernel.
I just made in initrd for that kernel2.6.27-r5... and by god it
booted using the initrd so that initrd is loading the driver you
mentioned I guess.
I see now that even the original working kernel had LSI driver as
module ...so I'll try compiling into the kernel now as you've
suggested. Thanks...
Well I think I can fairly report that absolutely none of these
suggestions has helped... I don't mean the info unearthed in them.. I
mean putting them in practice has failed miserably.
Built in or modules... including all the junk in the working kernel
config. All fails when the rubber meats the road.
Even removing the .config and calling `genkernel all' which build a
kernel with all bells and whistles even that fails to boot.
You also need the filesystem driver built-in (ext3, Reiser, whatever
you're using.) An initrd is really only useful for generic kernels
and for bootsplash. I guess that means the appliance you downloaded
was sub optimal in the sense that nothing special or any kind of
effort was required to create it. A good appliance would have
provided a slim kernel with only what's needed compiled-in since
VMWare has the same hardware everywhere (that's the whole point of
VMWare actually.)
Yes, I did have enough sense to build in all filesystem type stuff
Maybe the appliance was suboptimal... but it beat the hell out of my
own attempts at building one from gentoo. All of which totally failed
to boot. It boots effortlessly if I use the original kernel and initrd
and the price was right...
Thinking about it... it really did save me a lot of hair pulling. I'm
going thru it now by choice... but in the meantime I have a working
appliance.
Harry Putnam wrote:
Nikos Chantziaras rea...@arcor.de writes:
cp /boot/the-initrd-you-want ~/initrd.cpio.gz
gunzip ~/initrd.cpio.gz
Examine it's contents with mc or extract it with cpio.
But I don't think there's a trick driver or anything involved. You
don't even need an initrd if you compile the LSI driver in-kernel.
Thanks for example commans.
No there doesn't appear to be anything special.
But compiling those items in-kernel has made not one whit of
difference ... bootup still fails.
I then tried copying as best I can from the working kernel config of
2.6.24-r8 by running menuconfig in that directory and
genkernel --menuconfig all in the new kernel directory.
I'd already tried the same thing but without genkernel... just calling
make after getting the config as close as seems possible to the
working config. ... That failed
So now employing genkernel on the same closely copied .config hoping
at least the new kernel will boot with the initrd genkernel creates.
Again,,, failed miserably at boot time.
So hand built or genkernel built the result is the same ... no boot.
I did have one success... hand built kernel 2.6.27-r5 and then ran
`genkernel initrd --install' to plop the initrd in /boot
That handbuilt kernel will boot but only with the initrd.
Oh, and if any one is interested here are the commands needed to
decompose the initramfs.
(stolen in large part from Nikos - thanks Nikos):
mkdir test
cd test
cp /boot/the-initrd-you-want ./initrd.gz
gunzip initrd.gz
cpio -ivd initrd
Will result in extracting the filestructure and files out of the
initrd.
Best to do the first step so extraction takes place in a test
directory, away from the regular file system.
[gentoo-user] Re: kenel line in grub.conf when using initrd
Heinrichs, Dirk (EXT-Capgemini - DE/Dusseldorf) dirk.heinrichs@nsn.com writes: [...] What is the error message you get? Posted in thread: Tragic kernel building for vmware gentoo guest on WinXP [...] Did you try to examine the contents of that initrd with the one you produce. Maybe somthing is missing there. Could you post the .config here together with an ls -Rl output of the initrd contents. I suspect the drivers mentioned by Alan are compiled as modules and put into that initrd instead of just compiling them into the kernel. Would like to verify that. Inlined at the end is the output of ls -lR [...] I'm starting to wonder now if the vmappliance creator has put something into the initrd that isn't the standard genkernel assembly. Some driver that makes the boot work. Yes, that may be the case. However during boot, the kernel I've built appears to fail after the initrd has already passed the torch on to the kernel. Usually it's vice versa. The kernel uses the initrd as a temporary root fs. This one sets up the real rootfs (by loading the needed driver modules, unlocking encrypted devices or similar stuff). Finally, it calls pivot_root to switch root devices and runs /sbin/init from the real root device. I'm saying the failure appears to happen after pivot_root.. what ever initrd loaded wasn't enough for the kernel to find /dev/sdb3 That particular build and attempt has been replaced by several new tries. [...] Sure, we can give it a try. Please see the thread noted at the start of this message. If you are willing to continue. === ls -lR ~/projects/kernel/test/ /home/reader/projects/kernel/test: total 5820 drwxr-xr-x 2 reader reader4096 Dec 11 11:45 bin drwxr-xr-x 2 reader reader4096 Dec 11 11:45 dev drwxr-xr-x 3 reader reader4096 Dec 11 11:45 etc -rwxr-xr-x 1 reader reader 15025 Dec 11 11:45 init drwxr-xr-x 4 reader reader4096 Dec 11 11:45 lib lrwxrwxrwx 1 reader reader 3 Dec 11 11:45 lib64 - lib lrwxrwxrwx 1 reader reader 4 Dec 11 11:45 linuxrc - init drwxr-xr-x 2 reader reader4096 Dec 11 11:45 proc drwxr-xr-x 2 reader reader4096 Dec 11 11:45 sbin drwxr-xr-x 2 reader reader4096 Dec 11 11:45 sys drwxr-xr-x 2 reader reader4096 Dec 11 11:45 temp -rw-r--r-- 1 reader reader 482 Dec 11 11:50 tocat drwxr-xr-x 4 reader reader4096 Dec 11 11:45 usr drwxr-xr-x 3 reader reader4096 Dec 11 11:45 var /home/reader/projects/kernel/test/bin: total 7844 -rwxr-xr-x 8 reader reader 995368 Dec 11 11:45 [ -rwxr-xr-x 8 reader reader 995368 Dec 11 11:45 ash -rwxr-xr-x 8 reader reader 995368 Dec 11 11:45 busybox -rwxr-xr-x 8 reader reader 995368 Dec 11 11:45 cut -rwxr-xr-x 8 reader reader 995368 Dec 11 11:45 echo -rwxr-xr-x 8 reader reader 995368 Dec 11 11:45 mount -rwxr-xr-x 8 reader reader 995368 Dec 11 11:45 sh -rwxr-xr-x 1 reader reader396 Dec 11 11:45 udhcpc.scripts -rwxr-xr-x 8 reader reader 995368 Dec 11 11:45 uname /home/reader/projects/kernel/test/dev: total 0 crw-rw 1 reader reader 5, 1 Dec 11 11:45 console crw-rw 1 reader reader 1, 3 Dec 11 11:45 null crw--- 1 reader reader 4, 1 Dec 11 11:45 tty1 /home/reader/projects/kernel/test/etc: total 36 -rw-r--r-- 1 reader reader97 Dec 11 11:45 fstab -rwxr-xr-x 1 reader reader 1775 Dec 11 11:45 initrd.defaults -rwxr-xr-x 1 reader reader 24046 Dec 11 11:45 initrd.scripts drwxr-xr-x 2 reader reader 4096 Dec 11 11:45 modules /home/reader/projects/kernel/test/etc/modules: total 52 -rw-r--r-- 1 reader reader 24 Dec 11 11:45 ataraid -rw-r--r-- 1 reader reader 17 Dec 11 11:45 dmraid -rw-r--r-- 1 reader reader 75 Dec 11 11:45 evms -rw-r--r-- 1 reader reader 23 Dec 11 11:45 firewire -rw-r--r-- 1 reader reader 31 Dec 11 11:45 fs -rw-r--r-- 1 reader reader 36 Dec 11 11:45 lvm -rw-r--r-- 1 reader reader 75 Dec 11 11:45 mdadm -rw-r--r-- 1 reader reader 10 Dec 11 11:45 net -rw-r--r-- 1 reader reader 534 Dec 11 11:45 pata -rw-r--r-- 1 reader reader 83 Dec 11 11:45 pcmcia -rw-r--r-- 1 reader reader 173 Dec 11 11:45 sata -rw-r--r-- 1 reader reader 513 Dec 11 11:45 scsi -rw-r--r-- 1 reader reader 74 Dec 11 11:45 usb /home/reader/projects/kernel/test/lib: total 8 drwxr-xr-x 2 reader reader 4096 Dec 11 11:45 keymaps drwxr-xr-x 3 reader reader 4096 Dec 11 11:45 modules /home/reader/projects/kernel/test/lib/keymaps: total 348 -rwxr-xr-x 2 reader reader 2823 Dec 11 11:45 1.map -rwxr-xr-x 2 reader reader 2823 Dec 11 11:45 10.map -rwxr-xr-x 2 reader reader 2823 Dec 11 11:45 11.map -rwxr-xr-x 2 reader reader 2823 Dec 11 11:45 12.map -rwxr-xr-x 2 reader reader 2823 Dec 11 11:45 13.map -rwxr-xr-x 2 reader reader 2823 Dec 11 11:45 14.map -rwxr-xr-x 2 reader reader 2823 Dec 11 11:45 15.map -rwxr-xr-x 2 reader reader 2823 Dec 11 11:45 16.map -rwxr-xr-x 2 reader reader 2823 Dec 11 11:45 17.map -rwxr-xr-x 2 reader reader 2823 Dec 11 11:45 18.map -rwxr-xr-x 2 reader reader 2823 Dec 11 11:45 19.map -rwxr-xr-x 2 reader reader 2823 Dec 11
[gentoo-user] Re: kenel line in grub.conf when using initrd
Heinrichs, Dirk (EXT-Capgemini - DE/Dusseldorf) dirk.heinrichs@nsn.com writes: Am Donnerstag, den 11.12.2008, 08:05 +0100 schrieb ext Heinrichs, Dirk (EXT-Capgemini - DE/Dusseldorf): I'll extract `exact' messages if you are willing to spend some time on this. But I suspect we should begin another thread with a subject that makes it clear this is about building a kernel for use inside a gentoo vmware appliance running on windows. Sure, we can give it a try. Oh, I see you already did and got it solved. Fine. Not! I managed to hand build a kernel and initrd that booted but still have not managed to build a trimmed down kernel that needs no initrd. See thread: `Subject: Tragic kernel building for vmware gentoo guest on WinXP'
[gentoo-user] Re: Tragic kernel building for vmware gentoo guest on WinXP
Dirk Heinrichs dirk.heinri...@online.de writes: From that and the contents of the original initrd you posted in the former thread and what others already found out: This initrd has all all sorts of driver modules for SATA and SCSI chipsets, so it's most likely that you forgot to compile in the correct drivers into your custom kernel. I think I've seen somebody already identified one of them as some Fusion SCSI driver, so I guess you would need to compile the Fusion stuff into your kernel (they even have an own section in menuconfig). That turned out a failure... already posted here (Sorry about the thread confusion) What this initrd doesn't have is modules for SCSI Disk support and filesystems, so they seem to be compiled into the kernel directly. Yes, compiled in. Could please post the kernels .config (or /proc/config) and lspci output from the original, working setup? Yes, sorry I made you work so hard for the info... you did ask for more info but I got working on this thread and forgot. These URLS seem to be loading kind of slow right now: lspci on system running 2.4.26-r4 www.jtan.com/~reader/kdiag/lspci.html config from build of 2.6.24-r8 (This one boots with initrd) www.jtan.com/~reader/kdiag/config.html lslR on initrd structure built in kernel tree 2.6.24-r8 www.jtan.com/~reader/kdiag/lslR_initrd.html lsmod on system running 2.6.24-r8 www.jtan.com/~reader/kdiag/lsmod.html
[gentoo-user] Re: Tragic kernel building for vmware gentoo guest on WinXP
Dirk Heinrichs dirk.heinri...@online.de writes: Forgot this one: dmesg output from the working setup. www.jtan.com/~reader/kdiag/dmesg.html
[gentoo-user] Re: Tragic kernel building for vmware gentoo guest on WinXP
Nikos Chantziaras rea...@arcor.de writes: Nikos Chantziaras wrote: [...] Just to make sure you're doing it right... [...] Forgot to mention that no initrd is needed and the grub.conf should not have an inird line. Ok Nikos... I'm going to do that right now but of course it will take a little while. Please continue the discussion under the new thread if you have time and are so inclined your input has been very usefull. I'm going to follow your receipt to the letter and report back.
[gentoo-user] Re: Tragic kernel building for vmware gentoo guest on WinXP
Dirk Heinrichs dirk.heinri...@online.de writes: [...] OK, I'll give it a try. I see this in lspci [...] and this in dmesg [...] which then later detects the sdb partitions. This means that you would need to compile the following into the kernel: CONFIG_PCI CONFIG_SCSI CONFIG_BLK_DEV_SD CONFIG_FUSION CONFIG_FUSION_SPI plus the filesystem you have formatted the partition with. But, as said this detects the _second_ device. You also need the drivers for the first one. If you leave them out, the fusion device will be detected as _sda_. So you'll also need: CONFIG_ATA CONFIG_ATA_PIIX and eventually CONFIG_ATA_ACPI CONFIG_SATA_AHCI You've got a sharp eye Dirk. Seems like you pieced it together pretty easily once given enough info. Thanks for your patience Dirk. Nikos, thanks for your patience as well Any other posters I've missed... much thanks. Not only can boot with no initrd but bootup is very noticably faster than with the original kernel. Might even be close to %50 faster. Well anyway considerably faster. Now to take notes on the proceedures passed along in this thread and try to do my own kernel compiling next time.
[gentoo-user] Re: video driver discovery
Robert Bridge rob...@robbieab.com writes: On Fri, 19 Dec 2008 18:35:35 + (UTC) James wirel...@tampabay.rr.com wrote: How can I verify which driver(version) it is using? Read /etc/log/Xorg.0/log It will tell you which driver it loaded. Sorry to butt in here.. but Robert can you show a line from your log that IDs the driver... I'm getting really confused looking at that log. It shows literally dozens of things `loading'. Its not clear where whatever is being loaded came from... what installed package or driver. Its probably right in front of me, but I'm not seeing it, or not recognizing what I see as being very useful I guess.
[gentoo-user] kernel config hell
Summary of request for help: Are there hardcore kernel builders in the house who can steer me to a faster way of figuring out what the installed modules do... for sure. Details: I'm at a point where any pared down kernel config I've built and tried has some terrible thing wrong with it. Usually involving udev and openrc someway or other... things not getting started or mounted etc etc. A full on genkernel build seems to be the quickest way to get a working kernel. That done, I'm now plodding along with build after build trying to discover what it is the genkernel has that my pared down versions do not. Trying to discover what all the 80 or so installed modules do seems like a really slow process. Take the module name and try to find something like it in .config I've even written a perl script to allow me to input the module names, or parts thereof and grep out the section name and lines that match inside .config. This is at least a weak start at knowing what the module is about. I'd think there would be some kind of cross reference somewhere that would connect module names to what they do, and what .config options are associated. Another path is to find the *.ko names in /lib/modules and use the absolute name to track them down in the kernel sources where there is usually a README of some sort in the tree leading to the *.ko. But my god what a slow and painful way to find out what these modules do. Just rmmod is another way but again a very slow and painful way. Maybe a module is used only occasionally and rmmodding may not show what it was for right away. What ever fails may not happen immediately.
[gentoo-user] Re: kernel config hell
Nikos Chantziaras rea...@arcor.de writes: [...] Well, my bit of wisdom here: Don't use modules. Do a make menuconfig, disable everything you don't need, and compile everything you need in-kernel instead of as a module. I'd say the disable everything you don't need part is what Harry's mail is all about. Well, finding out what every installed module does isn't going to help anyway. I'd start with only the modules currently used after a fresh boot (lsmod). If you compile those in-kernel, it will boot. Everything else can be tweaked later. Yeah, I talked about that in OP. But the only kernel I've got working at the moment is a genkernel and it installs 80+ modules. rmmoding my way through those is what lead to my post. Some indicate they are in use but I can see they aren't related to things I actually need. Digging that bit of info up is what I've been talking about. Dirk Heinrichs dirk.heinri...@online.de writes: What could help you here is a make xconfig. It's similar to make menuconfig but has a nice QT user interface. I would recommend to browse through it once and look at the help texts which are shown in the lower right pane for each option you klick. Based on this information, you can then decide wether or not to enable that option or even compile it as module. I have looked at that before but didn't think it was any better than `menuconfig' and the '/' help tool. Many times the help provided doesn't really explain what a given setting does. In fact in most cases it does not. What is really aggravating is that it doesn't even really tell you what exact thing in .config is being set with the various hundreds of options. I mean when you do set something, you don't really get to see what is being set inside of .config. I don't have X running currently so its a mute point, but is the help provided in xconfig and different than that available in `menuconfig'? Details: I'm at a point where any pared down kernel config I've built and tried has some terrible thing wrong with it. Usually involving udev and openrc someway or other... things not getting started or mounted etc etc. With udev, those things usually work automatically. However, you must make sure that everything needed for accessing the root filesystem must be compiled into the kernel. That usually includes the driver for the chipset that operates your harddisks, harddisk support and the filesystem used for /. I'd think there would be some kind of cross reference somewhere that would connect module names to what they do, and what .config options are associated. I don't know of any. But in most cases, the module name is listed in the help text. Another path is to find the *.ko names in /lib/modules and use the absolute name to track them down in the kernel sources where there is usually a README of some sort in the tree leading to the *.ko. Somtimes, you can also simply guess by module name, for example: joydev.ko - Joy(stick)Dev(ice). But my god what a slow and painful way to find out what these modules do. Yes, that's true. The browsing method may give you a rough overview within an hour or two. Just rmmod is another way but again a very slow and painful way. Maybe a module is used only occasionally and rmmodding may not show what it was for right away. What ever fails may not happen immediately. Or try modprobe + dmesg instead. Usually a driver module tells wether it has found some pice of supported hardware or not. Now that is a good piece of advice there... I did notice that rmmoding and modprobing can give you more info than you expect if you hit something that the module latches onto. I'm finding somewhat rough sledding in dmesg too. I find the ethernet stuff with no problem and, by now, know what I need there. My hardware is pretty common stuff, not even any sata discs, all ata. and I'm still not sure which driver is needed there. On the last attempted kernel, I just went menuconfig on a copy of the genkernel .config and turned off a number of things I was pretty sure didn't apply to me (all wireless for example) or anything but ethernet under the network section. All firmware turned off. Stuff I've never needed before. Every thing mounted but still no network was started or any of the stuff listed in `rc-update show'. I was dumped out into a root shell where I was able to modprobe and '/etc/init.d/bla start' my way into a fully running system. So the stuff was there but something (I suspect udev) blocked it starting up like it should. At the same time a genkernel built kernel just boots as expected so clearly something was turned off that shouldn't have been. Right now my dmesg is clogged up with stuff since bootup so I'm going to reboot the genkernel built kernel and have a close look at dmesg (again for the 10th time ..) rmmod and modprobe and see what I find.
[gentoo-user] Re: kernel config hell
Nikos Chantziaras rea...@arcor.de writes: Harry Putnam wrote: Nikos Chantziaras rea...@arcor.de writes: [...] Well, my bit of wisdom here: Don't use modules. Do a make menuconfig, disable everything you don't need, and compile everything you need in-kernel instead of as a module. I'd say the disable everything you don't need part is what Harry's mail is all about. Well, finding out what every installed module does isn't going to help anyway. I'd start with only the modules currently used after a fresh boot (lsmod). If you compile those in-kernel, it will boot. Everything else can be tweaked later. Yeah, I talked about that in OP. But the only kernel I've got working at the moment is a genkernel and it installs 80+ modules. The way I do it, is to simply know what hardware is in the machine (dmesg, lspci and hwinfo for things I'm not sure about) and look for it in the kernel configuration. For the few modules that remain where I don't know what they do, I just google their names. The important stuff is just the PATA/SATA controller, SCSI disk support and keyboard/mouse though. The rest I add later. Sounds like a plan... thanks. Maybe eventually some of that output will be a little easier. Here I just mean dmesg... lspci is easy enough. I must need some specific package to see hwinfo. Its unknown to bash here.
[gentoo-user] Re: kernel config hell
Dale rdalek1...@gmail.com writes: You may also want to try lspci -v. It shows you what modules the hardware uses and it should be able to boot with those at least. Example: Well son-of-a-gun... that is nice. Thanks
[gentoo-user] [OT and ducking buckshot] How can I tell Debian version installed
Don't shoot. I ask here because I know some here are debian users. I just created an vmware app with debian... I thought I was using the newest install media for latest release (lenny I think). But once installed (and this was a network install not from disc) I find really ancient tools.. a 2.6.18 kernel for example. Running `apt-cache search emacs' shows the newest available version to be emacs-21... which is barely even supported still. I must need to edit my sources for package installs or something but isn't there a way to know right off the bat what version of debian you have? But I'm thinking I've got hold of some older version here.
[gentoo-user] Re: [OT and ducking buckshot] How can I tell Debian version installed
Charles Welton rockyspirit2...@gmail.com writes: Other than that, this is not the list for such questions. Thanks... and right you are.
[gentoo-user] What is starting net.eth1 [not in rc-update]
I don't have an entry for net.eth1 in rc-update show I don't have any mention of eth1 in /etc/conf.d/net (only eth0) Nonetheless something continues to try to start net.eth1 during boot. What else controls that? If its not in rc-update or /etc/conf.d/net it shouldn't happen. I have a few other boot problems...I'm not sure where they arise from. hwclock is meddling about during shutdown. Again, it isn't shown in rc-update and /etc/conf.d/hwclock has this in it: # If you want to set the Hardware Clock to the current System Time # during shutdown, then say YES here. You normally don't need to # do this if you run a ntp daemon. clock_systohc=NO Still, on a shutdown I can't get past this output: hwclock waiting for localmount (Over and over) I have to hit a manual reset on the computer to get past hwclock waiting for localmount Also klogd cannot be stopped by reboot or shutdown. But at least, unlike hwclock, after a pause the shutdown proceeds anyway. eix -Ic openrc sys-apps/openrc (0@12/25/08): OpenRC manages the services, startup and shutdown of a host eix -Ic udev [I] sys-fs/udev (135...@12/24/08): Linux dynamic and persistent device naming support (aka userspace devfs)
[gentoo-user] Re: What is starting net.eth1 [not in rc-update]
Dirk Heinrichs dirk.heinri...@online.de writes: Am Sonntag, 28. Dezember 2008 12:38:37 schrieb Harry Putnam: Still, on a shutdown I can't get past this output: hwclock waiting for localmount I mentioned it in your other thread. Try masking openrc =0.4.0. Yeah, just got around to reading that with this nudge. I've masked it and downgraded but haven't rebooted yet. I'm looking at Ian Lee's posted URL... maybe those guys are on to something.
[gentoo-user] Re: What is starting net.eth1 [not in rc-update]
Ian Lee i...@leehouse.eclipse.co.uk writes: 1) net.eth1 problem There is a udev hook for starting net.* init scripts, /lib/udev/rules.d/90-network.rules to be precise The script is very brief There is no mention of net.eth1 in that script SUBSYSTEM==net, ACTION==add,RUN+=net.sh %k start SUBSYSTEM==net, ACTION==remove, RUN+=net.sh %k stop Further it says not edit this script since it gets overwritten on update. Apparently this is not the place to alter what happens at runlevels. 2) Openrc problem I'm asuming here the openrc problems are from a recent upgrade you have done and not inslalled the the runlevels required sadly they are not done automatically. Have a look in /usr/share/openrc/runlevels these are needed for openrc to work copy any that don't exist in /etc/runlevels most important are sysinit and shutdown, boot and default are likey to be fine They are all present in /etc/runlevels. And again I see no reference to net.eth1 or hwclock
[gentoo-user] Re: What is starting net.eth1 [not in rc-update]
Dirk Heinrichs dirk.heinri...@online.de writes: Am Sonntag, 28. Dezember 2008 12:38:37 schrieb Harry Putnam: Still, on a shutdown I can't get past this output: hwclock waiting for localmount I mentioned it in your other thread. Try masking openrc =0.4.0. I've masked =sys-apps/openrc-0.4.0 and downlgraded to sys-apps/openrc (0.3.0...@12/28/08) Bootup seems normal except for the fact that something is still trying to start eth1. Other things seem to have started normally and no hwclock on shutdown. So why are there entities beyond /etc/conf.d/net and the controls used in rc-udpate that can even start things in /etc/init.d? Aren't those two controls the time honored places to handle that sort of stuff? What else is capable of attempting to start services? Have I been hacked (.. hehe)
[gentoo-user] Re: What is starting net.eth1 [not in rc-update]
Ian Lee i...@leehouse.eclipse.co.uk writes: Ian Lee wrote: Neil Bothwick wrote: On Sun, 28 Dec 2008 17:04:23 -0600, Dale wrote: Probably hotplug, add !net.eth0 to rc_hotplug in /etc/rc.conf That's in /etc/conf.d/rc on mine. Has it moved? It moved in the switch from baselayout1 to baselayout2/openrc. This could be what four looking for http://bugs.gentoo.org/show_bug.cgi?id=206518 Ian try putting rc_coldplug=no in conf.d/udev or /etc/rc.conf i would assume the udev init script checks both places I can tell you from trying that just now... that is not a good solution. First setting rc_coldplug=no has some very bad effects: 1) caused my KVM switch setup to be ignored completely, where as with with the default yes the kvm is recognized soon as I get past grub 2) Very strange behavior with the `screen' tool. I call screen and get started but if I do `C-a c' (which should start another screen) Instead it prompts me to login and then takes the original screen so I can only get one screen, completely defeating the purpose of `screen'. I'm also wondering about the wisdom introduciing some esoteric places to control services. If someone needs sophisticated controls they can set that up, but for the rest of us /etc/conf.d and rc-update should be THE central tools to have basic services started at boot. There should be nothing scrolling thru the network softlinks attempting to start anything it finds.
[gentoo-user] Re: What is starting net.eth1 [not in rc-update]
Ian Lee i...@leehouse.eclipse.co.uk writes: They are all present in /etc/runlevels. And again I see no reference to net.eth1 or hwclock that udev rule starts any found network devices on your system net.sh is just a wrapper to the net.* scripts in init.d, if you never use eth1 then remove net.eth1 from /etc/init.d. Well that kind of sucks. I don't use eth1 often but I do want it in /etc/init.d. I'm wondering how wise it is to have tools other than re-update and /etc/conf.d dinking around with basic services. It seems like starting an unwanted ethernet device could even have serious security problems. Having to remove it from /etc/init.d doesn't sound like a very good solution either.
[gentoo-user] KVM recognition changes in recent kernels
kernel 2.6.27-r7 and 2.6.28 and several other earlier kenels Summary: Anyone here know more details about the kernel settings and KVM switching? Details: (and inlined dmesg) I'm not exactly sure when or what kernel was in use when this change in behavior started but its been at least 2 mnths ago. Phenomena: I've used kvm switching for several yrs... Usually trouble free. I have 4 machines running thru a KVM switch including my main desktop running 2008 gentoo. The others are winXP I don't have the kvm model to hand but it is an IOGEAR 4 port USB I've noticed a change in recent mnths where until bootup is complete the kvm switch is not recogized. I see that thru several kernel upgrades and various kernel builds. I have to have a second keyboard connected direct if I want to mess around with grub or something... while testing kernels. But once bootup reaches the login prompt the KVM is in the loop, and I can use the kvm connected keyboard. In kernels somewhere back down the road the KVM was in the loop right from the start. Diagnosing is made harder by the fact that I've changed KVM switches twice in that time. However, with the current KVM there was a point where it was recognized immediately and available even at the grub screens. Unfortunately I didn't document any of this at the time. It appears the kernel has to have some of the `hid' settings enabled for the KVM to work at all so I'm wondering if some special setting is what is responsible for the change. I've found in recent experiments with 2.6.28 that at least these two settings must be set `y' or `m' in order for the KVM to work at all CONFIG_HIDRAW=y # near line 1269 (2.6.27-r7 .config) CONFIG_USB_HID=m # near line 1274 (2.6.27-r7 .config) It gets pretty complicated beyond those two trying to see if anything else will allow the KVM to be seen immediately. == I'm probably just not sharp eyed enough but I don't see anything relating to KVM in particular. The kvm works in this case but only after bootup completes. dmesg following recent boot of 2.6.28 BIOS EBDA/lowmem at: 0009fc00/0009fc00 Linux version 2.6.28-gentoo-hp (r...@reader) (gcc version 4.3.2 (Gentoo 4.3.2-r2 p1.5, pie-10.1.4) ) #5 Tue Dec 30 23:32:16 CST 2008 KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD NSC Geode by NSC Cyrix CyrixInstead Centaur CentaurHauls Transmeta GenuineTMx86 Transmeta TransmetaCPU UMC UMC UMC UMC BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 7fff (usable) BIOS-e820: 7fff - 7fff8000 (ACPI data) BIOS-e820: 7fff8000 - 8000 (ACPI NVS) BIOS-e820: fec0 - fec01000 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: fff0 - 0001 (reserved) DMI 2.3 present. AMI BIOS detected: BIOS may corrupt low RAM, working it around. last_pfn = 0x7fff0 max_arch_pfn = 0x10 kernel direct mapping tables up to 377fe000 @ 1-16000 ACPI: RSDP 000FA3A0, 0014 (r0 AMI ) ACPI: RSDT 7FFF, 002C (r1 AMIINT INTEL865 10 MSFT 97) ACPI: FACP 7FFF0030, 0081 (r1 AMIINT INTEL865 11 MSFT 97) ACPI: DSDT 7FFF0120, 37D5 (r1 INTELI865G 1000 MSFT 10D) ACPI: FACS 7FFF8000, 0040 ACPI: APIC 7FFF00C0, 005C (r1 AMIINT INTEL8659 MSFT 97) 1159MB HIGHMEM available. 887MB LOWMEM available. mapped low ram: 0 - 377fe000 low ram: - 377fe000 bootmap 00012000 - 00018f00 (6 early reservations) == bootmem [00 - 00377fe000] #0 [00 - 001000] BIOS data page == [00 - 001000] #1 [10 - 4ce398]TEXT DATA BSS == [10 - 4ce398] #2 [4cf000 - 4d2000]INIT_PG_TABLE == [4cf000 - 4d2000] #3 [09fc00 - 10]BIOS reserved == [09fc00 - 10] #4 [01 - 012000] PGTABLE == [01 - 012000] #5 [012000 - 019000] BOOTMAP == [012000 - 019000] Zone PFN ranges: DMA 0x0010 - 0x1000 Normal 0x1000 - 0x000377fe HighMem 0x000377fe - 0x0007fff0 Movable zone start PFN for each node early_node_map[2] active PFN ranges 0: 0x0010 - 0x009f 0: 0x0100 - 0x0007fff0 On node 0 totalpages: 524159 free_area_init_node: node 0, pgdat c045b544, node_mem_map c1000200 DMA zone: 32 pages used for memmap DMA zone: 0 pages reserved DMA zone: 3951 pages, LIFO batch:0 Normal zone: 1744 pages used for memmap Normal zone: 221486 pages, LIFO batch:31 HighMem zone: 2320 pages used for memmap HighMem zone: 294626 pages, LIFO batch:31 Movable zone: 0 pages used for memmap ACPI: PM-Timer IO Port: 0x808 Allocating PCI resources starting at 8800 (gap:
