Re: Bug#296960: pmac G4 AGP 350MHz Install Report
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:
> >>Comments/Problems:
> >>
> >>- Shell escaping with the installer presents a difficult situation for
> >>mounting other partitions since
> >> /dev/hd[ab]* is not recognized.
> >
> >Sure, it uses devfs, so you need /dev/ide/host0/.../disc
>
> Sorry. Just so used to the old ways....
Hehe, but fear not, the devfs stuff is going away soon, but it is still used
inside d-i.
> >>- install kernel-2.6.8-powerpc as part of the standard install.
> >
> >Ok.
> >
> >>- installed 2.6.10 & 11-rc4 (both from ppckernel.org) kernels onto
> >>hda5
> >>because I know what's coming.
> >
> >Well, that is something that you should do post-reboot. Not during the
> >install
> >like you did.
>
> I apologize again. However this is the 2nd (actually 4th counting
> the two install hangs previously due to the root partition filling up. I
> was getting a little tired of it. Besides I don't think
> copying the vmlinux and sysmap to /boot and the kernel mods to
> /lib/modules really will create an
Well, ... One never knows.
> 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 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 :)
> 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 ? 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
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), 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
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.
Friendly,
Sven Luther
Reply to: