On Sat, Feb 26, 2005 at 09:58:06AM -0600, Jeffrey B. Green wrote: > Sometimes, computers are not a human's best friend. Lost prior version > >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.
Ok. You have two ATI rage 128 in that box, should probably even work in dual head mode. > 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). What i really want is your /var/log/XFree86.0.log in a failed to work situation. > >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. Which sucks You know that the 2.6.8-powerpc kernel is the *EXACT SAME* kernel you managed to boot the debian-installer with, don't you ? So it can only work. At worse, boot into debian-installer once more, chroot into the installed system, and mount it from there. > 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. I have some serious doubts about this, don't forget to run ybin too, and such stuff. I helped a guy out with a toilet-seat ibook at Solutions Linux last month, and this exact error message was the result of the missing initrd line. > Section "Device" > > # Option "UseFBDev" "true" > Identifier "ATI Rage 128 Pro GL PF (AGP)" > Driver "fbdev" Well, try using the ati driver here. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
