YDL on a G4 Cube
Maxwell Bottiger
yellowdog-newbie@lists.terrasoftsolutions.com
Thu, 7 Aug 2003 14:59:55 -0400 (EDT)
Ok, I tried this out. First, I booted the system and at the boot prompt I
typed "Linux video=aty128fb:vmode17, cmode:8" The computer booted, but
nothing changed. Startx resulted in the same output.
So, I thought, maybe I didn't get that right. Maybe I need to have
yabootconf add the line in there for me. So, I ran "yabootconf
--kernel-options "video=aty128fb:vmode17, cmode8" The program prompted me
to write the new boot loader config to the disk, and I took the default
option.
Now, when the computer starts, I'm no longer asked if I want to boot to
OSX, but rather I go strait to the linux yaboot prompt. If I choose Linux
(which is the only option) the screen quickly flashes a little bit of text
by, then goes black. Once everything goes black the computer no longer
boots. I don't see any of the normal output from the kernel being loaded.
So, how do I boot to some sort of rescue mode, and once I change the
yaboot params to anything else, where do I go next?
BTW, where can I find a list of the vmode and cmode params?
On Thu, 7 Aug 2003, Norberto Quintanar wrote:
> kernel argument:
> video=aty128fb:vmode:17, cmode:8
>
> try that to get started then fiddle with the vmode and cmode numbers
> to your choosing
> --- Maxwell Bottiger <sleepylight@jive-turkey.net> wrote:
> > Hi,
> > I have a clean install of YDL 3.0 on a G4 Cube. Although I've
> > been using RH linux on x86 machines the Mac is pretty new to me.
> > I'm
> > pretty sure I have an ATI Rage128 in the machine. And since I've
> > just
> > mentioned the video card, you've probably guessed that I'm having
> > X11
> > problems. You're right.
> > I had to install linux through the text installer because the
> > graphical installer was hanging when it tried to switch out of text
> > mode.
> > Now the system is up, and I still can't load X.
> > I'm sort of at a loss as to what my problem is. As far as I know
> > this Mac is a stock setup, and I'm just using 3.0 out of the box -
> > no
> > updates. I'll attach a typescript of the problem, and my config
> > file.
> > Let me know if you see anything wrong.
> >
> > --
> >
> >
> > -Maxwell Bottiger
> >
> > This thing is like a wolf
> > This thing is a wolf
> > Thus, it is a thing to be bansished
> >
> > > Script started on Thu 07 Aug 2003 11:04:44 AM EDT
> > [root@localhost root]# startx
> > Using authority file /root/.Xauthority
> > Writing authority file /root/.Xauthority
> > Using authority file /root/.Xauthority
> > Writing authority file /root/.Xauthority
> >
> >
> > XFree86 Version 4.3.0 (Yellow Dog Linux release: 4.3.0-2.1c)
> > Release Date: 27 February 2003
> > X Protocol Version 11, Revision 0, Release 6.6
> > Build Operating System: Linux 2.4.20-7csmp ppc [ELF]
> > Build Date: 12 March 2003
> > Build Host: skyfox.terraplex.com
> >
> > Before reporting problems, check http://www.XFree86.Org/
> > to make sure that you have the latest version.
> > Module Loader present
> > OS Kernel: Linux version 2.4.20-8d (dburcaw@skyfox.terraplex.com)
> > (gcc version 3.2.2 20030217 (Yellow Dog Linux 3.0 3.2.2-2a)) #1 Sat
> > Mar 15 19:38:12 EST 2003
> > Markers: (--) probed, (**) from config file, (==) default setting,
> > (++) from command line, (!!) notice, (II) informational,
> > (WW) warning, (EE) error, (NI) not implemented, (??)
> > unknown.
> > (==) Log file: "/var/log/XFree86.0.log", Time: Thu Aug 7 11:04:47
> > 2003
> > (==) Using config file: "/etc/X11/XF86Config"
> > (EE) R128(0): Cannot read V_BIOS (5)
> > (EE) R128(0): No DFP detected
> > Symbol drmCtlUninstHandler from module
> > /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved!
> > Symbol DRIGetDeviceInfo from module
> > /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved!
> > Symbol drmCtlInstHandler from module
> > /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved!
> > Symbol drmGetInterruptFromBusID from module
> > /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved!
> > Symbol drmAgpBase from module
> > /usr/X11R6/lib/modules/drivers/r128_drv.o is unresolved!
> >
> > *** If unresolved symbols were reported above, they might not
> > *** be the reason for the server aborting.
> >
> > Fatal server error:
> > Caught signal 11. Server aborting
> >
> >
> > When reporting a problem related to a server crash, please send
> > the full server output, not just the last messages.
> > This can be found in the log file "/var/log/XFree86.0.log".
> > Please report problems to xfree86@xfree86.org.
> >
> > XIO: fatal IO error 104 (Connection reset by peer) on X server
> > ":0.0"
>
> > after 0 requests (0 known processed) with 0 events
> > remaining.
>
> > [root@localhost root]#
> > Script done on Thu 07 Aug 2003 11:04:51 AM EDT
> > > # File generated by Xautoconfig.
> > Section "ServerLayout"
> > Identifier "XFree86 Configured"
> > Screen 0 "Screen0" 0 0
> > InputDevice "Mouse0" "CorePointer"
> > InputDevice "Keyboard0" "CoreKeyboard"
> > EndSection
> >
> > Section "Files"
> > # RgbPath is the location of the RGB database. Note, this is the
> > name of the
> > # file minus the extension (like ".txt" or ".db"). There is
> > normally
> > # no need to change the default.
> >
> > # Multiple FontPath entries are allowed (they are concatenated
> > together)
> > # By default, Red Hat 6.0 and later now use a font server
> > independent of
> > # the X server to render fonts.
> >
> > RgbPath "/usr/X11R6/lib/X11/rgb"
> > FontPath "unix/:7100"
> > EndSection
> >
> > Section "Module"
> > Load "dbe"
> > Load "extmod"
> > Load "fbdevhw"
> > Load "glx"
> > Load "record"
> > Load "freetype"
> > Load "type1"
> > #Load "dri"
> > EndSection
> >
> > Section "InputDevice"
> > Identifier "Keyboard0"
> > Driver "keyboard"
> > # Change "XkbModel" to "macintosh_old" if you are using
> > # the deprecated adb keycodes.
> > Option "XkbRules" "xfree86"
> > Option "XkbModel" "macintosh"
> > Option "XkbLayout" "us"
> > EndSection
> >
> > Section "InputDevice"
> > Identifier "Mouse0"
> > Driver "mouse"
> > Option "ZAxisMapping" "4 5"
> > Option "Protocol" "IMPS/2"
> > Option "Device" "/dev/input/mice"
> > EndSection
> >
> > Section "Monitor"
> > Identifier "Monitor0"
> > ModelName "Monitor Model"
> > Option "DPMS"
> > HorizSync 30-130
> > VertRefresh 50-60
> >
> > EndSection
> >
> > Section "Device"
> > Identifier "Card0"
> > #Option "ShadowFB" "true"
> > Driver "r128"
> > BusID "PCI:0:16:0"
> > EndSection
> >
> > Section "Screen"
> > Identifier "Screen0"
> > Device "Card0"
> > Monitor "Monitor0"
> > DefaultDepth 16
> > SubSection "Display"
> > Depth 8
> > Modes "640x480"
> > EndSubSection
> > SubSection "Display"
> > Depth 16
> > Modes "1280x1024" "1024x768" "800x600" "640x480"
> > EndSubSection
> > SubSection "Display"
> > Depth 24
> > Modes "1280x1024"
> > EndSubSection
> > EndSection
> >
> > Section "DRI"
> > Group 0
> > Mode 0666
> > EndSection
> >
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com
> _______________________________________________
> yellowdog-newbie mailing list
> yellowdog-newbie@lists.terrasoftsolutions.com
> http://lists.terrasoftsolutions.com/mailman/listinfo/yellowdog-newbie
>
--
-Maxwell Bottiger
This thing is like a wolf
This thing is a wolf
Thus, it is a thing to be bansished