Sorry - been marooned in Maine for a day.

You should use the gentoo-dev sources for amd64.Actually those are the only ones that supposedly work.You can also check with the gentoo forums under architectures.There is a sticky thread about amd64 issues and stuff.

I always install from stage 1.Did have trouble with stage3 once and never with stage1.

Hey crash, tnx for your replies.
I did infact use the gentoo-dev-sources kernel.
Got most of the install done, but now I'm stuck.

I created a new thread, cuz it's more gentoo now than suse.
http://www.linuxquestions.org/questi...hreadid=166660

if you are interested.

Tnx.
L8rz

I am currently running FC1 (standard i386) on an emachine M6805. Most things work fine. I'm running kernel-2.6.5 (configuration available on request), and use a couple periferals, namely an intelimouse and a usb2-dvdrw+/-. I'm using the ati driver for video, and i'm still using the OSS libraries for sound (via82cxxx_audio is the kernel mod). ACPI is configured with pci=noacpi during kernel boot. And I'm using acpi_irq_balance as well, though it doesn't seem to make much of a difference whether thats in there or not. ACPI works for the power button, battery and cpu. The machine can be put to sleep, but waking up is a bit more challenging. Suspending to swap works sometimes, and not others, not sure why that is.

Problems I'm working on now seem to be relating to the fact that my machine seems to double up on its irqs. A look at my interupts file:

CPU0
0: 4351499 XT-PIC timer
1: 4165 XT-PIC i8042
2: 0 XT-PIC cascade
8: 1 XT-PIC rtc
9: 78391 XT-PIC ndiswrapper, uhci_hcd, eth0
10: 99787 XT-PIC acpi, uhci_hcd, via82cxxx
11: 0 XT-PIC uhci_hcd
12: 10860 XT-PIC i8042
14: 15176 XT-PIC ide0
15: 6479 XT-PIC ide1
NMI: 0
ERR: 0

Note that ndiswrapper is installed, this is to load the broadcom driver for my integrated wireless card, which doesn't work. In fact, activiating the wireless card (FN+F2) causes other drivers to get into a traffic accident:

Apr 20 15:16:44 laptop kernel: irq 10: nobody cared!
Apr 20 15:16:44 laptop kernel: Call Trace:
Apr 20 15:16:44 laptop kernel: [<c010bb2a>] __report_bad_irq+0x2a/0x90
Apr 20 15:16:44 laptop kernel: [<c010bc1c>] note_interrupt+0x6c/0xb0
Apr 20 15:16:44 laptop kernel: [<c010c1a9>] do_IRQ+0x259/0x340
Apr 20 15:16:44 laptop kernel: [<c0112ae7>] restore_fpu+0x17/0x20
Apr 20 15:16:44 laptop kernel: [<c010a158>] common_interrupt+0x18/0x20
Apr 20 15:16:44 laptop kernel:
Apr 20 15:16:44 laptop kernel: handlers:
Apr 20 15:16:44 laptop kernel: [<c01f6adb>] (acpi_irq+0x0/0x16)
Apr 20 15:16:44 laptop kernel: [<e0966010>] (via_new_interrupt+0x0/0x180 [via82cxxx_audio])
Apr 20 15:16:44 laptop kernel: [<e09a7630>] (usb_hcd_irq+0x0/0x70 [usbcore])
Apr 20 15:16:44 laptop kernel: [<e0a2e290>] (ohci_irq_handler+0x0/0xc70 [ohci1394])
Apr 20 15:16:44 laptop kernel: Disabling IRQ #10

The drivers which get hit are not always the same.

I'm curious. Is there a way to change the IRQs which these devices are using? The BIOS on the eMachine isn't exactly useful. There is a ton of information which is probably required to diagnose this problem if you haven't delt with it in the past, and I'm more than willing to work with anyone who has the knowledge necessary to troubleshoot something like this.

I'm also interested in obtaining a full keymap for use within the kernel to activate the volume/internet keys. I'm sure there is a way to pull this out of the machine, but I'm pretty new to kernel programming and haven't the background information required to do this yet.

frm

I tried installing the new gentoo 2.6.5 install on my emachines M6805 laptop and everything went fine until the reboot when I tried to login. The ethernet failed and the keyboard didn't respond at the login prompt. I have successfully installed the 2.6.3 kernel and everything went fine although I haven't been able to setup X, probably not due to bugs but my inexperience.

My mouse is responding when I 'cat' the mice driver file.
Can someone please supply a /etc/make.conf and XFree86.conf file for the M6805 laptop that they used where kde or gnome was successfully installed. Also step by step instructions would be helpful. When I type startx there is a white bar across the screen and I suspect that the screen is being scrunched down.

I'm not particularilly familiar with gentoo, but presuming everything is basically the same as a redhat/fedora system package wise here is what you need to do to get X working well:

1) download the video drivers from ati Here

2) Install the RPM. ATI did a great job on their packaging, it will build against your kernel and install a kernel module for you.

3) Install the synaptics touchpad driver get it here

4) use the xfree86 config file located here

You should be all set. This config will support both the touchpad and an external usb mouse. With the synaptics driver for the touchpad compiled and installed you get support for things like tapping the touchpad for mouse button, and the side scroll bar working in X.

Good luck.

I don't know about the synaptics driver but the pad worked fine for me without any patching.There are no 64 bit drivers from ati and the 32 bit drivers will not work on a 64 bit system - you can only use the vesa driver there - not even the xfree radeon driver will work on this chipset.
Make sure you don't got any typos in the bootoptions.

I beg to differ. I'm using the 32 bit drivers on my 64 bit system right now. They are working perfectly.

line from my lsmod: fglrx 213572 7

The touchpad 'worked' but you don't have full functionality using the default ps2 driver for it. The synaptics driver makes it work better.

That doesn't look like a 64 bit system.

Aye, I'm running 32 bit code on my 64 bit processor. Perhaps I made an invalid assumption that destraht was running the default gentoo installation and not the amd64 version of the install, putting him in the same hardware/software config class I'm in. In which, the 32bit driver runs fine on my 64bit hardware.

I just assumed that he uses the 64 bit distro since that's where the thread came from.I had 32 bit running on there no problem except for the IRQ's and that and a problem with apic.
But as was said by the mod's "Hell we ain't need no stinkin' 64 bit forum - too confusing".

Did you happen to fix that apic problem? I've been fighting that, as well as a few others, and have got to the point where I've dumped the DSDT table on my machine, and have been working on fixing it. Funn, doing an iasl -d on the DSDT table produces code that won't compile using iasl -tc becuause of msising methods in avarious parts of the code; most prominently the CPU0 section. As well as a fairly comon problem with bounds. Of course, I get a kernel panic during the parse of the table when rebooting with it built into the kernel...

Didn't fix it - I got rid of the laptop because the ati support got me really p'd off.AFAIK there is no fix for it yet.Maybe emachines will release a BIOS one day that doesn't share the IRQ's.

ah, I'm just using it with pci=noacpi, haven't really had a problem with that though it may be a directly reason that I can't wake after S3, but I suspect that that has more to do with the fact that the wake state isn't written correctly in the DSDT table.

I think that I'm going to just wait awhile before I use linux on my M6805. I have spent around 30 hours total trying out the distros and have yet to find something that completely works. Gentoo 2004.0 amd 64 using pci=noapic works but I can't get X to work correctly or it is buggy. I'm sure if I knew enough I could change every other configuration file but it isn't worth the effort right now for me. The truth is I'm not getting anything done, I'm just installing OSs. With the BIOS problems and the experimental nature of the 64 bit OS this is not an easy setup. Also Gentoo 2004.1 doesn't work, I guess they introduced a new bug? All of the 9.2, and 10.0 mandrakes don't work and Fedora Core 1 and Core 2 beta 3 don't seem to work.

My take is that this is impossible for me to understand at the moment because there are too many complicated problems and also that the damn BIOS is the main problem. From what I understand the kernel needs to be compiled in a certain way with USB built-in instead of as a module or it won't work and that there are other special kernel considerations for the laptop if it is going to work in 64 bit mode. That means to me that even after alot of these problems get ironed out there might still be later versions of distros that forget about the laptop only to remember it in a later version? Isn't that the way it would work? We need to get this damn BIOS problem fixed. Does anybody know the most effective way of doing this, perhaps the email of a sympathetic Emachines or Via employee? I don't see this problem getting fixed right away because it works fine on Windows XP with the quick switch program.

Please anyone let me know if I don't know what I'm talking about.

You are absolutely correct - 64 bit OS is slightly on the experimental side right now and there are issues with drivers and stuff.It's probably not as bad with a regular box because you can choose what you put in there.I am thinking hp or compaq right now for a laptop because those are the only ones with nvidia graphics but that is a backburner thing.