Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Some great information all around! Thank You
  2. I'm not someone who hasn't read the handbook. I also have several other books, that say "don't worry about installing every module now, just the essential...because they can be installed later". In fact I've installed a custom kernel, so i won't be reverting to anything simpler any time soon. What I'm asking for is a generic yet accurate explaination of what happens when a module (driver) is installed later on (Your musings, far less taxing than an overly technical hurdle). Is it "registered with the kernel" somehow? is the entire kernel recompiled each time? is there an intermediate program that handles new modules "mod[something something]" Is it a standard or non-standard way of dealing with modules? What are the essential (abstract?--though I doubt I'd ever consider accurate summation abstract... the crux of my burden in life) elements of the addition of a module to a system?
  3. I'm trying to get as deep an understanding as I can so I can eventually be a power user like you folks. So manuallly setting up the Kernel is a big deal (at least for someone like me). Is it important that I find all the drivers the first time through? Is the Kernel updated with every driver install? Driver installation is of course automated on other platforms, and it is to some extent on funtoo as well (there are packages for different graphics cards). Is that last statement the key to my answer? That the Kernel does need to be updated every time but that it's done with the install script? And if it is updated, what does that entail? (everything seems so intimately connected going through this the first several time; the kernel bone's connected to the bios/uefi grub... bone etc.) Would it just be updating the kernel "file" thing that comes out of compilation, replacing the old one where it sits?
  4. I may end up doing that. It should work. It's far less of a performance jump for me though.Thanks for the input.
  5. This is the Xorg.0.log after the xorg.conf guidance is added: http://pastebin.com/TjXezKUt And the dmesg after the same, just for the hell of it: http://pastebin.com/LwtKRehh It goes black on udev, after install, and during a startx .. Like the hardware framebuffer only wants to cooperate with a very few efi friends. I still have no idea what udev has to do with it.
  6. 'Ran startx in the dark. I was told nvidia glx driver should be in use, not x.org's. I'm a little angry that that was not done for me in a pristine emerge, if that's the case. (Wouldn't know the best way to fix it, if an issue) This is my newly created Xorg.0.log : http://pastebin.com/uYayUjB6
  7. Sorry for venting. Thanks for the responses to the "Kernel Advice" thread, which should be considered "solved" for good general advice. 'wising up :0], and getting specific: I have only been able to boot with either one of the two efi framebuffer configurations (that I know of) enabled. Either EFI Framebuffer outright, or the Simple Framebuffer with Mark VGA/VBE/EFI FB as generic... everything works: mouse, keyboard, internet, wacom, webcam seems detected... It's only after an aparently squeeky clean install of xorg-server, pulling in a masked to appropriate version nvidia-drivers, that the screen goes black at "starting udev" The terminal functions in the blackness. I'm also very experienced in chrooting in and doing/undoing things. Though I'm taking it slow and easy this time; 'trying to hit the target. UVESAFB is configured to the best of my knowledge, however it fails to load as I have specified in my kernel commandline options, and "falls back" to simple framebuffer (maybe UVESAFB and NVIDIA-DRIVERS are encountering the same problem? ...further My assumption is the efi does not require efi fbs if it's booting in "legacy mode" assuming I have it. I have setup an install with an efi-grub loader pointing at a "normal" kernel and install; and that did not work (thought it may be that I haven't got those installation methods down). The kernel would seem to be ...real nice... besides haha. If that even means anything. It's so cerebral (I think maybe I could boot "normally" or maybe it's fundamental failure corrected by efistub options somehow). I'm now paying closer attention to the dmesg, finding no xorg.0.log (because xorg doesn't run on boot! suprise to me... thinking it was the xorg-server install that triggered the issue... nor is XDM or XFS in the default runlevel anyway... does UDEV trigger X somehow?) So here is my dmesg, if you care to join me :0] http://pastebin.com/f5a3yYRf
  8. It's going on three months now. It's been an enlightening journey. But it looks like it's just going to end in heartbreak. I have installed funtoo/gentoo on my machine in so many different configurations I can't count. I've done uefi stub, uefi/grub, rEFInd with all sorts of filesytem configurations. I'm just now getting very confident in the function of everything. I was only able to get the kernel to boot once, with efi stub... and SPECIFICALLY with efi frambuffer [uncheck it and it's cooked again]... No other configuration will boot... at all. Is Kernel configuration really this ALL ...or nothing?... Can't I at least crack the boot... just once; Just once see some boot messages scrolling. My Kernel boots, but only as a uefi stub. What the hell does that mean? everything you need for your computer to run is in your kernel but.... but... no.? What book or manpage could I possibly read in my lifetime to make a custom kernel for a 2010 macbook air? (I have a book on kernel configuration). I'm starting to believe no amount of expertise could take me there. Right now. I have gentoo-sources with the configuration file that booted the uefi stub, with the stub options removed, while I constantly recompile and reboot with new fb options. It has a functioning uefi grub bootloader on a fat sda1 /boot partition that points at and is configured for my kernel and initramfs. I see grub. That's always good. But then darkness after selecting funtoo. The mouse is lit as well as the screen, this was not always the case. Having all this freedom and new knowledge. It's like being trapped in a glob of cement on a beach filled with beautiful girls, while slowly dying. I installed sysklogd, there is no log file when I chroot in from the usb after a boot. Where should I even look? What should I read? The only reason I looked up new flavors and found funtoo was because I wanted to streamline my dated machine for graphics. It's excruciating to think that after all is said and done, I may as well have stuck with my clunky linuxmint install three months ago. What is this one incredibly stubborn stumbling block? How did you approach learning about kernels when you first started? (generally speaking)
  • Create New...