okay, i rebuit for the right processor this time :) still hangs at the same place. worse off than i was with the mandrake kernel and initrd image.
i've been thinking about moving /boot over to the ide drive. is this all i would have to do (besides telling bootx where to boot from) to bypass this whole scsi issue? that way i could tell if it's really a scsi issue or something else with my machine. thanks again. -c ----- Original Message ----- From: "Stew Benedict" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, September 26, 2001 10:15 AM Subject: Re: problems with 2.4 kernel on oldworld mac > On Wed, 26 Sep 2001, Chris Mann wrote: > > > okay, i tried building my own kernel from the 2.4.4-6.4mdk source rpms. > > first i did a make config. > > i left everything as default except for the following scsi settings, which i > > changed to Y: > > SCSI disk support > > SCSI generic support > > MESH (Power Mac internal SCSI) support > > 53C94 (Power Mac external SCSI) support > > > > one thing i wasn't sure about was the Processor Type. You've got a choice > > between 6xx/7xx/74xx/8260, POWER3, POWR4, and 8xx. I went with POWER3, > > cause I'm assuming that means G3 and this machine has a G3 upgrade, but I'm > > not sure. > > Nope - should have checked the help: > > CONFIG_6xx: > x > x > x > x There are four types of PowerPC chips supported. The more common > x > x types (601, 603, 604, 740, 750, 7400), the Motorola embedded versions > x > x (821, 823, 850, 855, 860, 8260), the IBM embedded versions (403 and > x > x 405) and the high end 64 bit Power processors (Power 3, Power 4). > x > x Unless you are building a kernel for one of the embedded processor > x > x systems, or a 64 bit IBM RS/6000, choose 6xx. Note that the kernel > x > x runs in 32-bit mode even on 64-bit chips. > > Stick with 6xx/7xx/74xx/8260 > > > Then make mrproper, make dep make clean, make vmlinux, make modules, make > > modules-install. (i also changed the extra version number for the kernel so > > it woulnd't overwrite teh mandrake version) > > > > moved the kernel and system map over to /boot (vmlinx-2.4.4-6.4scsi and > > System.map-2.4.4-6.4scsi) and copied the kernel over to the System > > Folder:Linux Kernels folder on the mac side. Select that kernel in BootX > > when rebooting and the machine hangs at this point: > > > > Welcome to Linux, kernel 2.4.4-6.4scsi > > started at : 0x00000000 > > linked at : 0xc0000000 > > frame buffer at : 0x81801400 (phys), 0x81801400 (log) > > klimit : 0xc02cbb30 > > MSR : 0x00000042 > > HID0 :0x80000c204 > > ICTC : 0x00000000 > > > > booting... > > > > which is worse than what i was getting with the default mandrake 2.4 kernel, > > but about what i got with the benh 2.4 kernel. does BootX take care of > > changing the symbolic links for System.map and vmlinux or should i do that > > myself. and also what should the file persmissions be on the System.map > > files. some are read write and others are just read. > > > > Well nothing should need to write to System.map, only read. The init > scripts setup the symlink on a successful boot - rc.sysinit > > Try with the right processor type and see what happens. > > Stew Benedict > > -- > MandrakeSoft OH/TN, USA http://perso.mandrakesoft.com/~sbenedict/ > PPC Faq: http://marc.theaimsgroup.com/?l=mandrake-cooker-ppc&m=99441208917647&w= > >
