[gentooppc-user] Fwd: Re: Gentoo-ppc Newbie Questions

[Calum Selkirk]

haven't seen this on the list as yet and so i'm reposting ..

----- Forwarded message from Calum Selkirk <cselkirk@g.o> -----

> Date: Tue, 8 Oct 2002 11:53:35 +0200
> From: Calum Selkirk <cselkirk@g.o>
> Reply-To: Calum Selkirk <cselkirk@g.o>
> To: gentooppc-user@g.o
> Subject: Re: Gentoo-ppc Newbie Questions

> * Marcio Luis Teixeira [marciot@×××××××××××××××.edu] [2002-10-06 16:16 -0600]:
>
> > I've recently successfully got Gentoo PPC running on my old PowerBook
> > 3400c.  It compiled for five days straight (whew!) but eventually I
> > had a working system. It's looking good so far and seems to work
> > better than other precompiled distributions (my system now goes to
> > sleep without crashing [..]
>
> this would be the pll, mclk, issue (with older kernels not establishing the
> correct values for the ATI card). This hit other Powerbook models also
> (though much less than it hit the 3500). Sometime in the not do distant
> past atyfb was revamped and so there is no longer the need for users to
> pass pll and mclk values to the kernel (via kernel args). The 3500 not
> crashing on sleep is the upshot of this.
>
> > I apologize for posting all this to the mailing list. I'm sure there
> > are more appropriate places for each of these items, but I don't yet
> > know what they are. If anything, I would appreciate it if you could
> > point me in the right direction :)
>
> heh .. no no .. here is definitely an appropriate place (in fact, I for
> one would like to see more traffic on this list in general, in order to
> build up some kind of knowledge base).
>
> [..]
> > 1) The docs for the PPC Install say that to enable mouse button
> > emulation you must enter into /etc/conf.d/local.start the following
> > lines:
> >
> >    echo "1" > /proc/sys/dev/mac_hid/mouse_button_emulation
> >    echo "87" > /proc/sys/dev/mac_hid/mouse_button2_keycode
> >    echo "88" > /proc/sys/dev/mac_hid/mouse_button2_keycode
> >
> > That wasn't working for me, so I changed the third line to
> > "mouse_button3_keycode". Seems to work now, so I'm thinking that this
> > may be a bug in the docs. Is it?
>
> yes .. but in more ways than you might think. The whole concept of
> echoing digits into proc is depreciated in favor of sysctl (see:
> /usr/src/linux/Documentation/sysctl/README). All these values should
> be set up via a /etc/sysctl.conf (and note we *do* CONFIG_SYSCTL=y
> for this very reason).
>
> This was reported as a bug to rajiv some weeks .. see:
>
> http://bugs.gentoo.org/show_bug.cgi?id=8118
>
> An /etc/sysctl.conf with the following values will achive the same
> effect.
>
> # Enable mouse button emulation
> dev.mac_hid.mouse_button_emulation = 1
> # Set 2nd button to 87 - F11
> dev.mac_hid.mouse_button2_keycode = 87
> # Set 3rd button to 88 - F12
> dev.mac_hid.mouse_button3_keycode = 88
>
> > 2) In the past, to get PCMCIA to work on my PowerBook, I had to change
> > the default settings in /etc/pcmcia/config.opts as such:
> >
> >    # Settings for the PowerBook:
> >    include port 0x100-0x4ff, port 0x1000-0x17ff
> >    include memory 0x80000000-0x80ffffff
> >
> > This is directly from the PCMCIA How-To:
> >
> >     http://pcmcia-cs.sourceforge.net/ftp/doc/PCMCIA-HOWTO-2.html#ss2.5
> >
> > I'm wondering if a) this still applies to Gentoo, and if so b) whether
> > this should be part of the installation guide (at least for PowerBook
> > users).
>
> These are the default values when you install pcmcia-cs on gentoo.
>
> zsh% cat /etc/pcmcia/config.opts | egrep "^inc"
> include port 0x1000-0x1fff
> include memory 0x90000000-0x9003ffff
>
> The presence of two ports in the PCMCIA-HOWTO suggest a 3500 or Wallstreet
> (whereas the defaults seem to be targeting more recent models). If these
> worked for you in the past i would suggest sticking with them (and
> please report how you get on).
>
> > 3) I had a hell of a time figuring out how to configure my mouse under
> > XFree86. Would it make sense to add a note about this to the PPC
> > install instructions? Basically, I had to set the mouse protocol to
> > "PS/2" and the device to "/dev/input/mice." This is definitely not
> > what I had expected, as in other distros I had used "BusMouse" and
> > "/dev/mouse". Again, I wonder if the PPC Install guide should include
> > such info for PowerBook users.
>
> Sometime around 2.2.17 there were changes make to the (ppc) kernel
> known infamously as "the new input layer" or "mac_hid". These changes
> depreciated the old ADB keycodes in favor of linux keycodes.  However
> the old method was (and still is) supported. The upshot of this was lots
> of chickens running around all using different keycodes and clucking
> furiously on the various list of the time about what needed to be
> enabled/disabled in the kernel, what to echo in to /proc and most
> famously "my keyboard is b0rked". Gentoo took a rather novel approach to
> this (though we still encountered some users who, using non-gentoo
> kernels, also exclaimed "b0rked") by disabling CONFIG_MAC_ADBKEYCODES
> altogether, and gerk wrote Xeasyconf which would set the option "Protocol"
> to "IMPS/2" in /etc/X11/XF86Config-4. Of course the situation with the
> new input layer is still not altogether behind us, but we have done our
> best to ensure that users don't encounter this (using XF86Config's from
> other installs aside). Something for the doc's? .. maybe .. but we can
> not cover every piece of legacy code out there, and IMO it's best we
> move on.
>
> > 4) Once I do "kdm" to start the window manager, I am able to log in
> > correctly.  But, once I log out, the mouse stops working and freezes.
> > I have to hit "Alt-E" to restart the X server before logging in again.
>
> ALT-E? (maybe you mean ALT-c?) .. no idea about this, i avoid {k,g,x)dm
> like the plague ;)
>
> Tip from an old shell geezer:
>
> In your .bash_profile or .zprofile (dependent on what your shell is).
>
> [ -z "$DISPLAY" ] && [ -n `tty | grep tty` ] && exec startx
>
> Then you can skip kdm, and fancy splash screens altogether (unless
> there is some initialization kdm performs that i'm unaware of).
>
> > 5) My CD-ROM drive does not work. At startup I get:
> >
> > hdc: packet command error: status=0x51 { DriveReady SeekComplete Error }
> > hdc: packet command error: error=0x54
> > ATAPI device hdc:
> >   Error: Illegal request -- (Sense key=0x05)
> >   Invalid field in command packet -- (asc=0x24, ascq=0x00)
> >   The failed "Start/Stop Unit" packet command was:
> >   "1b 00 00 00 03 00 00 00 00 00 00 00 "
> > cdrom: open failed.
>
> humm .. doesn't work at all? How did you install? Are you able to mount
> CD's? What errors do you get when mounting? Does /dev/cdroms/cdrom0
> exist?
>
> > In other distos, I think I had to use SCSI emulation for this drive,
> > so I think that may be my problem (still haven't had the time to
> > research how to do this under Gentoo).
>
>
> > Grief with Emerge:
> > --------------------
> >
> > 6) I was able to successfully emerge "alsa-driver" and "alsa-lib", but
> > when I try emerging "alsa-utils" (so I can use "amixer" to set the
> > volume, as per the desktop configuration guide), I get:
> >
> > emerge: all ebuilds that could satisfy "alsa-utils" have been masked.
> >
> > What gives?
>
> The package is masked for testing (see: /usr/portage/profiles/package.mask)
>
> It is possible to override this by specifying the full path of the ebuild:
>
> emerge /usr/portage/media-sound/alsa-utils/alsa-utils-0.9.0_rc3.ebuild
>
> > 7) When I try emerging "sketch", the emerge fails. Here's what I get:
> >
> >    >>> emerge media-gfx/sketch-0.6.12-r1 to /
> >    ... blah, blah ...
> >    >>> md5 ;-) sketch-0.6.12.tar.gz
> >    >>> Unpacking source...
> >    >>> Unpacking sketch-0.6.12.tar.gz
> >    >>> Source unpacked.
> >    looking for include dir for Imaging.h under /usr/include/python2.2
> >    Imaging.h not found under /usr/include/python2.2 !
> >
> >    !!! ERROR: The ebuild did not complete successfully.
> >    !!! Function src_compile, Line 27, Exitcode 1
> >    !!! setup.py configure failed
> >
> > I guessed that perhaps "sketch" depended on the python Imaging
> > library, so I tried "emerge dev-python/Imaging" and I get the dreaded
> > masked message:
> >
> > merge: all ebuilds that could satisfy "dev-python/Imaging" have been
> > masked.
>
> specify the full path to dev-python/Imaging-1.1.2-r2.ebuild and try
> again to merge sketch. Imaging-1.1.2-r2.ebuild is not KEYWORDed ppc.
>
> best
>
> cal

----- End forwarded message -----