or Connect
NotebookForums.com › Forums › General Notebook Discussions › Linux & Other OS's › Community Project: Get ABF to build Gentoo and shut up
New Posts  All Forums:Forum Nav:

# Community Project: Get ABF to build Gentoo and shut up - Page 2

I'd add the networking stuff for wireless. I run a monolithic kernel so the only things I have in my /etc/module.autoload.d/kernel-2.6 are ipw2100 stuff. It realy depends on what is mudularized for your genkernel build.
so xorg installed, but having issues setting it up, doesn't recognise by touchpad. i emerged synaptics, nothing yet

EDIT:
nvm, found a fix. now installing gnome....now we wait
so i left it to install gnome overnight, it didn't finish. i just turned off the computer because i didn't want it to run all day today (i will not be back till 9pm) so thats a setback, gnome is taking a while...and yes i did do USE="-qt -kde" and i did xorg before and that only took just over an hour.
Yea Gnome or KDE both will take a LONG time to install, so many packages.

Honestly I always just started them emerging and maybe 2 or 3 other programs I know I needed and went to sleep for the night, depending on how it was doing in the morning I might keep it going or give it a break. Interesting to hear about your drivers on that ethernet port, I havent had that problem myself yet on any of the gentoo installs I have done.

In as far as the touchpad, search through the gentoo docs and wiki, I believe there is something on there for it, there is a littel extra work that has to be done in the xorg.conf file I believe for it.

Quote:
 Originally Posted by seablade Yea Gnome or KDE both will take a LONG time to install, so many packages.
Back when I was still using KDE, early 3.x versions used to take about 3 hours to compile, sans fluff like games and some other packages. This was on my 5680 with the 2.4GHz chip (I've upgraded to a 3.2GHz chip since then; 6 minutes for a clean kernel compile, 'ing love it.).
ugh...i have a 2.0ghz amd64 3200+ and it did the kernel fast (less than an hour) it did xorg fast (less than 2 hours), and done kde (back in the day...when i tried to install gentoo for the first time) took less than 4 hours. Why did gnome take 7+ hours?
I don't think Gnome should take that long. I think you've bloated the numbers a bit, abf. the AMD64 chip should perform better than the 'equivalent' P4. Either way, Xorg takes 40-60 minutes, Firefox takes 35-40 minutes. Did you have a gig-o-RAM?
I dont think ABF is bloating numbers much at all to be honest, what he said sounds right compared to my single opteron chip installs with a gig of ram, I remember gnome taking quite a while, of course there may be other reasons for that like due to USE flags not just installing the Base Gnome package but also installing a few extras and things like that.

like i said, i did "USE -kde -qt" and i only have 512mb right now....i lost my other 512mb stick a little while back....lol. still can't find it. at any rate, my goal is to finish of gnonme install today/tonight/tomorrow and get the rest of the thing going
UPDATE
======

Goals Achived So far:
----------------------------
-install x86 stage 3 base installation
-install xorg and gnome (2.10) and xscreensaver

Goals to Achive:
---------------------
-install fglrx
-get sound to work
-get cpu freq to work
-install software which includes but is not limited to firefox, gaim, thunderbird, xchat, mplayer, xmms, xine-ui
-install media codecs (w32codecs and otherwise)
-and finally...>BUG FIXES (err...rather things i screwed up originally that i now need to fix)

i guess the major reason for this update is to tell you gnome now works and we got a visual on the screen...no more working from text mode...YEY. there is still a long way to go though
let the bug fixing begin!

so at this point i have installed most basic software i need for day to day operations (firefox, gaim, openoffice, mplayer, xine) and this is actually the first reply i am writing from gentoo.

next up is to get my wireless to work because i can't sit next to the router all day long, it would be nice that i can go back to my room and do the work in comfort, not ugh...anyway. madwifi is giving me a bad signal (quality=0/100) so i figured i'd go the all natural way (madwifi). currently emerging all that good stuff.

some things that need fixing and i have no idea how to fix:
1 - USB plug-n-play. basically, i want it to auto mount my USB devices, and i want my USB mouse to work. the touchpad works, but its no fun to use, i need a mouse

2- on boot up it starts but then it pauses and asks me what partition to boot (so i have to type in /dev/hda2 ...which is my ext3 partition) and then it continues. how can i make it know that /dev/hda2 is my linux partition so i am not stuck typing /dev/hda2 every time i boot up.

thats pretty much it in terms of problems that need to be fixed NOW

i believe i already resolved my resolution and alsa issue, i just need to reboot to check, however openoffice is taking a hell lot of time to emerge so i didn't have a chance y
in order.
1) I emerged hald and gnome-volume-manager, added hald to default runlevel, and added my user account to the hald group. That should get your usb drives working. I haven't bothered with adding a usb mouse to the laptop in linux. I use my MX duo in windows for gaming.

2) Can you post up your grub.conf and fstab for us to take a look at.
fstab:
Code:
# /etc/fstab: static file system information.
# $Header: /var/cvsroot/gentoo-src/rc-scripts/etc/fstab,v 1.18.4.1 2005/01/31 23:05:14 vapier Exp$
#
# noatime turns off atimes for increased performance (atimes normally aren't
# needed; notail increases performance of ReiserFS (at the expense of storage
# efficiency).  It's safe to drop the noatime options if you want and to
# switch between notail / tail freely.
#

# <fs>\t\t\t<mountpoint>\t<type>\t\t<opts>\t\t<dump/pass>

# NOTE: If your BOOT partition is ReiserFS, add the notail option to opts.
/dev/hda2\t\t/\t\text3\t\tnoatime\t\t0 1
/dev/hda3\t\tnone\t\tswap\t\tsw\t\t0 0
/dev/cdroms/cdrom0\t/mnt/cdrom\tiso9660\t\tnoauto,ro\t0 0
#/dev/fd0\t\t/mnt/floppy\tauto\t\tnoauto\t\t0 0

# NOTE: The next line is critical for boot!
proc\t\t\t/proc\t\tproc\t\tdefaults\t0 0

# glibc 2.2 and above expects tmpfs to be mounted at /dev/shm for
# POSIX shared memory (shm_open, shm_unlink).
# (tmpfs is a dynamically expandable/shrinkable ramdisk, and will
#  use almost no memory if not populated with files)
shm\t\t\t/dev/shm\ttmpfs\t\tnodev,nosuid,noexec\t0 0


lilo.conf
Code:
boot=/dev/hda
prompt
timeout=100
default=windows

image=/boot/kernel-genkernel-x86-2.6.12-gentoo-r10
\tlabel=gentoo
\troot=/dev/hda2
\tinitrd=/boot/initramfs-genkernel-x86-2.6.12-gentoo-r10

other=/dev/hda1
label=windows



### oh crap

oh crap is the least of my worries.

i rebuilt my kernel because the genkernel sucked. i added on alsa support, powernow support, and changed the cpu family from 586 to athlon64. now 1/2 the modules don't load, gnome is being a bitch, and i can't get online anymore, not even wired

i am not giving up. for the next few days i will be using windows but i will rebuild, but i'll start at either stage 1 or 2 and i will do a custom kernel from the start, no genkernel for me
ABF feel free to rebuild your kernel of course, but I would STRONGLY reccomend you always keep the old at least until you can confirm that the new works, and make a new entry in your boot loader for the new one.

For some reason I have better luck with doing a menuconfig through the genkernel script than a straight menuconfig for the boot loader, otherwise I got some problems on bootup, a kernel panic I never did narrow down, needless to say it wasnt your typical reasons of no support for filesystems or lack of ramfs, for an example. Never figured out exactly why that was.

Ina s far as recompiling your kernel from 586 to AMD64... I am not completly sure but I believe you may need to recompile everything that uses your kernel from that point as it would all be compiled for a 32bit environment and all the sudden you would be trying to run it in a 64 bit environment. That is the reason why in 64 bit environments a chrooted 32 bit environment is so popular to run certain apps(Such as wine)

right now i have no time to do the fixes. i really don't so meanwhile since i need a working computer i installed ubuntu. i will rebuild when i find a span of some free time
Quote:
 Originally Posted by seablade For some reason I have better luck with doing a menuconfig through the genkernel script than a straight menuconfig for the boot loader, otherwise I got some problems on bootup, a kernel panic I never did narrow down, needless to say it wasnt your typical reasons of no support for filesystems or lack of ramfs, for an example. Never figured out exactly why that was.
My guess is that the kernel image wasn't copied appropriately?
ehh better luck next time. Gentoo can be a real bear. You'll get it. at least you can get Ubuntu up and going fairly quickly. We'll be here when you need us.
Quote:
 Originally Posted by john_sheu My guess is that the kernel image wasn't copied appropriately?
Nope redid it several times, it was copied correctly and the bootloader(Grub) set up correctly, I actually think it was a problem with the ramdisk that was made. The error was typically the error you get when support for your filesystem was not compiled into the kernel, in this case it was, and a ramdisk was made anyways, however I still got the same Panic, and repeated said process multiple times. I did notice though that the genkernel seems to make a ramdisk without mkinitrd which is what I used so I think there is a different method used there that works a bit better.