Re: Bug#296960: pmac G4 AGP 350MHz Install Report
Sometimes, computers are not a human's best friend. Lost prior version
of this reply. Configuring T-bird on my new install and tried out saving
drafts to server...didn't seem to work. Oh well, one more time...
Sven Luther wrote:
On Sat, Feb 26, 2005 at 07:00:34AM -0600, Jeff Green wrote:
On Feb 26, 2005, at 2:59 AM, Sven Luther wrote:
On Fri, Feb 25, 2005 at 06:15:25PM -0600, Jeff Green wrote:
issue. (If it does, something is wacky.) However, the thing that did
create a problem was attempting to install a deb there (your
2.6.10-powermac kernel plus extras) which created the problems
2.6.10-powerpc, and what extras ?
(In my best Jack Webb voice: Just the docs, 'Mam.) Probably should have
said "plus docs", extras really means something else.
in the "select and install" step after rebooting into the base-install.
Ah, well, there is when you should have installed it i think.
I effectively just removed it, i.e.
did a re-install of 2.6.10-powermac and then a de-install. That indeed
2.6.10-powerpc, not -powermac :)
My mind is not what it used to be, though maybe that is a good thing.
should have been installed after everything was up and working okay.
Just a note though, the very first time I did this install (last
weekend), the installer (rc2 ?) did put in its own boot info into the
boot partition, and booted into kernel 2.6.8. No fiddlin' there,
exactly (iirc) the same thing happened. (I was not happy about it
wiping out my boot partition.)
Exact, so your problem is probably that you forgot to include the initrd in
your /etc/yaboot.conf.
- nb: 2.6.10 won't startx, and 2.6.11 will with fb driver config
though
w/o working wacom support.
Would really like to use my wacom mouse and pen (if possible). I'm back
to the hockey puck at this point. May have to do a kernel build
myself.....
What graphic card do you have and what is the problem with X ?
The graphic card I think is listed in the lspci, which is all the info
that I have right now about it. There are actually two video cards
there, which has a bit of a story behind it in regards to the old 2.4
kernels, circa 2002 or so. To get more info about the card(s), I'd have
to reboot into OS X to see what Apple says that I have.
The problem is that X doesn't work with the "ati" driver I did get it to
work with "fbdev" driver, and I guess that's okay, but you'd think that
an old card (c.2000) should have all of the driver issues sorted out by
now. I'll attach my XF86Config-4 for you (file_for_sven_xfconfig).
It should be
ok, i think, or you should maybe upgrade to X.org or dri-trunk kernel, don't
know. Could you provide the details. As for the wacom support, i believe this
is a missing module or more probably an XFree86 issue, since we build all the
modules that are buildable on powerpc. And indeed i have :
CONFIG_USB_WACOM=m
So provided your wacom tablet is indeed the usb one, try :
modprobe wacom
Will do as soon as I get 2.6.10-powerpc back on *and* it boots. (I will
try it one more time with the initrd stuff.)
And add them to your /etc/modules or that fancy X mouse module loading stuff.
- also (tried to) install sven's 2.6.10-3-powerpc before rebooting but
see below....
- (NEED to sync yaboot.conf again between the two systems.)
- REBOOT into base system:
- kernel 2.6.8 hangs (with the following as the tail of the boot
process:)
TCP: Hash tables configured (established 262144 bind 65536)
VFS: Cannot open root device "hda5" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
<0>Rebooting in 180 seconds..
This should not happen, i think your hardware is well suppported, but
for some
reason the ide driver is not loaded in the initrd. I suspect this may
be due
to you doing unorthodoxe kernel things during the install though, or
is a bug
in initrd-tools. Mmm, maybe you simply forget to add the initrd entry
in your
yaboot.conf ?
As above, it happened also with the installer doing everything on
its own, yaboot.conf too. I did try 2.6.8 with my own yaboot.conf and with
the initrd entry, same result. However the current status of
yaboot.conf may or may not have good 2.6.8 setup status if it's in
there at all. I'll grab it and attach at the end.
Ok.
I would like :
1) a lspci and lspci -n output of your hardware.
Wasn't that part of the install report that I submitted? It came
along in the debian mail that I received. I think you received the same
mail. Or are you asking for something different?
Yep, had erased it when i was replying also, but it could be the same, will
check. Mmm, you have :
0001:11:02.0 SCSI storage controller: Adaptec AHA-7850 (rev 03)
0001:11:07.0 ff00: Apple Computer Inc. KeyLargo Mac I/O (rev 02)
May guess is that your IDE disk (it is ide right)
Believe so.
, is hanging off this
KeyLargo super controller. Could you also paste me the content of the
/proc/device-tree/aliases ? I guess the interesting part would be the one
named ide or something such, maybe hd.
Still, this IDE controller should be included in both the 2.6.10 and 2.6.8 :
CONFIG_BLK_DEV_IDE_PMAC=y
CONFIG_BLK_DEV_IDE_PMAC_ATA100FIRST=y
CONFIG_BLK_DEV_IDEDMA_PMAC=y
So i am baffled about your problem.
2) if you could mount the initrd (both 2.6.10 and 2.6.8), and run a
find on
it to check for the presence or absence of modules with the above
list.
Hmmm, you mean an "lsmod" after the kernel is running? Or something
else? I'm not totally familiar with initrd images and what they do. (A
small gap in my kernel knowledge, maybe you could fill it in real
quick...25 words or less, or point me to a doc file in the kernel
documentation, please not too long right now...short on time. My
_present_ knowledge ends at putting the initrd= line into the
yaboot.conf file.)
mount -t cramfs /boot/initrd.img-2.6.(8|10)-powerpc /mnt
find /mnt >>file_for_sven
Ack!! The ppckernel.org kernel (2.6.11) can't handle the cramfs type, e.g.
naro:/boot# mount -t cramfs /boot/initrd.img-2.6.8-powerpc /mnt/initrd
mount: fs type cramfs not supported by kernel
attache file_for_sven to a followup to this bug report.
3) just to be on the safe side, the content of your yaboot.conf.
Smart man. I'll attach. May be at the bottom of the msg. The
partition 5 items are the current install that I did yesterday. The
partition 7 group is the install from last week. The orb has an ancient
linuxppc install on it and I use it for my rescue disk. (Probably should
update that baby.)
Well, there the mystery is solved, none of your entries had any initrd field,
... wrong, you had one in this one :
image=hd:7,/boot/vmlinux
label=testing
initrd=/boot/initrd.img
device=hd:
partition=7
root=/dev/hda7
Which is the entry from last week (which worked right ?), but none of the
partition 5 had any initrd entry. and your error message was :
VFS: Cannot open root device "hda5" or unknown-block(0,0)
Which clearly shows it trying to access partition 5. So add the initrd= field
to the right yaboot entry, and everything will work out fine for you.
I am curious thought about the partition=7 field in this context, since i
thought that OF numbered partitions at 0, at least it does so on my pegasos,
and probably the sun boxes. not sure about the ibm ones.
- retry with 2.6.10 from ppckernel.org => comes up
- needed to edit /etc/network/interfaces to change eth1 to eth0,
networking wouldn't work otherwise
- In the 'select and install' step, after selecting, the list of
packages flies by and then a dialog
saying one or more packages failed to install.
- moved the /v/c/apt to /usr/v/c/apt, but still had the error (due to
kernel-2.6.10-powerpc bad install)
Err, you seem to say there is a bad install, and see below for
details, but i
am missing the details in question. So, please provide detailed info
on that
too.
Like I said (way) above, that was probably my mistake. I just
"undid" it. But now I have to re-install your 2.6.10. (Need to get outside
right now to do some birding...migration time...sandhill cranes...that
kind of thing.)
Ok, so please fix your (hand-crafted) yaboot.conf, and try again, my guess is
that things will immediately get fixed from there.
As I mentioned, I will try the initrd thing again with your kernel. I
guess I can try the already present 2.6.8 kernel right now. And will see
what happens. However, you may have to be prepared for bad news....tho'
hope not. Back in a bit.
jeff
# XF86Config-4 (XFree86 X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
# This file is automatically updated on xserver-xfree86 package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xfree86
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following commands as root:
#
# cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
# md5sum /etc/X11/XF86Config-4 >/var/lib/xfree86/XF86Config-4.md5sum
# dpkg-reconfigure xserver-xfree86
Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen" 0 0
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
EndSection
Section "Files"
# local font server
# if the local font server has problems, we can fall back on these
FontPath "unix/:7100"
FontPath "/usr/lib/X11/fonts/misc"
FontPath "/usr/lib/X11/fonts/cyrillic"
FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/Type1"
FontPath "/usr/lib/X11/fonts/CID"
FontPath "/usr/lib/X11/fonts/Speedo"
FontPath "/usr/lib/X11/fonts/100dpi"
FontPath "/usr/lib/X11/fonts/75dpi"
EndSection
Section "Module"
Load "GLcore"
Load "bitmap"
Load "dbe"
Load "ddc"
Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "record"
Load "speedo"
Load "type1"
Load "vbe"
EndSection
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "macintosh"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "Auto"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
Identifier "Apple Studio Display 17 inch"
HorizSync 80.0 - 80.0
VertRefresh 75.0 - 75.0
Option "DPMS"
EndSection
Section "Device"
# Option "UseFBDev" "true"
Identifier "ATI Rage 128 Pro GL PF (AGP)"
Driver "fbdev"
ChipSet "fbdev"
Card "fbdev fbdev"
BusID "PCI:0:16:0"
EndSection
Section "Screen"
Identifier "Default Screen"
Device "ATI Rage 128 Pro GL PF (AGP)"
Monitor "Apple Studio Display 17 inch"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1152x864" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 4
Modes "1152x864" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 8
Modes "1152x864" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 15
Modes "1152x864" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 16
Modes "1152x864" "800x600" "640x480"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1152x864" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
Reply to: