Re: Install Question(s)
On Mon, Apr 02, 2001 at 02:12:54PM -0400, Roy Wood wrote: > I've downloaded and burned to CD-R the latest 2.2r2 ISO images, but > contrary to what is suggested in the install docs, I can't boot from them > (at least not by holding down "C" when rebooting, though I have to take a > look at open firmware tricks still). Judging from some of the old > postings here, it seems that the best thing to do (since I have no floppy > drive) is to set up a Zip disk and boot from that to get going. just boot into OF, (comand option o f at boot) and enter: boot cd:,\\yaboot that should work, though you may have to enter linux video=ofonly at the resulting boot prompt if your video hardware is unsupported. potato r3 CDs will boot on all newworld machines, past present and future. > As well, I'd be wise to juggle my partitions so I can install yaboot at > the start of the partition table, I believe. yes, you need a 800K type Apple_Bootstrap partition before all the macos partitions, it can be after the driver crap though. read the install docs to find the mkofboot command used to install the bootstrap and make the system bootable. note the installed bootstrap may have the same problem as the CD, if so boot into OF and enter: boot hd:,\\yaboot and upgrade the yaboot pacakge from proposed-updates, then setup /etc/yaboot.conf and run mkofboot (this time without all the command line switches) -- Ethan Benson http://www.alaska.net/~erbenson/ pgpRFsEbrAdTJ.pgp Description: PGP signature
Re: network install problems on 7200/90
This is the problem which I mistakenly labeled as "the MACE driver being completely broken". And since I last tried using it, I speculated that pump was the culprit. Now I'm glad someone confirmed it. The problem does indeed exist in kernel 2.4.2. Adam On Mon, Apr 02, 2001 at 11:33:29AM -0700, Peter Canning wrote: > My experience (using a PowerMac 7300) is a mixture of these two experiences. > What I have seen, using a 2.2.18 kernel I built myself, is: > > (1) if I configure /etc/network/interfaces to use a static IP address, > networking works great, > (2) if I use dhcpcd (I have to get the deb from potato since its been > obsoleted in woody), networking works great, > (3) if I use pump (the only DHCP clients available in woody AFAIK), > networking doesn't work. Pump appears to configure the network correctly > (from what I can see using ifconfig and route), but when I try to ping my > router/dhcp-server/name-server (a 3COM OfficeConnect ISDN lan modem), all > the returned packets appear to get dropped (at least cat /proc/net/dev > shows lots of dropped packets), so ping fails completely. > > It seems to me that it can't be the kernel that is at fault, since it works > fine configured statically, or using dhcpcd. It seems to me that dhcpcd > must being doing something different than pump. My personal preference > would be to see dhcpcd un-obsoleted, and to make it the DHCP client used in > the install disks and base images. Until somebody can figure out how to > make pump work, I don't see why dhcpcd should be obsoleted. > > - Peter Canning > > PS: I haven't used a 2.4 kernel yet, so I can't comment on that. > > At 12:03 AM 3/31/2001, Andrew Sharp wrote: > >MACE seems to work "fine" on all my old worlds: 7200/75, 7600/200, > >8500/200MP. 2.2.18pre21 and 2.2.17. I'm using the TP port. > > > >a > > > > > >Adam Goode wrote: > >> > >> Yes, I have had this problem. The short answer is: MACE is completely > >> broken in recent 2.2 and 2.4 kernels. It seems to be able to send 1-2 > >> packets before failing with "lost a status word". These few initial > >> packets allow DHCP to work ok, while everything else fails. > >> > >> I don't know how to fix it, although I remember using MACE on Linux > >> fine back in 1998 (don't ask me which kernel!), and NetBSD and Mac OS > >> work fine. > >> > >> Perhaps this will spark some discussion to the root cause, as I would > >> like to use Debian on my old 604-upgraded 7500! > >> > >> Adam > >> > >> On Sun, Mar 25, 2001 at 12:19:56AM +0100, Martin Hedenfalk wrote: > >> > Hi all! > >> > > >> > I'm trying to install Debian on my 7200/90. After getting a > >> boot-floppy that > >> > recognized my keyboard (2.2.19, 2000-11-22), I was able to boot into the > >> > install program. Now I wan't to get the drivers/modules from the > >> network. > >> > eth0 (MACE) is configured ok and the default route is ok, but I'm > >> unable to > >> > ping anything except my own IP. And, yes, the cable is plugged in. > >> Networking > >> > worked in MacOS. > >> > > >> > Has anyone had the same problem? > >> > > >> > thanks in advance / Martin > >> > > >> > -- > >> > Martin Hedenfalk <[EMAIL PROTECTED]> > >> > PGP Fingerprint: 4D0F 3A9F 2D5B 12D6 D17D 873E FD62 55A4 A0E3 3C50 > >> > -- > >> > Farnsdick's corollary: > >> > After things have gone from bad to worse, the cycle will repeat > >> itself. > >> > > >> > > >> > -- > >> > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > >> > with a subject of "unsubscribe". Trouble? Contact > >> [EMAIL PROTECTED] > >> > > >> > > >> > >> -- > >> To UNSUBSCRIBE, email to [EMAIL PROTECTED] > >> with a subject of "unsubscribe". Trouble? Contact > >> [EMAIL PROTECTED] > > > > > >-- > >To UNSUBSCRIBE, email to [EMAIL PROTECTED] > >with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > >
Re: Install Question(s)
Roy Wood <[EMAIL PROTECTED]> writes: > I've downloaded and burned to CD-R the latest 2.2r2 ISO images, but > contrary to what is suggested in the install docs, I can't boot from > them (at least not by holding down "C" when rebooting, though I have > to take a look at open firmware tricks still). Apparently the 2.2r2 CDs don't want to boot directly on the newer machines; but you should still be able to boot from CD by going into OpenFirmware (hold Command-Option-O-F on startup), and then typing boot cd:\\yaboot Does that work?
Re: Configure keys for my keyboard
Peter Cordes <[EMAIL PROTECTED]> writes:
> If you haven't tried xkeycaps, then you should. It's great :)
> Unless you need some serious keyboard kung fu, xkeycaps should
> handle all the dirty work and spit out an xmodmap input file. (This
> won't help if you're going to mess with the xkb defs, though.)
Yeah, also, if you've got one of the newer apple keyboards (the full
sized USB "Pro Keyboard") or the Lombard (probably other powerbooks as
well) the attached patch may be useful:
diff -urN xkeycaps-2.46/kbds/all-kbds.h xkeycaps-2.46.huber/kbds/all-kbds.h
--- xkeycaps-2.46/kbds/all-kbds.h Sun Dec 12 20:13:39 1999
+++ xkeycaps-2.46.huber/kbds/all-kbds.h Thu Jan 25 13:04:34 2001
@@ -88,6 +88,27 @@
#endif
#ifdef KBD
+ KBD ("MacProUSB", "Apple", "Pro Keyboard USB (XFree86; US)", 0,
+ &macpro104_geom, macpro104_caps, macpro104_codes, mac_linux_input_map),
+#else
+# include "macpro104-geom.h"
+# include "macpro104-caps.h"
+# include "macpro104-codes.h"
+# include "mac-linux-input-map.h"
+#endif
+
+#ifdef KBD
+ KBD ("MacLombard", "Apple", "PowerBook [Lombard] (XFree86; US)", 0,
+ &maclombard_geom, maclombard_caps, maclombard_codes,
+ mac_linux_input_map),
+#else
+# include "maclombard-geom.h"
+# include "maclombard-caps.h"
+# include "maclombard-codes.h"
+# include "mac-linux-input-map.h"
+#endif
+
+#ifdef KBD
KBD ("MacADB", "Apple", "Standard ADB (NetBSD; US)", 0,
&macstd_geom, macstd_caps, macstd_codes, macstd_map),
#else
diff -urN xkeycaps-2.46/kbds/mac-linux-input-map.h xkeycaps-2.46.huber/kbds/mac-linux-input-map.h
--- xkeycaps-2.46/kbds/mac-linux-input-map.h Wed Dec 31 19:00:00 1969
+++ xkeycaps-2.46.huber/kbds/mac-linux-input-map.h Thu Jan 25 14:14:45 2001
@@ -0,0 +1,131 @@
+#ifndef __MAC_LINUX_INPUT_MAP_H__
+#define __MAC_LINUX_INPUT_MAP_H__
+
+/*
+ * This file was generated from a machine running Linux, with the new
+ * input layer enabled. The input layer translates Apple style scancodes
+ * to PC style scancodes for better compatibility out of the box. We
+ * still need a special map file due to the extra keys on a mac keyboard.
+ *
+ * - Josh Huber <[EMAIL PROTECTED]>, 1/25/2001
+ *
+ */
+
+static const struct default_keycode_map mac_linux_input_map [] = {
+ /* these keys have keycodes but no keysyms in the default map */
+ { 93, 0, { 0 }}, /* F13 */
+ { 133, 0, { 0 }}, /* Left Command */
+ { 134, 0, { 0 }}, /* Right Command */
+
+ { 9, 0, { XK_Escape }},
+ { 10, 0, { XK_1, XK_exclam }},
+ { 11, 0, { XK_2, XK_at }},
+ { 12, 0, { XK_3, XK_numbersign }},
+ { 13, 0, { XK_4, XK_dollar }},
+ { 14, 0, { XK_5, XK_percent }},
+ { 15, 0, { XK_6, XK_asciicircum }},
+ { 16, 0, { XK_7, XK_ampersand }},
+ { 17, 0, { XK_8, XK_asterisk }},
+ { 18, 0, { XK_9, XK_parenleft }},
+ { 19, 0, { XK_0, XK_parenright }},
+ { 20, 0, { XK_minus, XK_underscore }},
+ { 21, 0, { XK_equal, XK_plus }},
+ { 22, 0, { XK_BackSpace }},
+ { 23, 0, { XK_Tab }},
+ { 24, 0, { XK_q, XK_Q }},
+ { 25, 0, { XK_w, XK_W }},
+ { 26, 0, { XK_e, XK_E }},
+ { 27, 0, { XK_r, XK_R }},
+ { 28, 0, { XK_t, XK_T }},
+ { 29, 0, { XK_y, XK_Y }},
+ { 30, 0, { XK_u, XK_U }},
+ { 31, 0, { XK_i, XK_I }},
+ { 32, 0, { XK_o, XK_O }},
+ { 33, 0, { XK_p, XK_P }},
+ { 34, 0, { XK_bracketleft, XK_braceleft }},
+ { 35, 0, { XK_bracketright, XK_braceright }},
+ { 36, 0, { XK_Return }},
+ { 37, ControlMask, { XK_Control_L }},
+ { 38, 0, { XK_a, XK_A }},
+ { 39, 0, { XK_s, XK_S }},
+ { 40, 0, { XK_d, XK_D }},
+ { 41, 0, { XK_f, XK_F }},
+ { 42, 0, { XK_g, XK_G }},
+ { 43, 0, { XK_h, XK_H }},
+ { 44, 0, { XK_j, XK_J }},
+ { 45, 0, { XK_k, XK_K }},
+ { 46, 0, { XK_l, XK_L }},
+ { 47, 0, { XK_semicolon, XK_colon }},
+ { 48, 0, { XK_apostrophe, XK_quotedbl }},
+ { 49, 0, { XK_grave, XK_asciitilde }},
+ { 50, ShiftMask, { XK_Shift_L }},
+ { 51, 0, { XK_backslash, XK_bar }},
+ { 52, 0, { XK_z, XK_Z }},
+ { 53, 0, { XK_x, XK_X }},
+ { 54, 0, { XK_c, XK_C }},
+ { 55, 0, { XK_v, XK_V }},
+ { 56, 0, { XK_b, XK_B }},
+ { 57, 0, { XK_n, XK_N }},
+ { 58, 0, { XK_m, XK_M }},
+ { 59, 0, { XK_comma, XK_less }},
+ { 60, 0, { XK_period, XK_greater }},
+ { 61, 0, { XK_slash, XK_question }},
+ { 62, ShiftMask, { XK_Shift_R }},
+ { 63, 0, { XK_KP_Multiply }},
+ { 64, Mod1Mask, { XK_Alt_L }},
+ { 65, 0, { XK_space }},
+ { 66, LockMask, { XK_Caps_Lock }},
+ { 67, 0, { XK_F1, XK_F11 }},
+ { 68, 0, { XK_F2, XK_F12 }},
+ { 69, 0, { XK_F3, XK_F13 }},
+ { 70, 0, { XK_F4, XK_F14 }},
+ { 71, 0, { XK_F5, XK_F15 }},
+ { 72, 0, { XK_F6, XK_F16 }},
+ { 73, 0, { XK_F7, XK_F17 }},
+ { 74, 0, { XK_F8, XK_F18 }},
+ { 75, 0, { XK_F9, XK_F19 }},
+ { 76, 0, { XK_F10, XK_F20 }},
+ { 77, Mod2Mask, { XK_Num_Lock }},
+ { 78, Mod5Mask, { XK_Scroll_Lock }},
+ { 79, 0, { XK_KP_7 }},
+ { 80, 0, { XK_KP_8 }},
+ { 81, 0, { XK_KP_9 }},
+ { 82, 0, { XK_KP_Subtract }},
+ { 83, 0, { XK_KP_4 }},
+ { 84, 0, { XK_KP_5 }},
+ { 85, 0, { XK_KP_
Re: Compiling Lame to DebianPPC
On Mon, Apr 02, 2001 at 09:48:51PM +0100, Jarkko Pienim?ki wrote: > do i need some special arguments when i want to compile lame for > DebianPPC? I don't think so... I'm pretty sure all I did was ./configure, make, make install. That was for LAME 3.88. Have you tried already and you're having problems? -- Grant Hollingworth / [EMAIL PROTECTED] / http://okcomputer.antiflux.org
Make X function properly
Greetings, I have successfully installed Debian 2.2 R2 on my G4 However when X boots up, the resolution is very bad (only 640x480) and the mouse doesn't work. (however, it works with gpm) I have an ATI Rage 128 w /16 mb ram so it's should be supported. I have tried making modifications directly to the xf86config file (since I couldn't find any configuration tool) but no luck. Does anyone know how I can configure X to work properly on my G4? (I am not a newbie to X at all on i386 machines) Thanks --Yan
External Monitor under Pismo
Hey All, So after 7 months of flailing I finally got my Pismo to run it's external monitor port, yeah!!! 3 days before I had a talk to give about our OpenSource project, I realized I was going to be using OpenOffice under linux, and I couldn't actually drive a projector... So after I got done panicing I hit google. I find a link on the YDL lists about the 'mirror' program that appears to have been originally written by Paul Mackeras. It gives me the functionality I need, but unfortunately it doesn't seem to work with 2.4 kernels, only 2.2. The program is doing some pretty low-level memory mojo which I am clueless about. Could someone slightly wiser point out what would change between 2.2 and 2.4 that would cause this to break? Is it the base memory offset for the framebuffer? Cheers! jas. mirror2.c Description: Binary data
Re: network install problems on 7200/90
On Mon, Apr 02, 2001 at 11:33:29AM -0700, Peter Canning wrote: > It seems to me that it can't be the kernel that is at fault, since it works > fine configured statically, or using dhcpcd. It seems to me that dhcpcd > must being doing something different than pump. My personal preference > would be to see dhcpcd un-obsoleted, and to make it the DHCP client used in > the install disks and base images. Until somebody can figure out how to > make pump work, I don't see why dhcpcd should be obsoleted. dhcpcd has moved to the dhcp-client package. -- #define X(x,y) x##y Peter Cordes ; e-mail: X([EMAIL PROTECTED] , ns.ca) "The gods confound the man who first found out how to distinguish the hours! Confound him, too, who in this place set up a sundial, to cut and hack my day so wretchedly into small pieces!" -- Plautus, 200 BCE
Compiling Lame to DebianPPC
do i need some special arguments when i want to compile lame for DebianPPC? regards jarpie
Re: network install problems on 7200/90
My experience (using a PowerMac 7300) is a mixture of these two experiences. What I have seen, using a 2.2.18 kernel I built myself, is: (1) if I configure /etc/network/interfaces to use a static IP address, networking works great, (2) if I use dhcpcd (I have to get the deb from potato since its been obsoleted in woody), networking works great, (3) if I use pump (the only DHCP clients available in woody AFAIK), networking doesn't work. Pump appears to configure the network correctly (from what I can see using ifconfig and route), but when I try to ping my router/dhcp-server/name-server (a 3COM OfficeConnect ISDN lan modem), all the returned packets appear to get dropped (at least cat /proc/net/dev shows lots of dropped packets), so ping fails completely. It seems to me that it can't be the kernel that is at fault, since it works fine configured statically, or using dhcpcd. It seems to me that dhcpcd must being doing something different than pump. My personal preference would be to see dhcpcd un-obsoleted, and to make it the DHCP client used in the install disks and base images. Until somebody can figure out how to make pump work, I don't see why dhcpcd should be obsoleted. - Peter Canning PS: I haven't used a 2.4 kernel yet, so I can't comment on that. At 12:03 AM 3/31/2001, Andrew Sharp wrote: MACE seems to work "fine" on all my old worlds: 7200/75, 7600/200, 8500/200MP. 2.2.18pre21 and 2.2.17. I'm using the TP port. a Adam Goode wrote: Yes, I have had this problem. The short answer is: MACE is completely broken in recent 2.2 and 2.4 kernels. It seems to be able to send 1-2 packets before failing with "lost a status word". These few initial packets allow DHCP to work ok, while everything else fails. I don't know how to fix it, although I remember using MACE on Linux fine back in 1998 (don't ask me which kernel!), and NetBSD and Mac OS work fine. Perhaps this will spark some discussion to the root cause, as I would like to use Debian on my old 604-upgraded 7500! Adam On Sun, Mar 25, 2001 at 12:19:56AM +0100, Martin Hedenfalk wrote: > Hi all! > > I'm trying to install Debian on my 7200/90. After getting a boot-floppy that > recognized my keyboard (2.2.19, 2000-11-22), I was able to boot into the > install program. Now I wan't to get the drivers/modules from the network. > eth0 (MACE) is configured ok and the default route is ok, but I'm unable to > ping anything except my own IP. And, yes, the cable is plugged in. Networking > worked in MacOS. > > Has anyone had the same problem? > > thanks in advance / Martin > > -- > Martin Hedenfalk <[EMAIL PROTECTED]> > PGP Fingerprint: 4D0F 3A9F 2D5B 12D6 D17D 873E FD62 55A4 A0E3 3C50 > -- > Farnsdick's corollary: > After things have gone from bad to worse, the cycle will repeat itself. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Install Question(s)
I'm starting out installing Debian on my PowerMac G4 450, DVD ROM, Zip Drive. I have MacOS 9.0.4 already installed on the hard drive, which, by the way, is partitioned into 4 partitions, since I expected to install Linux on here at some point. I've downloaded and burned to CD-R the latest 2.2r2 ISO images, but contrary to what is suggested in the install docs, I can't boot from them (at least not by holding down "C" when rebooting, though I have to take a look at open firmware tricks still). Judging from some of the old postings here, it seems that the best thing to do (since I have no floppy drive) is to set up a Zip disk and boot from that to get going. As well, I'd be wise to juggle my partitions so I can install yaboot at the start of the partition table, I believe. Any comments or words of advice at this point, folks? By the way, I'm very comfortable with my RedHat x86 box, and have survived all sorts of fun there in relation to funky hardware, so I'm not about to start whining that this is not just a one-click install, boo hoo. -Roy
Debian-PPC on display (was: Re: Thanks DebianPPC Porters + Writers!)
On Wed, Mar 28, 2001 at 02:17:26AM -0700, Nate Duehr wrote: > I just wanted to publically thank you all for your hard work on > Debian-PPC. I just loaded up the iMac DV SE I was having trouble with > back during the early days of Potato, and 2.2r2 is a breeze for an > experienced Debian-head who wanted to try something new. The new docs > linked from the PPC pages at www.debian.org (Ethan's and others...) are > very helpful. > > Still diddling with X and trying to get the mouse to work (it said > something about "send mail to debian-powerpc, your Apple hardware is not > recognized" or somesuch, but I'm also about 2000 messages behind in my > debian-ppc reading, so I figured it's probably already in here > somewhere... and I need to catch up on my reading I suppose. > > But seriously, NICE JOB to you and all the other PPC porters! > > As a direct result of your hard work, the Debian area/booth at > the Colorado Linux Info Quest [www.thecliq.org] later this week > will have an iMac DV SE there running the Debian PPC port for folks to > see! I'm sure it will attract attention! > > Congrats, and thanks again! Just a follow-up, we had a Debian-PPC machine on display (the iMac DV SE mentioned above) at the Colorado Linux Info Quest Debian booth Friday. (Along with Debian on PA-RISC, Sparc, and ho-hum... i386 of course.) :-) -- Nate Duehr <[EMAIL PROTECTED]> GPG Key fingerprint = DCAF 2B9D CC9B 96FA 7A6D AAF4 2D61 77C5 7ECE C1D2 Public Key available upon request, or at wwwkeys.pgp.net and others.
Re: Configure keys for my keyboard
* Arne Scheffler <[EMAIL PROTECTED]>, 20010401 22:41 +0200: > Hi, > there are some keys on my keyboard which xkb don't map > right. Now I want to know the keycodes. But I don't know > which tool to use. Is there a tool I can start, press the > key and see which keycode it produce ? > > Thanks for any help > > arne showkey on the consoles, xev (xcontrib) for X. Andre Berger[EMAIL PROTECTED]
