Randalf, thanks, that patch did the trick. I don't understand how it is that after searching through numerous forum posts/bug reports/blog posts about Gentoo on Alu PB G4s, this patch was never mentioned. Thanks again.

Hi randalf, thanks for the pointer. /proc/bus/input/devices shows several devices, including an ADB mouse. Bus 0017 Vendor 0001 Product 3301 Version 0100. The Sysfs is /class/input/input3 and the Handlers are mouse1 and event3.

There are also listings for "Macintosh mouse button emulation" and ...

Okay, well I looked in /usr/src/linux/.config and /proc/config.gz and the latter said that appletouch was unset. So I built a new kernel, making sure that appletouch was set to 'y' and that evdev was also set to 'y'. I booted using that kernel, but I still have the same exactly synaptics errors. Any ...

How can I check that? I know I can look in , but I think I probably have futzed around in and saved changes in anticipation of compiling a new kernel. So how can I check what my kernel was actually built with?

Thanks for the idea, gringo. No, I hadn't been using /dev/input/event3 as my Device in the InputDevice center. All the examples, and the generic InputDevice mouse use /dev/input/mice. But I did try using /dev/input/event3, and just the same, the log issues the notification:

(II) Synaptics ...

I'm having this same issue. The errors say:

(II) Synaptics touchpad driver version 0.14.6 (1406)
Synaptics no synaptics event device found (checked 17 nodes)

**snip**

(EE) Synaptics no synaptics touchpad detected and no repeater device
(EE) Synaptics Unable to query/initialize Synaptics hardware ...

Subject line says it all. When I load the keymap marked mac-dvorak, none of the keys are correct, the characters that keys correspond to are just a mess: backspace doesn't mean backspace, for example. I'm wondering if there's a keymap for using the Dvorak layout on a PowerBook keyboard (this is an ...

sPHERE911 wrote:EDIT: The LiveCD image is over 800mb, why's that? I mean, there's already a LiveDVD iso.

Yeah, I don't get this. How is this going to fit on a CD?

Dirk.R.Gently wrote:Is ppc (32 bit) support being dropped?

Or perhaps PPC (32 bit) just isn't one of the architectures for the beta release.

I don't know what exactly I did but I managed to get it to merge correctly. Maybe I had a typo, because I copied and pasted those lines again. It seemed to error when I didn't specify USE="rt2500usb" so maybe I had to do that.

Then I modprobed the modules: rt2500, rt2x00usb rt2500usb, rt2x00 lib ...

I used the ebuild from this bug and simply added your lines between done and linux-mod_src_compile:
sed -i -e 's/ rt2x00dev->interface.id,//g' rt2x00mac.c
# SO quick and dirty...
echo '#define IEEE80211_TXCTL_LONG_RETRY_LIMIT (1<<10)' >> rt2x00.h
Your ebuild also gives hassles when the rfkill use ...

I tried each of the ebuilds, and when I modprobe the modules I get errors in dmesg:

usbcore: deregistering interface driver rt2500usb
wmaster0: Failed to select rate control algorithm
wmaster0: Failed to initialize rate control algorithm
phy1 -> rt2x00lib_probe_dev: Error - Failed to initialize hw ...

kingLatency,

Its not part of any overlay - rt2x00 is in portage, so it will not be in an overlay too. You need to make your own overlay.
See /etc/make.conf.example to learn how to tell portage about your overlay location.
Put the code snippet into a file in your overlay called net-wireless/rt2x00 ...

What overlay is that package part of? How do I set it up?

Thanks for posting this, I'm having the same problem. The ebuild is asking for options in the kernel that are no longer in the kernel, it seems.

Where is the file you're editing? I'm looking in /usr/portage/net-wireless/rt2500 and I see some ebuilds but not the 9999 one. Am I looking in the right ...

You only need that ramdisk support if you plan on setting up a bootsplash image. Did you trying switching from vesafb-tng to vesafb, and recompiling your kernel? That's what I had to do. Keep in mind that with the older vesafb you need a vga= option instead of the resolution in the video= line. You ...

Well, switching to vesafb instead of vesafb-tng did the trick, thanks.

I was, however, hoping to set up gensplash. Does anyone know if that requires the use of vesafb-tng or if it will work with plain 'ol vesafb?

Thanks!

VESA default mode in the kernel: 1024x768@75

For the grub.conf kernel line I've tried a number of adjustments, currently:

I'm using vesafb-tng. I've tried setting it up with just the kernel settings and no resolution in grub.conf, or no video= part in the kernel line of grub.conf, but neither work. I heard that works for some people, but it didn't on my system, for whatever reason. Any other ideas?

Hi folks. I recently upgraded my kernel to 2.6.22-r2 (from 2.6.21-r4 from when I first installed a few weeks ago) to help me get my USB wireless device working, but now I don't get the proper resolution in virtual terminals. I have a 15" LCD whose native resolution is 1024x768... the machine boots ...

I'm setting up a bot for an IRC channel I frequent. Formerly, I ran an eggdrop bot there. But since this bot is mainly for seen, google, imdb, and logging, I figure I can use something a lot simpler and easier to set up. However, there seem to be a plethora of IRC bots to choose from.

So, what IRC ...

I've got 3.3.3, so I guess that bug is what's affecting me. I'm going to try gentoo-dev-sources.

I may just try a newer kernel version if that'll help me get my network going. Were you also attempting to use sungem? Might I ask which package containing a 2.6 kernel it was you were using? I know there are several options-- gentoo-sources, benh, dev ppc sources, etc.

eth1 didn't work either.

I just booted with sungem compiled in. I was getting this message before, and it might be useful, but I don't know what it means. When we get to the "* Bringing eth0 up..." SIOCSIFADDR: No such device
eth0: unknown interface: No such device
SIOCSIFBRDADDR: No such device
eth0: unknown interface: No ...

I tried making again with the command you recommended. Unfortunately, I still get the same error when trying to use modprobe. Now I'll try with sungem compiled in.

What else could it be? Something about module dependencies (sungem seems to depend on sungem_phy)?