Too stupid to find ppc floppy.img

rickenbacherus · 12-24-2003, 03:13 PM

Reading the installer howto I see this:

Quote:

If you can't boot from CD, you can download floppy images to install
Debian. You need the bootfloppy-image.img, the floppy-image.img and
possibly one of the driver disks.

So I go look at Testing the Debian installer

floppy, netboot and other non-CD images [i386]
[powerpc] but I see nothing that ends with .img there. What am I doing wrong? Thanks.

llamakc · 12-24-2003, 06:57 PM

You don't need floppy images to install on powerpc. Tell us the model you are working with to begin. You need root.bin, linux.bin, yaboot, and yaboot.conf from a debian mirror and put those in the ALREADY partitioned partition.

What how-to or install instructions are you following?

EDIT:

SO I see you are trying to install with the Unstable installer. Perhaps you should join the d-i mailing list. That software isn't ready.

If you want to install Debian Stable on PowerPC hardware and THEN upgrade to Unstable I can help you.

rickenbacherus · 12-24-2003, 09:25 PM

OK I did find the stable discs here:
http://ftp2.de.debian.org/debian/dis...c/images-1.44/
and downloaded
boot-floppy-hfs.img
driver-1.bin
driver-2.bin
rescue.bin
root.bin

This is an old world UMAX s900 that doesn't seem to like to boot from cd although I will admit I'm not too well versed on ppc's. I think I need to use bootx which is already installed in macos9.1 so hopefully I just point it to /root. I have 2 drives a 2.3G for macos and a 9.1 for Linux. Currently yellowdog is installed but I'd really rather have Debian for various reasons.

I'm sure I'll be back with some questions.

rickenbacherus · 12-24-2003, 10:38 PM

So far so good- nuked macos (yeah!) and am installing stable from floppy ATM. I'm going to try to use quik instead of bootx. We'lll see how it goes.

Nu-Bee · 12-24-2003, 11:25 PM

Since there about 5 different sets of install docs, and depending on which webpage you link from you will end up finding different instructions, don't be surprised if people start telling you that you are using the wrong ones.

I have never seen a more disjointed setup in my life...everything from finding the -RIGHT- install docs, to their weirdo jigdo system. Then to find out that even though my Pioneer-105 DVD-ROM Drive boots off almost anything...the Debian CDs won't boot. Debian is the first & only distro that I had to create boot floppies for.

Now...those who got lucky & happened to find the right docs, and who were lucky and the CDs booted OK, and were lucky in several other things...are sure to claim Debian is the greatest thing since sliced bread.

The truth is otherwise though...

rickenbacherus · 12-25-2003, 01:21 AM

OK done. That was easy. Now I have a bit of a strange problem. Not wishing to use the ADB mouse I've installed a pci USB 2.0 card. It worked under ydl no problem. I've installed hotplug but when I try to load usbcore the module doesn't exist!

/lib/modules/2.2.20-pmac/usb$ ls
acm.o audio.o joydev.o printer.o wmforce.o

Where is usbcore and friends?

Code:

dmesg|grep usb
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
usb.c: registered new driver hid
usb-ohci.c: USB OHCI at membase 0xcc405000, IRQ 2
usb.c: new USB bus registered, assigned bus number 1
usb-ohci.c: request interrupt 2 failed
usb.c: USB bus 1 deregistered
usb.c: registered new driver wacom

Code:

cat /proc/interrupts
           CPU0
  2:          0   PMAC-PIC      MACE-txdma
  3:       1184   PMAC-PIC      MACE-rxdma
  4:          0   PMAC-PIC      SCC-txdma
  5:          0   PMAC-PIC      SCC-rxdma
  6:          0   PMAC-PIC      SCC-txdma
  7:          0   PMAC-PIC      SCC-rxdma
 12:         24   PMAC-PIC      53C94
 13:      30530   PMAC-PIC      MESH
 14:       1096   PMAC-PIC      MACE
 15:          0   PMAC-PIC      SCC
 16:          0   PMAC-PIC      SCC
 18:      15164   PMAC-PIC      VIA
 19:          0   PMAC-PIC      SWIM3
BAD:          0

I don't have a wacom tablet- dunno what that's about. Any ideas?

X is working and Enlightenment loads no problem. The background looks fine but the cursor and icon boxes are all.....well.....wavy I guess is how I'd describe it. I had to edit the XF86Config-4 to 832x624 and add DefaultFbBpp 32 in order to get X to start. fbset won't let me set it to 800x600 (unless I'm doing it wrong).

Code:

     DefaultDepth    24
        DefaultFbBpp 32

/snip/

SubSection "Display"
                Depth           24
                Modes           "832x624" "640x480"
        EndSubSection

Code:

fbset -i

mode "832x624-98"
    # D: 57.003 MHz, H: 65.370 kHz, V: 98.449 Hz
    geometry 832 624 832 1255 32
    timings 17543 16 16 16 16 8 8
    accel true
    rgba 8/16,8/8,8/0,8/24
endmode

Frame buffer device information:
    Name        : IMS TT (IBM)
    Address     : 0x82000000
    Size        : 4194304
    Type        : PACKED PIXELS
    Visual      : DIRECTCOLOR
    XPanStep    : 8
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 3328
    MMIO Address: 0x82800000
    MMIO Size   : 262144
    Accelerator : IMS Twin Turbo

I'm going to muck about with the H & V freq's and maybe that'll get it sorted out. Anyone else have a IMS twin turbo video card? Thanks.

rickenbacherus · 12-25-2003, 01:23 AM

Quote:

Originally posted by Nu-Bee
Since there about 5 different sets of install docs, and depending on which webpage you link from you will end up finding different instructions, don't be surprised if people start telling you that you are using the wrong ones.

I have never seen a more disjointed setup in my life...everything from finding the -RIGHT- install docs, to their weirdo jigdo system. Then to find out that even though my Pioneer-105 DVD-ROM Drive boots off almost anything...the Debian CDs won't boot. Debian is the first & only distro that I had to create boot floppies for.

Now...those who got lucky & happened to find the right docs, and who were lucky and the CDs booted OK, and were lucky in several other things...are sure to claim Debian is the greatest thing since sliced bread.

The truth is otherwise though...

OK so MDK is an easy install but that's where the fun ends. If you haven't ran into rpm dependency hell yet then just wait. That's exactly why I use Debian. I'm just not particularly familiar with ppc's.

llamakc · 12-25-2003, 07:24 AM

Do this: apt-cache search kernel-image. See anything with 2.4? apt-get install that. You could have also done this at the install prompt when you first tried installing:

bf24

And that would have put the 2.4 kernel instead of the 2.2 one you have. Personally, I'd check to see if BenH's older kernels support your machine. I rsync his 2.4 tree and rarely have problems with it. Modconf doesn't have your modules?

Good luck!

rickenbacherus · 12-25-2003, 09:59 AM

Thanks llamakc that new kernel (2.4.18-powerpc) did the trick on the USB. Now the last of my troubles- that twin turbo card. Had I been thinking I would have saved XF86Config-4 from my ydl install but I think I have that correct and that perhaps I need to pass some parameters on boot for the driver. When I was using bootx one parameter passed on boot was 'no video driver" although I'm not sure how to do this w/ quik yet. BTW it takes a considerable time before the display is up and working on boot- i don't get a prompt even tho I've increased the timeout in quik.conf to 500. I can't see anything until the kernel has already started booting. It's as though the display driver is wrong somehow. The first of the kernel messages I see are:

initialiizng rt netlink socket

duno if that's of any help or not.

(II) imstt(0): Not using mode "832x624" (no mode of this name)
(--) imstt(0): Virtual size is 640x480 (pitch 640)
(**) imstt(0): Default mode "640x480": 36.0 MHz, 43.3 kHz, 85.0 Hz
(++) imstt(0): DPI set to (100, 100)

So it's woking at 640x480- hmmm not ideal but how to fix it?

Thanks for any ideas.