On Thu, 2004-09-09 at 09:09, Sven Luther wrote: > On Thu, Sep 09, 2004 at 03:43:21AM -0400, Russell Hires wrote: > > Package: installation-reports > > > > Debian-installer-version: rc1 > > uname -a: 2.4.25 > > Date: 9/8/04 > > Method: root.img floppy image, then netinst > > > > Machine: Apple Macintosh G3 > > Processor: 266 Mhz PowerPC G3 > > Memory: 384 > > Root Device: IDE /dev/hda6 > > Root Size/partition table: > > /dev/hda6 on / type ext3 (rw,errors=remount-ro) > > proc on /proc type proc (rw) > > devpts on /dev/pts type devpts (rw,gid=5,mode=620) > > tmpfs on /dev/shm type tmpfs (rw) > > usbfs on /proc/bus/usb type usbfs (rw) > > /dev/hda10 on /home type ext3 (rw) > > /dev/hda9 on /tmp type ext3 (rw) > > /dev/hda7 on /usr type ext3 (rw) > > /dev/hda8 on /var type ext3 (rw) > > > > Output of lspci and lspci -n: > > lspci > > 0000:00:00.0 Host bridge: Motorola MPC106 [Grackle] (rev 40) > > 0000:00:0d.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01) > > 0000:00:0e.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 > > Controller (rev 50) > > 0000:00:0e.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 > > Controller (rev 50) > > 0000:00:0e.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 51) > > 0000:00:0f.0 Ethernet controller: 3Com Corporation 3c590 10BaseT [Vortex] > > 0000:00:10.0 ff00: Apple Computer Inc. Heathrow Mac I/O (rev 01) > > 0000:00:12.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP > > (rev 5c) > > > > lspci -n > > 0000:00:00.0 0600: 1057:0002 (rev 40) > > 0000:00:0d.0 0300: 121a:0005 (rev 01) > > 0000:00:0e.0 0c03: 1106:3038 (rev 50) > > 0000:00:0e.1 0c03: 1106:3038 (rev 50) > > 0000:00:0e.2 0c03: 1106:3104 (rev 51) > > 0000:00:0f.0 0200: 10b7:5900 > > 0000:00:10.0 ff00: 106b:0010 (rev 01) > > 0000:00:12.0 0300: 1002:4750 (rev 5c) > > > > > > > > Base System Installation Checklist: > > [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it > > > > Initial boot worked: [ ] > > Configure network HW: [ ] > > Config network: [ ] > > Detect CD: [ ] > > Load installer modules: [ ] > > Detect hard drives: [ ] > > Partition hard drives: [ ] > > Create file systems: [ ] > > Mount partitions: [ ] > > Install base system: [ ] > > Install boot loader: [ ] > > Reboot: [ ] > > > > Comments/Problems: > > > > What a major pain! This was sooo much easier to when it was woody. To start with, > > I'll have to submit some info on installing w/ BootX > > for the other hapless souls out there who try to install on a beige G3... > > Well, there have been various success reports with installing bootX, but sure, > the documentation is utherly broken still on powerpc, since i guess nobody > found the time to work on it.
Well, I will hopefully in the next week or so. > > I had to play around with getting started, as the docs don't yet reflect the > > changes wrought. So...the 2.6.7 kernel doesn't work with my > > G3/266, as I've got a voodoo3 card, and I get no video. I mentioned in another > > email that I'll set up a serial console to figure out > > what's up with that, but I won't be able to fix it. I've not had any success with > > 2.6.x kernels and voodoo3. I just get a blank screen. > > So, I used a 2.4.25 kernel with ext3 compiled in. > > Ok, be a bit more precise here. What voodoo do you have ? Does using offb work ? > And are you doing this in the installed system or in d-i ? > I have a Voodoo3 card 0000:00:0d.0 VGA compatible controller: 3Dfx Interactive, Inc. Voodoo 3 (rev 01) I don't know about the offb thing, though...I installed to a preformatted Maxtor 80 GB disk with about 20 GB for a Mac OS hfs partition. The other 60 GB were free space used by d-i. > Voodoo powerpc support is shaky at best, so there is no wonder that you don't > have much luch with them, but could you send me the dmesg output of your > kernel please. > [1] see end of message > Also, i don't understand what kernels you are using. Current d-i kernels are > 2.6.8-4 and 2.4.25-8 (soon to be moved to 2.4.27-1). Both of those have voodoo > framebuffer devices built in, but acceleration is broken, i think, don't > remember if it is enabled or not in those kernels you are using. > yeah, acceleration is broken, so I just put into the BootX command line 'noaccel' so my console text is okay. I didn't try to boot using the d-i 2.4 kernels. I didn't realize that 2.4 in the tree meant the kernel version. > Please provide more details of what exactly you do. > > > Using BootX, I booted with root.img as my start image off the hard drive as the > > ramdisk. No matter how many different ways I tried, > > the initrd.gz ramdisk never worked for my install. I would get a kernel panic > > about ... something. I saw a similar message to mine in an > > archive after googling for it, but it didn't mean anything. What filesystem does > > initrd.gz use, anyway? What must be compiled into the > > kernel for this to work? > > Have you tried : > > using miboot floppies from : > > http://people.debian.org/~luther/d-i/images/daily/powerpc/floppy-2.4/ > no > Using bootx with the vmlinux and initrd.gz from : > > http://people.debian.org/~luther/d-i/images/daily/powerpc/netboot/ > yes...utter failure. initrd.gz chokes, no ramdisk loads, kernel panic... > or > > http://people.debian.org/~luther/d-i/images/daily/powerpc/cdrom/ > > And what about the 2.4 versions of the above : > > http://people.debian.org/~luther/d-i/images/daily/powerpc/netboot/2.4/ > > or > > http://people.debian.org/~luther/d-i/images/daily/powerpc/cdrom/2.4/ > > > Which root.img and kernel where you using with BootX ? Whatever you do this is > not the correct way of booting. The root.img is exclusively to be used with > the miboot booting method. Wrong...it worked, so I don't think it's wrong. I don't like the fact that debian is trying to shoe horn people into certain ways of doing something. I did BootX with root.img as the ramdisk. I chose the "options" button in BootX, found my root.img on an hfs partition, click okay, then the 'Linux' button. Poof! I'm booting into the installer. As for the version, some time around 8/31/04. > > The thing about the root.img is that the assumption is that you'll continue to use > > floppies. Since I faked out the system by using BootX > > to load the ramdisk image into memory, I figured I could switch over to getting > > the other things I need from a CD that I'd burned. But > > that didn't work, since apparently "once a floppy install, always a floppy > > install." Fortunately, I didn't need any other drivers from > > any other floppy. Also, I found that /target doesn't seem to hold on to settings > > like mounting /dev/cdrom onto /floppy...once you exit > > the console to go back to the installer, it's gone. > > Sure, since it is a floppy initrd. You should use either the cdrom or netboot > initrd if you are going to do the BootX stuff, depending on if you want to do > an installation from sarge CDs or the network. Others where able to do this > without too much trouble, so i don't understand what your problem is. > You're right about this, but I did try, and it didn't work. I would love to find out what others have done, but the archive for the last year doesn't seem to have too much in it that pertains to my situation. I have a CD that I burned from an ISO, but that initrd.gz died just as bad as any other method, except for what worked for me above. Again, I would like it if I could switch from the root.img to cd or network from there. > > I didn't like the way that skipping the "install additional drivers from floppy" > > kept giving me the red screen that gave dire warnings > > of a failed step. Woody did that better, too, with a list of items, and that one > > just staying at the top. Once I've skipped a step, I > > don't need to be reminded over and over that I've skipped it. I did eventually get > > to the next step and completed the install, but ... > > Well, i dare to say that if you used a non-matching sets of floppies on woody, > it would fail as surely as it failed for you here. > That's the thing. Everything I needed in woody was there. root.bin was the ramdisk. If I needed to mount something (like an extra hd or cd) I could, and it would stick, and I could get it. I had to do this with the woody install when it was still in beta to get my pppoe to work. > > As far as getting the install: in two or three of the apt lists, England, aka UK, > > aka United Kingdom, aka Great Britain, aka Britain... > > is listed all over the place in its various forms. It should be consistent > > throughout with the same name. And why not be able to add a > > second/third apt source? > > Because the d-i package retriever is not able to use more than one apt source. > The second stage installer after the reboot will reask you about apt sources > anyway. > I don't think it did that. > > And what's up with having to have your root partition be ext2 in order to install > > quik? It doesn't seem that debian wants to play nice > > with the other OS I have running on my computer (Mac OS), either. I put ext3 on > > all my partitions (the default)...there should be some > > explanation of why you chose ext3 as the default, and how to change it to > > something else. The partitioning program seemed a bit slow > > in doing its thing. The partition program also didn't allow a surface check of the > > disk, which I needed...I've been having problems with > > my disk, so on an install this would have been a good thing. I didn't want to go > > back to woody for just this one thing. I think I was > > just having problems with xfs filesystem though, as I haven't had any with ext3. > > This is a quik-installer issue, i have not (yet) any idea about this. I have a > 8200/120 sitting here, but i still lack a keyboard and vga adapter to make use > of it. > I've got a kajillion keyboards for mac, if you want one. I think I've got an adapter, too, just let me know...are you in the US? Russell > > Last thing is that I tried to install the Desktop system from Tasksel, and none of > > the desktop stuff installed because one package, > > kdegraphics, didn't install. That's just stupid. The whole thing shouldn't fail > > because one package is missing. > > Known problem, if the buildd will not provide this soon, i will make the > upload. > > Friendly, > > Sven Luther [1] Memory BAT mapping: BAT2=256Mb, BAT3=128Mb, residual: 0Mb Total memory = 384MB; using 1024kB for hash table (at c0400000) Linux version 2.4.25 ([EMAIL PROTECTED]) (gcc version 3.3.3 (Debian)) #1 Fri Mar 12 21:18:53 EST 2004 Found a Heathrow mac-io controller, rev: 1, mapped at 0xfdc80000 PowerMac motherboard: PowerMac G3 (Silk) Found Grackle (MPC106) PCI host bridge at 0x80000000. Firmware bus number: 0->0 L2CR overriden (0xa9100000), backside cache is enabled On node 0 totalpages: 98304 zone(0): 98304 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/hda6 video=tdfx:[EMAIL PROTECTED] keyboard_sends_linux_keycodes=1 noaccel System has 64 possible interrupts GMT Delta read from XPRAM: -240 minutes, DST: on via_calibrate_decr: ticks per jiffy = 167082 (1002492 ticks) Console: colour dummy device 80x25 Calibrating delay loop... 534.11 BogoMIPS Memory: 383608k available (2540k kernel code, 1228k data, 168k init, 0k highmem) Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) Inode cache hash table entries: 32768 (order: 6, 262144 bytes) Mount cache hash table entries: 512 (order: 0, 4096 bytes) Buffer cache hash table entries: 32768 (order: 5, 131072 bytes) Page-cache hash table entries: 131072 (order: 7, 524288 bytes) POSIX conformance testing by UNIFIX PCI: Probing PCI hardware PCI: Cannot allocate resource region 1 of device 00:12.0 PCI: moved device 00:12.0 resource 1 (101) to 1400 PCI: Via IRQ fixup for 00:0e.0, from 24 to 8 PCI: Via IRQ fixup for 00:0e.1, from 24 to 8 Macintosh CUDA driver v0.5 for Unified ADB. Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Initializing RT netlink socket Thermal assist unit using timers, shrink_timer: 200 jiffies Starting kswapd Journalled Block Device driver loaded devfs: v1.12c (20020818) Richard Gooch ([EMAIL PROTECTED]) devfs: boot_options: 0x0 Installing knfsd (copyright (C) 1996 [EMAIL PROTECTED]). SGI XFS with no debug enabled fb: Voodoo3 memory = 16384K tdfxfb: reserving 1024 bytes for the hwcursor at d9ffe000 Console: switching to colour frame buffer device 128x48 fb0: 3Dfx Voodoo3 frame buffer device atyfb: using auxiliary register aperture atyfb: 3D RAGE PRO (PQFP, PCI) [0x4750 rev 0x7c] 6M SGRAM, 14.31818 MHz XTAL, 230 MHz PLL, 100 Mhz MCLK, 100 Mhz XCLK atyfb: monitor sense=73f, mode 6 fb1: ATY Mach64 frame buffer device on PCI MacOS display is /pci/3Dfx,Voodoo3 Using unsupported 1024x768 3Dfx,Voodoo3 at 90d00000, depth=32, pitch=4096 fb2: Open Firmware frame buffer device on /pci/3Dfx,Voodoo3 input0: Macintosh mouse button emulation pty: 256 Unix98 ptys configured Generic RTC Driver v1.07 RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize loop: loaded (max 8 devices) eth0: BMAC at 00:05:02:83:0d:84 PCI: Enabling device 00:0f.0 (0004 -> 0005) 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html See Documentation/networking/vortex.txt 00:0f.0: 3Com PCI 3c590 Vortex 10Mbps at 0x1000. Vers LK1.1.18-ac 00:0f.0: Overriding PCI latency timer (CFLT) setting of 32, new value is 248. 00:20:af:f0:76:bc, IRQ 25 product code 4244 rev 00.0 date 06-02-94 Internal config register is 200d2, transceivers 0xe108. 32K byte-wide RAM 1:1 Rx:Tx split, 10baseT interface. 00:0f.0: scatter/gather disabled. h/w checksums disabled pcnet32.c:v1.27a 10.02.2002 [EMAIL PROTECTED] PPP generic driver version 2.4.2 PPP Deflate Compression module registered [drm] Initialized tdfx 1.0.0 20010216 on minor 0 Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx ide0: Found Apple Heathrow ATA controller, bus ID 0 ide1: Found Apple Heathrow ATA controller, bus ID 1 Probing IDE interface ide0... hda: Maxtor 6Y080P0, ATA DISK drive Unhandled interrupt d, disabled hda: Enabling MultiWord DMA 2 Probing IDE interface ide1... hdc: MATSHITADVD-ROM SR-8582, ATAPI CD/DVD-ROM drive hdd: Maxtor 90845D4, ATA DISK drive Unhandled interrupt e, disabled hdc: Enabling MultiWord DMA 2 hdd: Enabling MultiWord DMA 2 ide0 at 0xdbb0e000-0xdbb0e007,0xdbb0e160 on irq 13 ide1 at 0xdbb12000-0xdbb12007,0xdbb12160 on irq 14 hda: attached ide-disk driver. hda: host protected area => 1 hda: 160086528 sectors (81964 MB) w/7936KiB Cache, CHS=158816/16/63, (U)DMA hdd: attached ide-disk driver. hdd: host protected area => 1 hdd: 16514064 sectors (8455 MB) w/512KiB Cache, CHS=16383/16/63, (U)DMA hdc: attached ide-cdrom driver. hdc: ATAPI 24X DVD-ROM drive, 512kB Cache, DMA Uniform CD-ROM driver Revision: 3.12 Partition check: /dev/ide/host0/bus0/target0/lun0: [mac] p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 /dev/ide/host1/bus0/target1/lun0: [mac] p1 p2 p3 p4 p5 p6 p7 p8 p9 SCSI subsystem driver Revision: 1.00 scsi0 : SCSI host adapter emulation for IDE ATAPI devices mesh: configured for synchronous 5 MB/s mesh: performing initial bus reset... scsi1 : MESH mesh: target 2 synchronous at 5.0 MB/s Vendor: QUANTUM Model: FIREBALL SE4.3S Rev: PJ0A Type: Direct-Access ANSI SCSI revision: 02 Attached scsi disk sda at scsi1, channel 0, id 2, lun 0 SCSI device sda: 8443592 512-byte hdwr sectors (4323 MB) /dev/scsi/host1/bus0/target2/lun0: [mac] p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 Macintosh non-volatile memory driver v1.0 usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb.c: registered new driver hid hid-core.c: v1.8.1 Andreas Gal, Vojtech Pavlik <[EMAIL PROTECTED]> hid-core.c: USB HID support drivers mice: PS/2 mouse device common for all mice NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 4096 buckets, 32Kbytes TCP: Hash tables configured (established 32768 bind 65536) NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. adb: starting probe task... kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode. VFS: Mounted root (ext3 filesystem) readonly. Freeing unused kernel memory: 168k init 4k chrp 36k prep adb devices: [2]: 2 2 [3]: 3 1 ADB keyboard at 2, handler set to 3 Detected ADB keyboard, type ANSI. input1: ADB HID on ID 2:2.02 ADB mouse at 3, handler set to 4 input2: ADB HID on ID 3:3.01 adb: finished probe task... Adding Swap: 500800k swap-space (priority -1) Adding Swap: 102396k swap-space (priority -2) EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,6), internal journal kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,10), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,9), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,7), internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS 2.4-0.9.19, 19 August 2002 on ide0(3,8), internal journal EXT3-fs: mounted filesystem with ordered data mode. phy registers: 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 Unable to identify CD-ROM format. EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
