Subject: Re: yellowdog-general Digest 25 Jan 2001 03:35:47 -0000 Issue 332
From: Hollis R Blanchard (hollis+@andrew.cmu.edu)
Date: Thu Jan 25 2001 - 13:49:53 MST
On Fri, 26 Jan 2001, bph wrote:
> Please remove me from this list!
Please below to find out exactly how to unsubscribe yourself!
-Hollis
> > yellowdog-general-digest-help@lists.yellowdoglinux.com wrote:
> >
> > yellowdog-general Digest 25 Jan 2001 03:35:47 -0000 Issue 332
> >
> > Topics (messages 9068 through 9097):
> >
> > 2.4 Kernel & Xfree-4.0.1
> > 9068 by: "Paul J. Lucas" <pauljlucas@mac.com>
> > 9070 by: Donnell <donnell@quepasa.com>
> > 9072 by: Ole Kristoffer Apeland <oleap@student.matnat.uio.no>
> > 9073 by: Vincent Favre-Nicolin <Vincent.Favre-Nicolin@cryst.unige.ch>
> > 9074 by: Iain Stevenson <iain@IainStevenson.com>
> > 9075 by: Larry Kollar <kollar@alltel.net>
> > 9076 by: Stefan Jeglinski <jeglin@4pi.com>
> > 9078 by: "Neil Jolly" <njolly@home.com>
> > 9079 by: "Neil Jolly" <njolly@home.com>
> > 9081 by: "Paul J. Lucas" <pauljlucas@mac.com>
> > 9083 by: FT Rathore <mawali@news.icns.com>
> > 9087 by: "Paul J. Lucas" <pauljlucas@mac.com>
> > 9095 by: Stefan Jeglinski <jeglin@4pi.com>
> > 9097 by: "Paul J. Lucas" <pauljlucas@mac.com>
> >
> > Video on dual G4
> > 9069 by: adriaan@etl.go.jp (Adriaan Tijsseling)
> >
> > MOL and Audio CDs (yes, the usual questions but the usual answers don't seem to work ;-)
> > 9071 by: Joss Winn <joss@josswinn.org>
> >
> > iMac DV Install Prob
> > 9077 by: "Michael Baldwin" <michael@westpole.com>
> > 9092 by: Jonathan Bertsch <bertsch.13@osu.edu>
> >
> > MOL and Audio CDs
> > 9080 by: Hollis R Blanchard <hollis+@andrew.cmu.edu>
> >
> > HELP! Long ping times under Yellow Dog Linux
> > 9082 by: Gawain Reifsnyder <gawain@guitar.net>
> >
> > drive initialization problem
> > 9084 by: antadam <antadam@lunch-lady.com>
> >
> > yup update problem
> > 9085 by: Bryan Stillwell <bstill@terraplex.com>
> > 9088 by: "Philip Good" <phil@redplanetx.com>
> > 9090 by: Bryan Stillwell <bstill@terraplex.com>
> > 9096 by: Patrick Callahan <pac1@tiac.net>
> >
> > @: yup update problem
> > 9086 by: Bryan Stillwell <bstill@terraplex.com>
> >
> > The BriQ
> > 9089 by: christopher.murtagh@wcg.mcgill.ca
> > 9093 by: "Sean O. Denney" <sdenney@cise.ufl.edu>
> >
> > Pismo mirror program
> > 9091 by: "Philip Good" <phil@go2taichi.com>
> >
> > MOL help needed
> > 9094 by: Sam Moore <samiwas@macconnect.com>
> >
> > Administrivia:
> >
> > To subscribe to the digest, e-mail:
> > yellowdog-general-digest-subscribe@lists.yellowdoglinux.com
> >
> > To unsubscribe from the digest, e-mail:
> > yellowdog-general-digest-unsubscribe@lists.yellowdoglinux.com
> >
> > To post to the list, e-mail:
> > yellowdog-general@lists.yellowdoglinux.com
> >
> > ----------------------------------------------------------------------
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: Tue, 23 Jan 2001 21:43:43 -0800 (PST)
> > From: "Paul J. Lucas" <pauljlucas@mac.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: Yellowdog Linux Mail List <yellowdog-general@lists.yellowdoglinux.com>
> > CC: linuxppc mail list <linuxppc-user@lists.linuxppc.org>
> >
> > On Tue, 23 Jan 2001, Neil Jolly wrote:
> >
> > > I've compiled the 2.4 kernel with support for rage 128 & 64 (among other
> > > things), the kernel boots into runlevel 3 alright, but as soon as i startx or
> > > change to runlevel 5 the screen blanks and the system appears to freeze
> >
> > Although you neglected to mention what machine and boot method
> > you are using (always, ALWAYS say at least what machine), it's
> > my understanding that if you are using BootX, it leaves the PCI
> > bus in a weird state that XFree86 4.x isn't happy with.
> > (XFree86 3.x doesn't care). Hence, if you want to use XFree86
> > 4.x, you MUST use yaboot. If you're on an old-world machine,
> > this implies that you can not use XFree86 4.x.
> >
> > If anybody knows the above to be false (by actually running
> > XFree86 4.x on a machine booted with yaboot, please correct me).
> >
> > - Paul
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: Wed, 24 Jan 2001 02:21:18 -0500
> > From: Donnell <donnell@quepasa.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > "Paul J. Lucas" wrote:
> > >
> > > On Tue, 23 Jan 2001, Neil Jolly wrote:
> > >
> > > > I've compiled the 2.4 kernel with support for rage 128 & 64 (among other
> > > > things), the kernel boots into runlevel 3 alright, but as soon as i startx or
> > > > change to runlevel 5 the screen blanks and the system appears to freeze
> > >
> > > Although you neglected to mention what machine and boot method
> > > you are using (always, ALWAYS say at least what machine), it's
> > > my understanding that if you are using BootX, it leaves the PCI
> > > bus in a weird state that XFree86 4.x isn't happy with.
> > > (XFree86 3.x doesn't care). Hence, if you want to use XFree86
> > > 4.x, you MUST use yaboot. If you're on an old-world machine,
> > > this implies that you can not use XFree86 4.x.
> > >
> > > If anybody knows the above to be false (by actually running
> > > XFree86 4.x on a machine booted with yaboot, please correct me).
> > >
> > > - Paul
> >
> > For whatever it's worth, I've been experimenting with Debian GNU/Linux
> > (kernel 2.2.17 ppc) and XFree86 4.0.2 on my home machine. I use BootX
> > with my setup--a PowerBase 180 w/Sonnet G3/L2 upgrade and a 2MB ATI
> > Mach64 video card.
> >
> > .Donnell
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: Wed, 24 Jan 2001 08:53:38 +0100 (MET)
> > From: Ole Kristoffer Apeland <oleap@student.matnat.uio.no>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: <yellowdog-general@lists.yellowdoglinux.com>
> >
> > On Wed, 24 Jan 2001, Donnell wrote:
> >
> > > "Paul J. Lucas" wrote:
> > > >
> > > > On Tue, 23 Jan 2001, Neil Jolly wrote:
> > > >
> > > > > I've compiled the 2.4 kernel with support for rage 128 & 64 (among other
> > > > > things), the kernel boots into runlevel 3 alright, but as soon as i startx or
> > > > > change to runlevel 5 the screen blanks and the system appears to freeze
> > > >
> > > > Although you neglected to mention what machine and boot method
> > > > you are using (always, ALWAYS say at least what machine), it's
> > > > my understanding that if you are using BootX, it leaves the PCI
> > > > bus in a weird state that XFree86 4.x isn't happy with.
> > > > (XFree86 3.x doesn't care). Hence, if you want to use XFree86
> > > > 4.x, you MUST use yaboot. If you're on an old-world machine,
> > > > this implies that you can not use XFree86 4.x.
> > > >
> > > > If anybody knows the above to be false (by actually running
> > > > XFree86 4.x on a machine booted with yaboot, please correct me).
> > > >
> > > > - Paul
> > >
> > > For whatever it's worth, I've been experimenting with Debian GNU/Linux
> > > (kernel 2.2.17 ppc) and XFree86 4.0.2 on my home machine. I use BootX
> > > with my setup--a PowerBase 180 w/Sonnet G3/L2 upgrade and a 2MB ATI
> > > Mach64 video card.
> > >
> > > .Donnell
> >
> > I'm using YDL on a Performa 6400. I also use BootX with my setup - 603e
> > 180 and ATI orion (rage 128). I boot perfectly into X (4.0.2) with 24 bit
> > color. The only difference is that i use the standard kernel (the one that
> > came with the YDL cd) 2.2.18 -I think.
> >
> > Ole K.
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: Wed, 24 Jan 2001 09:21:29 +0100
> > From: Vincent Favre-Nicolin <Vincent.Favre-Nicolin@cryst.unige.ch>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com, linuxppc-user@lists.linuxppc.org
> >
> > > Although you neglected to mention what machine and boot method
> > > you are using (always, ALWAYS say at least what machine), it's
> > > my understanding that if you are using BootX, it leaves the PCI
> > > bus in a weird state that XFree86 4.x isn't happy with.
> > > (XFree86 3.x doesn't care). Hence, if you want to use XFree86
> > > 4.x, you MUST use yaboot. If you're on an old-world machine,
> > > this implies that you can not use XFree86 4.x.
> > >
> > That last point at least is wrong. You *can* use XFree
> > 4.0x with oldWorld machines and BootX. I use XFree 4.02 with
> > my 3dfx cards without problem. And I have received emails
> > from several other persons in the same configuration (XFree
> > 4.0x, 3dfx, BootX), and they are fine, too.
> > So I do not know if the 'weird PCI state' when leaving
> > BootX also applies to OldWorld Machines, but you can
> > definitly use BootX with XFree 4.0x.
> >
> > --
> > Vincent Favre-Nicolin http://www.unige.ch/crystal/favrev/
> > Laboratoire de Cristallographie Phone: +41 (22) 702 60 79
> > 24 quai Ernest-Ansermet
> > CH-1211 Geneva 4, Switzerland Fax: +41 (22) 702 61 08
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: Wed, 24 Jan 2001 10:27:02 +0000
> > From: Iain Stevenson <iain@IainStevenson.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: <yellowdog-general@lists.yellowdoglinux.com>
> >
> > I have a 9600/200 with a Rage Orion (128) card. It runs BootX and XFree86
> > 4.01 perfectly with the 2.2.18 kernel. The linuxppc_2_4 kernel boots and
> > XFree8 4.01 works fine with this too - unfortunately the networking doesn't
> > work properly with this bleeding edge kernel.
> >
> > Iain
> >
> > on 24/1/01 5:13 am, Neil Jolly at njolly@home.com wrote:
> >
> > > I've compiled the 2.4 kernel with support for rage 128 & 64 (among other
> > > things), the kernel boots into runlevel 3 alright, but as soon as i startx or
> > > change to runlevel 5 the screen blanks and the system appears to freeze
> > > (haven't tried sshing in from anywhere yet). Anybody know if I have to run
> > > Xfree 4.0.2 or some such thing. X works great under 2., and there are no
> > > errors in the log either. The log just ends partway through.
> > >
> > > Neil Jolly
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: Wed, 24 Jan 2001 07:07:52 -0500
> > From: Larry Kollar <kollar@alltel.net>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: Neil Jolly <njolly@home.com>,
> > "Yellowdog Linux Mail List" <yellowdog-general@lists.yellowdoglinux.com>
> > CC: "linuxppc mail list" <linuxppc-user@lists.linuxppc.org>
> >
> > Neil Jolly wrote:
> >
> > >I've compiled the 2.4 kernel with support for rage 128 & 64 (among other
> > >things), the kernel boots into runlevel 3 alright, but as soon as i startx or
> > >change to runlevel 5 the screen blanks and the system appears to freeze
> > >(haven't tried sshing in from anywhere yet).
> >
> > Have you tried doing Cmd-Ctrl-F1 to get back to the console after the
> > system "appears to freeze"?
> >
> > I have a similar problem, only from the opposite end and not all
> > the time (in fact, it hasn't happened at all recently) -- the system
> > appears to hang, on occasion, when I log out of an X session. I can
> > flip back to console 1, log in, and kill the kdm process. This seems
> > to give X the slap upside the head that it needs, and I'll get the
> > login screen.
> >
> > Even switching to the text console, then back to the X screen, is
> > sometimes enough to wake it up.
> >
> > In your case, you may find that your computer hasn't crashed &
> > the console screen has a list of errors that an expert like Ani
> > or some of the others can use to determine what's going wrong.
> >
> > >Anybody know if I have to run Xfree 4.0.2 or some such
> > >thing. X works great under 2., and there are no
> > >errors in the log either. The log just ends partway through.
> >
> > By "under 2." I assume you meant kernel 2.2.x? At least you have
> > a good fallback position. :-) Post your hardware info, and be
> > ready to hand out your 2.4 .config file to someone who knows what
> > they're doing (that's not me). It may be something as simple as
> > disabling framebuffer support during the config.
> >
> > Larry
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: Wed, 24 Jan 2001 09:14:55 -0500
> > From: Stefan Jeglinski <jeglin@4pi.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > > Although you neglected to mention what machine and boot method
> > > you are using (always, ALWAYS say at least what machine), it's
> > > my understanding that if you are using BootX, it leaves the PCI
> > > bus in a weird state that XFree86 4.x isn't happy with.
> > > (XFree86 3.x doesn't care). Hence, if you want to use XFree86
> > > 4.x, you MUST use yaboot. If you're on an old-world machine,
> > > this implies that you can not use XFree86 4.x.
> > >
> > > If anybody knows the above to be false (by actually running
> > > XFree86 4.x on a machine booted with yaboot, please correct me).
> >
> > I run 402 and BootX on 2 9500-class machines with no problems. I have
> > a 6500 with BootX for which I cannot launch X402 without fatal errors
> > involving the atimisc module, regardless of whether I install from
> > available rpms or build from source. That one is really aggravating
> > me, because there appears to be -no- resolution to the issue. If
> > anyone is running X402 on a 6500, I really want to talk to you!
> >
> > Stefan Jeglinski
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: 24 Jan 2001 15:24:00 -0000
> > From: "Neil Jolly" <njolly@home.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> > CC: linuxppc-user@lists.linuxppc.com
> >
> > >
> > > Neil Jolly wrote:
> > >
> > > >I've compiled the 2.4 kernel with support for rage 128 & 64 (among
> > other
> > > >things), the kernel boots into runlevel 3 alright, but as soon as i
> > startx or
> > > >change to runlevel 5 the screen blanks and the system appears to
> > freeze
> > > >(haven't tried sshing in from anywhere yet).
> > >
> > >
> > > Have you tried doing Cmd-Ctrl-F1 to get back to the console after the
> > > system "appears to freeze"?
> > Yeah I tried that as well, and can't even get back to a console.
> > >
> > > I have a similar problem, only from the opposite end and not all
> > > the time (in fact, it hasn't happened at all recently) -- the system
> > > appears to hang, on occasion, when I log out of an X session. I can
> > > flip back to console 1, log in, and kill the kdm process. This seems
> > > to give X the slap upside the head that it needs, and I'll get the
> > > login screen.
> > >
> > > Even switching to the text console, then back to the X screen, is
> > > sometimes enough to wake it up.
> > >
> > >
> > > In your case, you may find that your computer hasn't crashed &
> > > the console screen has a list of errors that an expert like Ani
> > > or some of the others can use to determine what's going wrong.
> > >
> > >
> > >
> > > >Anybody know if I have to run Xfree 4.0.2 or some such
> > > >thing. X works great under 2., and there are no
> > > >errors in the log either. The log just ends partway through.
> > >
> > > By "under 2." I assume you meant kernel 2.2.x? At least you have
> > > a good fallback position. :-) Post your hardware info, and be
> > > ready to hand out your 2.4 .config file to someone who knows what
> > > they're doing (that's not me). It may be something as simple as
> > > disabling framebuffer support during the config.
> > >
> > Sorry about that. It's supposed to read the 2.2.18 kernel. I'd be happy
> > to hand out my .config from the 2.4 kernel, and my XF86Config to any one
> > who has an idea of what might be the problem.
> > > Larry
> > >
> > >
> > >
> > >
> > >
> >
> > "Computers let you make more mistakes faster than any other
> > invention in human history, with the possible exception of
> > handguns and tequila."
> >
> > Mitch Radcliffe
> >
> > Neil Jolly
> > ----------------------------------------------------------
> > http://www.members.home.net/njolly/xppc/index.htm
> > ----------------------------------------------------------
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: 24 Jan 2001 15:36:22 -0000
> > From: "Neil Jolly" <njolly@home.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: "Paul J. Lucas" <pauljlucas@mac.com>,
> > Yellowdog Linux Mail List <yellowdog-general@lists.yellowdoglinux.com>,
> > linuxppc mail list <linuxppc-user@lists.linuxppc.org>
> >
> > >
> > > On Tue, 23 Jan 2001, Neil Jolly wrote:
> > >
> > > > I've compiled the 2.4 kernel with support for rage 128 & 64 (among
> > other
> > > > things), the kernel boots into runlevel 3 alright, but as soon as i
> > startx or
> > > > change to runlevel 5 the screen blanks and the system appears to
> > freeze
> > >
> > > Although you neglected to mention what machine and boot method
> > > you are using (always, ALWAYS say at least what machine), it's
> > > my understanding that if you are using BootX, it leaves the PCI
> > > bus in a weird state that XFree86 4.x isn't happy with.
> > > (XFree86 3.x doesn't care). Hence, if you want to use XFree86
> > > 4.x, you MUST use yaboot. If you're on an old-world machine,
> > > this implies that you can not use XFree86 4.x.
> > >
> > Yes I probably should mention that I'm using a biege G3 wth an at1 rage
> > 128 Nexxus video card ( the stock rage 64 is still installed, but not
> > being used), and that I'm using bootx. However my main concern here was
> > is XFree86-4.0.1 compatible with the 2.4 kernel. I suspect the problem
> > may lie with the Nexxus video card.
> >
> > > If anybody knows the above to be false (by actually running
> > > XFree86 4.x on a machine booted with yaboot, please correct me).
> > >
> > Definately false, as I've been running XFree86-4.0.1 for a month or so
> > now with no problem.
> >
> > "Computers let you make more mistakes faster than any other
> > invention in human history, with the possible exception of
> > handguns and tequila."
> >
> > Mitch Radcliffe
> >
> > Neil Jolly
> > ----------------------------------------------------------
> > http://www.members.home.net/njolly/xppc/index.htm
> > ----------------------------------------------------------
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: Wed, 24 Jan 2001 08:44:05 -0800 (PST)
> > From: "Paul J. Lucas" <pauljlucas@mac.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> > CC: linuxppc-user@lists.linuxppc.org
> >
> > On Wed, 24 Jan 2001, Vincent Favre-Nicolin wrote:
> >
> > > That last point at least is wrong. You *can* use XFree
> > > 4.0x with oldWorld machines and BootX. I use XFree 4.02 with
> > > my 3dfx cards without problem. And I have received emails
> > > from several other persons in the same configuration (XFree
> > > 4.0x, 3dfx, BootX), and they are fine, too.
> > > So I do not know if the 'weird PCI state' when leaving
> > > BootX also applies to OldWorld Machines, but you can
> > > definitly use BootX with XFree 4.0x.
> >
> > Well, here's the thread:
> >
> > http://x54.deja.com/[ST_rn=ps]/threadmsg_ct.xp?AN=704644183.1&mhitnum=4&CONTEXT=980354233.1761542218
> >
> > Is this guy wrong?
> >
> > - Paul
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: Wed, 24 Jan 2001 13:09:40 -0600 (EST)
> > From: FT Rathore <mawali@news.icns.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: "Paul J. Lucas" <pauljlucas@mac.com>
> > CC: Yellowdog Linux Mail List <yellowdog-general@lists.yellowdoglinux.com>,
> > linuxppc mail list <linuxppc-user@lists.linuxppc.org>
> >
> > Hi
> > I am using mine with XF86-4.0.2, linux-2.4.1-pre7 with BootX on my Imac
> > with 333MHZ Green one.
> > FT
> >
> > On Tue, 23 Jan 2001, Paul J. Lucas wrote:
> >
> > >
> > > On Tue, 23 Jan 2001, Neil Jolly wrote:
> > >
> > > > I've compiled the 2.4 kernel with support for rage 128 & 64 (among other
> > > > things), the kernel boots into runlevel 3 alright, but as soon as i startx or
> > > > change to runlevel 5 the screen blanks and the system appears to freeze
> > >
> > > Although you neglected to mention what machine and boot metho d
> > > you are using (always, ALWAYS say at least what machine), it's
> > > my understanding that if you are using BootX, it leaves the PCI
> > > bus in a weird state that XFree86 4.x isn't happy with.
> > > (XFree86 3.x doesn't care). Hence, if you want to use XFree86
> > > 4.x, you MUST use yaboot. If you're on an old-world machine,
> > > this implies that you can not use XFree86 4.x.
> > >
> > > If anybody knows the above to be false (by actually running
> > > XFree86 4.x on a machine booted with yaboot, please correct me).
> > >
> > > - Paul
> > >
> > >
> > > ** Sent via the linuxppc-user mail list. See http://lists.linuxppc.org/
> > >
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: Wed, 24 Jan 2001 13:19:35 -0800 (PST)
> > From: "Paul J. Lucas" <pauljlucas@mac.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> > CC: linuxppc-user@lists.linuxppc.org
> >
> > On Wed, 24 Jan 2001, Paul J. Lucas wrote:
> >
> > > Well, here's the thread:
> > >
> > > http://x54.deja.com/[ST_rn=ps]/threadmsg_ct.xp?AN=704644183.1&mhitnum=4&CONTEXT=980354233.1761542218
> > >
> > > Is this guy wrong?
> >
> > Actually, to get this thread back in line with the Subject,
> > I've recently be alerted to the fact that the PCI stuff has
> > been fixed up in the 2.4 kernels, so BootX, XFree86 4.x, and
> > kernel 2.4 /should/ work fine. It's BootX, XFree86 4.x, and
> > 2.2.x and earlier that I was unsure about.
> >
> > - Paul
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: Wed, 24 Jan 2001 21:37:22 -0500
> > From: Stefan Jeglinski <jeglin@4pi.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > > > Well, here's the thread:
> > >>
> > >>
> > >>http://x54.deja.com/[ST_rn=ps]/threadmsg_ct.xp?AN=704644183.1&mhitnum=4&CONTEXT=980354233.1761542218
> > >>
> > >> Is this guy wrong?
> > >
> > > Actually, to get this thread back in line with the Subject,
> > > I've recently be alerted to the fact that the PCI stuff has
> > > been fixed up in the 2.4 kernels, so BootX, XFree86 4.x, and
> > > kernel 2.4 /should/ work fine. It's BootX, XFree86 4.x, and
> > > 2.2.x and earlier that I was unsure about.
> >
> > I don't know the details of the issue but strictly speaking, your
> > specific quote indicates the problem is with 2.2.17 and before, so in
> > this regard, 2.2.18 would also be OK...
> >
> > Stefan Jeglinski
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: 2.4 Kernel & Xfree-4.0.1
> > Date: Wed, 24 Jan 2001 19:35:32 -0800 (PST)
> > From: "Paul J. Lucas" <pauljlucas@mac.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > On Wed, 24 Jan 2001, Stefan Jeglinski wrote:
> >
> > > I don't know the details of the issue but strictly speaking, your
> > > specific quote indicates the problem is with 2.2.17 and before, so in
> > > this regard, 2.2.18 would also be OK...
> >
> > Yes, but the guy wrote me privaltely also and said that his PCI
> > patch didn't get all the way into 2.2.18.
> >
> > - Paul
> >
> > ---------------------------------------------------------------
> >
> > Subject: Video on dual G4
> > Date: Wed, 24 Jan 2001 14:47:14 +0900
> > From: adriaan@etl.go.jp (Adriaan Tijsseling)
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> > CC: linuxppc mail list <linuxppc-user@lists.linuxppc.org>
> >
> > Can anyone out there help out a newbie like me to enable the YDL 1.2.1.
> > to use the video mode. Right now I have to use linux-novideo and am
> > stuck in lame 256 color mode and a low resolution.
> >
> > Any hints, tips, suggestions, extremely welcome!
> >
> > Adriaan
> >
> > ---------------------------------------------------------------
> >
> > Subject: MOL and Audio CDs (yes, the usual questions but the usual answers don't seem to work ;-)
> > Date: Wed, 24 Jan 2001 16:28:18 +0900
> > From: Joss Winn <joss@josswinn.org>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > Hello,
> >
> > I have an iMac DV 500mhz with OS9.04 Japanese and SUSE 7.0PPC. All is
> > well but for a couple fo things.
> >
> > FIRST, I have folowed the very recent instructions on the SUSE support site
> > to get MOL working but alas, all I get is a bank grey X screen. I
> > have been given a molrc that works for someone else (different
> > machine and apple OS) and that produces the same results. MOL seems
> > to get so near yet so far from working. I don't get a chime, just a
> > grey X window. Would having the japanese OS be the problem. Does MOL
> > work on non English systems? I have been trying with this for a long
> > time and asked on all the lists except this one but still don't know
> > what's wrong. Can anyone here help? I am running thhe 2.2.18 kernel
> > withthe latest MOL.
> >
> > SECOND, I know there are issues with playing audio CDs on the newest
> > iMacs so I have followed the instructions at imaclinux.net that are
> > supposed to get Audio Cds working with xmms but these don't work.
> > Also, I have heard I can at least rip the tracks and play them off my
> > hard disk but cdparanoia doesn't recognise any CD in the drive. Data
> > discs/mp3 discs are fine.
> >
> > Any advice? I have the latest xmms, the plugins, everything but no CD
> > is recognised and no tracks show up in the GUI.
> >
> > thank you very much
> > joss
> >
> > --
> > joss@josswinn.org
> > http://www.josswinn.org
> >
> > ---------------------------------------------------------------
> >
> > Subject: iMac DV Install Prob
> > Date: Wed, 24 Jan 2001 09:29:51 -0500
> > From: "Michael Baldwin" <michael@westpole.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: <yellowdog-general@lists.yellowdoglinux.com>
> >
> >
> > I've been working on getting YD 1.2 installed on my iMac DV. After
> > some minor probs getting the install to recognize the USB keyboard and
> > mouse I was able to run an install using BenH's kernel and have had
> > some success in getting the install to work.
> >
> > However, the install isn't building a fstab. So I get errors
> > on reboot and the root fs is mounted read-only. I'd prefer not to
> > rebuild the fstab manually...but would attempt to do so if I could
> > figure out how to change the root fs to read-write.
> >
> > Has anyone else seen this problem? And, if so, can it be corrected
> > such that the install writes the fstab correctly itself?
> >
> > michael baldwin
> > michael@westpole.com
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: iMac DV Install Prob
> > Date: Wed, 24 Jan 2001 20:05:53 -0500 (EST)
> > From: Jonathan Bertsch <bertsch.13@osu.edu>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > I had a similar problem w/ 1.2 not creating a fstab file, so I waited
> > untill 1.2.1 came out and used the kernel on the install cd, and later
> > upgraded the kernel. I had no problems with 1.2.1, so I would recommend
> > getting that.
> >
> > --
> > Jonathan Bertsch
> > bertsch.13@osu.edu
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: MOL and Audio CDs
> > Date: Wed, 24 Jan 2001 11:28:29 -0500 (EST)
> > From: Hollis R Blanchard <hollis+@andrew.cmu.edu>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > On Wed, 24 Jan 2001, Joss Winn wrote:
> > >
> > > I have an iMac DV 500mhz with OS9.04 Japanese and SUSE 7.0PPC. All is
> > > well but for a couple fo things.
> > >
> > > FIRST, I have folowed the very recent instructions on the SUSE support site
> > > to get MOL working but alas, all I get is a bank grey X screen. I
> > > have been given a molrc that works for someone else (different
> > > machine and apple OS) and that produces the same results. MOL seems
> > > to get so near yet so far from working. I don't get a chime, just a
> > > grey X window. Would having the japanese OS be the problem.
> >
> > It could be. I assume you're using the Japanese Mac OS ROM file as rom/rom.nw?
> > If possible, try installing a "normal" system (and maconlinux.org has a copy
> > of a "normal" Mac OS ROM file), maybe on another partition, and try booting
> > that.
> >
> > > SECOND, I know there are issues with playing audio CDs on the newest
> > > iMacs so I have followed the instructions at imaclinux.net that are
> > > supposed to get Audio Cds working with xmms but these don't work.
> >
> > I got xmms-cdread working here... how does it "not work"? Are you adding
> > /dev/cdrom to your playlist?
> >
> > > Also, I have heard I can at least rip the tracks and play them off my
> > > hard disk but cdparanoia doesn't recognise any CD in the drive. Data
> > > discs/mp3 discs are fine.
> >
> > cdparanoia needs permissions to devices other than the normal cdrom. You could
> > either figure out what it needs (it has a -search and -verbose flags as I
> > recall) and grant it access, or just run it as root.
> >
> > -Hollis
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: HELP! Long ping times under Yellow Dog Linux
> > Date: Wed, 24 Jan 2001 10:44:21 -0600
> > From: Gawain Reifsnyder <gawain@guitar.net>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > I think I may have found the problem... After (finally) getting
> > around to installing analog on the G4 and analyzing some of the
> > recent log files it looks like we may simply be whacking our upstream
> > bandwidth cap. The machine is serving about 827MB/day, which works
> > out to 9.8kb/second (78.4kbps) averaged over 24 hours. We could
> > easily be hitting our 128kbps bandwidth cap a good part of the time.
> >
> > Thanks again to all who responded. We'll now be moving up the
> > schedule for getting a faster connection. :-)
> >
> > ---------------------------------------------------------------
> >
> > Subject: drive initialization problem
> > Date: Wed, 24 Jan 2001 14:19:38 +0000
> > From: antadam <antadam@lunc-lady.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > i have a 60 gig maxtor drive that was formatted hfs a while back so i could
> > mount it as mount -t hfs /dev/hda8 /mnt/hd60 and it'd mount fine, however, i
> > want to run it as an ftp drive so i gotta format it to ext2 to do that. so i
> > went into mac os to initialize it for 1 2 gig mac hfs partition then a unix
> > one (i had to do it to install ydl b/c pdisk didn't want to work for some
> > reason). so anyways, it wouldn't mount obviously. i ran pdisk w/the table
> > looking like this......
> > /sbin/disk /dev/hda
> >
> > 1: apple_partition_map Apple 63 @ 1
> > 2: apple_driver_ATA* macintosh 54 @ 64
> > 3: apple_driver_ATA* macintosh
> > 4: apple_fwdriver macintiosh
> > 5: apple_driver_iokit macintosh
> > 6: apple_patches patch partition
> > 7: apple_hfs untitled
> > 8: apple_unix_svr2 unreserved 1
> > 9: apple_free extra
> >
> > so i do delete partition 8, create partition 8 from the end of partition 7 to
> > the end of the drive, write the map, and quit. when i go to do mount
> > /dev/hda8 /mnt/hd60 i get mount: you must specify the filesystem type
> > so i do mount -t ext2 /dev/hda8 /mnt/hd60 and i get
> > mount: wrong fs type, bad option, bad superblock on /dev/hda8, or too many
> > mounted file systems
> > nothing's mounted in the /mnt/hd60 folder. any suggestions?
> > i ran /sbin/mke2fs and got an error (i was suggested to run it).
> > this is on a blue and white g3 450, 256 ram, running off a 10 gig scsi (the
> > 60 gig drive ran linux at one point on a 20 gig partition so i know it can be
> > partitioned), cs 1.2.1 kernel 2.2.17
> > any suggestions would be appreciated
> > adam
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: yup update problem
> > Date: Wed, 24 Jan 2001 13:39:25 -0700
> > From: Bryan Stillwell <bstill@terraplex.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > On Tue, Jan 23, 2001 at 01:22:40AM -0700, Philip Good wrote:
> > >I'm trying to use "yup update" but keep getting the following error:
> > >
> > >Unable to satisfy dependency rpmlib(PayloadFilesHavePrefix) <= 4.0-1 for
> > >package libmng
> > >
> > >using xrpm I can't find any traces of rpm4 or rpmlib. I do have rpm 3.05
> > >installed as well as libmng-0.9.2-1.
> >
> > The rpmlib() dependencies are part of rpm 3.0.5 and higher. The latest
> > version of yup handles these dependencies, you can get it from here:
> >
> > ftp://ftp.yellowdoglinux.com/pub/yellowdog/updates/champion-1.2/ppc/RPMS/yup-0.6.6-2.noarch.rpm
> >
> > Normally when running `yup update` it would update itself automatically,
> > but the sanity check is failing in your case probably due to installing
> > an rpm without yup that was built with rpm 3.0.5 or higher.
> >
> > Bryan
> >
> > --
> > Terra Soft Solutions, Inc. | Software Engineer
> > http://www.terrasoftsolutions.com/ | bstill@terraplex.com
> > GPG fingerprint: 3608 4610 8C08 B8EB 0970 9686 8A93 386C 6116 EFE2
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: yup update problem
> > Date: Wed, 24 Jan 2001 14:19:21 -0700
> > From: "Philip Good" <phil@redplanetx.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > Thanks.
> >
> > I do like yup but I'm finding that I've got so many hosed up
> > dependencies it's taking me quite a while to be able to get my system
> > fixed up so I can even use it. I've manged to get my BlueG3 fixed up and
> > and "yupped" now I'm working on my Pismo. Maybe you can help with the
> > following depenency failure when I run yup update
> >
> > libbz2.so.0 for package gnome-core ( I assume all my other gnome stuff
> > too).
> >
> > I've got bzip2-1.0.1-2 installed and that gives me libbz2.so.1, which is
> > required by some other packages, like ImageMagick. So, right now, I
> > can't run yup unless I degrade bzip2 and remove the packages that reuire
> > the libbz2.so.1.
> >
> > gnome seems to run OK even though I don't have the libbz2.so.0 that it
> > depends on. Is there a way to change this dependency?
> >
> > Thanks for any ideas.
> >
> > Phil
> >
> > > On Tue, Jan 23, 2001 at 01:22:40AM -0700, Philip Good wrote:
> > > >I'm trying to use "yup update" but keep getting the following error:
> > > >
> > > >Unable to satisfy dependency rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> > for
> > > >package libmng
> > > >
> > > >using xrpm I can't find any traces of rpm4 or rpmlib. I do have rpm
> > 3.05
> > > >installed as well as libmng-0.9.2-1.
> > >
> > > The rpmlib() dependencies are part of rpm 3.0.5 and higher. The
> > latest
> > > version of yup handles these dependencies, you can get it from here:
> > >
> > >
> > ftp://ftp.yellowdoglinux.com/pub/yellowdog/updates/champion-1.2/ppc/RPMS/yup-0.6.6-2.noarch.rpm
> > >
> > > Normally when running `yup update` it would update itself
> > automatically,
> > > but the sanity check is failing in your case probably due to
> > installing
> > > an rpm without yup that was built with rpm 3.0.5 or higher.
> > >
> > > Bryan
> > >
> > > --
> > > Terra Soft Solutions, Inc. | Software Engineer
> > > http://www.terrasoftsolutions.com/ | bstill@terraplex.com
> > > GPG fingerprint: 3608 4610 8C08 B8EB 0970 9686 8A93 386C 6116 EFE2
> > >
> > >
> >
> > --
> > Philip Good
> > Red Planet Development, Red Canyon Software, Good Chi Tai Chi
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: yup update problem
> > Date: Wed, 24 Jan 2001 15:53:23 -0700
> > From: Bryan Stillwell <bstill@terraplex.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > I actually ran into this problem while working on YDL 2.0. Normally an
> > ordinary user wouldn't experience this problem, because to have this
> > problem show up your would have had to installed bzip2 1.0.1-2 with the
> > --force option sent to rpm. If you didn't do this yourself it may have
> > been caused by the helixcode installer if you've ever used it.
> >
> > If you don't want to downgrade bzip2 and all the packages that require
> > libbz2.so.1 you can download the SRPMs for all the packages that require
> > libbz2.so.0 and rebuild them so they will use libbz2.so.1. That may be
> > a rather hefty project though, and you may just want to wait till YDL
> > 2.0 is released and upgrade then.
> >
> > Bryan
> >
> > --
> > Terra Soft Solutions, Inc. | Software Engineer
> > http://www.terrasoftsolutions.com/ | bstill@terraplex.com
> > GPG fingerprint: 3608 4610 8C08 B8EB 0970 9686 8A93 386C 6116 EFE2
> >
> > >I do like yup but I'm finding that I've got so many hosed up
> > >dependencies it's taking me quite a while to be able to get my system
> > >fixed up so I can even use it. I've manged to get my BlueG3 fixed up and
> > >and "yupped" now I'm working on my Pismo. Maybe you can help with the
> > >following depenency failure when I run yup update
> > >
> > >libbz2.so.0 for package gnome-core ( I assume all my other gnome stuff
> > >too).
> > >
> > >I've got bzip2-1.0.1-2 installed and that gives me libbz2.so.1, which is
> > >required by some other packages, like ImageMagick. So, right now, I
> > >can't run yup unless I degrade bzip2 and remove the packages that reuire
> > >the libbz2.so.1.
> > >
> > >gnome seems to run OK even though I don't have the libbz2.so.0 that it
> > >depends on. Is there a way to change this dependency?
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: yup update problem
> > Date: Wed, 24 Jan 2001 21:46:55 -0500
> > From: Patrick Callahan <pac1@tiac.net>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > On Wed, 24 Jan 2001, you wrote:
> > > I actually ran into this problem while working on YDL 2.0. Normally an
> > > ordinary user wouldn't experience this problem,
> > > because to have this
> > > problem show up your would have had to installed bzip2 1.0.1-2 with the
> > > --force option sent to rpm. If you didn't do this yourself it may have
> > > been caused by the helixcode installer if you've ever used it.
> > >
> > Shouldn't we be able to install additional packages and upgrades without
> > having to abandon the upgrades you provide?
> >
> > Otherwise the solution is a clean install,
> > followed by a yup update
> > followed by upgrades and installs of all the packages we want over and
> > above the ones ydl provides in the base distribution and yup.
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: @: yup update problem
> > Date: Wed, 24 Jan 2001 13:44:27 -0700
> > From: Bryan Stillwell <bstill@terraplex.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > On Tue, Jan 23, 2001 at 08:25:46PM +0900, Adriaan Tijsseling wrote:
> > >Another problem with yup is that you can't configure it for proxies. As
> > >such it won't work at all.
> >
> > I wouldn't mind adding support for proxies in yup, but I don't have
> > access to a proxying firewall to test with... So to make this happen
> > someone would either have to give me access to a computer behind a proxy
> > firewall or someone behind a proxy would have to write it themselves and
> > send me a patch.
> >
> > Bryan
> >
> > --
> > Terra Soft Solutions, Inc. | Software Engineer
> > http://www.terrasoftsolutions.com/ | bstill@terraplex.com
> > GPG fingerprint: 3608 4610 8C08 B8EB 0970 9686 8A93 386C 6116 EFE2
> >
> > ---------------------------------------------------------------
> >
> > Subject: The BriQ
> > Date: Wed, 24 Jan 2001 17:24:37 -0500 (EST)
> > From: christopher.murtagh@wcg.mcgill.ca
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > Has anyone here tried YDL on this machine:
> >
> > http://www.totalimpact.com/briQ.html
> >
> > It looks amazing!! A 5-3/4 inch wide G4! Is it vaporware or real?
> >
> > Cheers,
> >
> > Chris
> >
> > --
> >
> > Christopher Murtagh
> > Webmaster / Web Communications Group
> > McGill University
> > Montreal, Quebec
> > Canada
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: The BriQ
> > Date: Wed, 24 Jan 2001 20:35:17 -0500 (EST)
> > From: "Sean O. Denney" <sdenney@cise.ufl.edu>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > It's not vapor-ware, you can check out more info on /.
> >
> > This compay was first brought to light when they made the dual and
> > quad processor G3 and G4 PCI boards.
> >
> > --- Sean
> >
> > On Wed, 24 Jan 2001 christopher.murtagh@wcg.mcgill.ca wrote:
> >
> > >
> > > Has anyone here tried YDL on this machine:
> > >
> > > http://www.totalimpact.com/briQ.html
> > >
> > > It looks amazing!! A 5-3/4 inch wide G4! Is it vaporware or real?
> >
> > ---------------------------------------------------------------
> >
> > Subject: Pismo mirror program
> > Date: Wed, 24 Jan 2001 18:01:52 -0700
> > From: "Philip Good" <phil@go2taichi.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: "linuxppc-user@lists.linuxppc.org" <linuxppc-user@lists.linuxppc.org>,
> > " mol-general@lists.maconlinux.org" <mol-general@lists.maconlinux.org>,
> > " yellowdog-general@lists.yellowdoglinux.com" <yellowdog-general@lists.yellowdoglinux.com>
> >
> > I've put the mirror program for use with Pismo up for download on the
> > following site:
> >
> > http://www.redplanetx.com/linuxppc/pismo.html
> >
> > Several things:
> >
> > 1. This is a program which has been flating around between some of us
> > Pismo users. I don't know who wrote it and I don't have the source code.
> >
> > 2. If anyone out there is the original coder and would like to make the
> > source code public I can provide a place for it.
> > 3. If anyone out there is the original coder and wants this removed
> > I will immediately do so.
> > 4. Use at your own risk. I haven't had any problems with it in several
> > months of use.
> >
> > Also included on the linked page is a MOL hack and shel script which
> > will rerun mirror after changing video mode in MOL.
> >
> > Good luck everybody,
> > Phil
> >
> > ---------------------------------------------------------------
> >
> > Subject: Re: MOL help needed
> > Date: Wed, 24 Jan 2001 20:44:15 -0500
> > From: Sam Moore <samiwas@macconnect.com>
> > Reply-To: yellowdog-general@lists.yellowdoglinux.com
> > To: yellowdog-general@lists.yellowdoglinux.com
> >
> > I've been scratching my head about this for two days.
> > You're on 9.1, right?
> > What kind of hardware is it? (G3, iMac, etc)
> >
> > On 1/22/01 at 2:41 PM, cfairman@Stanford.EDU (Carolyn Jean Fairman) wrote:
> >
> > >
> > >
> > > Sam Moore <smoo@lungta.org> wrote:
> > >
> > > There should be a "Mac OS ROM" file in your Mac System Folder -
> > > that's the one
> > > you want. (It should also be in the System Folder of your MacOS
> > > install CD, but
> > > I don't know about the upgrader disk...)
> > >
> > > That's just it -- I can't find this file on my Mac! Is there any way
> > > I can use a generic one found elsewhere?
> > >
> > > Carolyn
> >
> > Sam Moore <smoo@lungta.org>
> >
> > Personal: http://www.lungta.org (not ready yet)
> > For the clan: http://smhtf.lungta.org
> > Work: http://www.ewcreative.com
> >
> > "Good and bad, happy and sad, all thoughts vanish into
> > emptiness like the imprint of a bird in the sky."
> h
>
This archive was generated by hypermail 2a24 : Thu Jan 25 2001 - 13:51:25 MST