Re: Powerbook 3400: installer crash, everytime.
Yello On Wed, 03 Apr 2002 11:27:05 +0200 Henrik Farre [EMAIL PROTECTED] wrote: If neither kernel works for you. there's not a lot I can do. The current kernel seems to work pretty well across a variety of machines. If you have a monolithic BenH kernele you built on one of your other distributions, you could give that a try. Other than that, I would start to suspect media or hardware problems, I got mdk 8.0 installed, but when it runs Aurora it locks up. I have tryed to enter 'single' and 'linux single' in bootx kernel args but I can't get into single user mode. -- Mvh. / Kind regards Henrik Farre enrique AT obel DOT auc DOT dk - If I were God, I would recompile the penguin with --enable-flying.
Powerbook 3400: installer crash, everytime.
Yello I have a powerbook 3400 (240Mhz, 80Mb ram, 3GB hd.), on which I'm trying to install mdk 8.2b2, but the installer crashes everytime I try. Here is what I did: First of all, if I try to unsit the file BootX/Mandrake Linux Install.sit it returns a error nr. -39 (great error code :), so I use BootX 1.2.3 from YellowdogLinux 2.1, copyed the files from the mdk cd to the systemfolder (initrd-2.4.18-6mdk.img to Systemfolder/ and vmlinuz-2.4.18-6mdk to Systemfolder/Linux Kernels/). I launch BootX, select the mdk kernel and the mdk ramdisk (size 32000 ??). Then linux boots and I get these errors: mesh: target 0 aborted scsi: device set offline - command error recover failed: host 0 channel 0 id 1 lun 0 ... (cut) scsi: device set offline - command error recover failed: host 0 channel 0 id 6 lun 0 Loading mac53c94 module /lib/mac53c94.o: init_module: No such device Hint: insmod (cut) ERROR: /bin/insmod exited abnormally ... (cut) pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2 ... (cut) Kernel panic: No init found. Try passing init= option to the kernel So I tryed to copy the files from the boot folder on the mdk cd, vmlinux to Systemfolder/Linux Kernels and all.gz to Systemfolder, and select them in bootx. Futher more I have to add boot:install-text to kernel args in bootx and select no video, else I can't get text install working. I select cdrom install, and the install program loads. Then I get a black screen saying: Oops: machine check, sig:7 ...(cut) and 10 lines of debuging output. If I switch to the first consol (Command-F1) I get the text installer. I work my way through the installation, partitions and package selection works, but after a fewl packages has been installed it crashes, debugin info flashes by, and the last line says: Kernel panic: Attempted to kill init! 0Rebooting in 180 seconds.. What to do?? I have no net access from the powerbook, nor does I have a floppy drive that works. -- Mvh. / Kind regards Henrik Farre enrique AT obel DOT auc DOT dk - If I where God, I would recompile the penguin with --enable-flying.
Re: Powerbook 3400: installer crash, everytime.
On Tue, 2 Apr 2002, Henrik Farre wrote: Yello I have a powerbook 3400 (240Mhz, 80Mb ram, 3GB hd.), on which I'm trying to install mdk 8.2b2, but the installer crashes everytime I try. Here is what I did: First of all, if I try to unsit the file BootX/Mandrake Linux Install.sit it returns a error nr. -39 (great error code :), so I use BootX 1.2.3 from YellowdogLinux 2.1, copyed the files from the mdk cd to the systemfolder (initrd-2.4.18-6mdk.img to Systemfolder/ and vmlinuz-2.4.18-6mdk to Systemfolder/Linux Kernels/). I launch BootX, select the mdk kernel and the mdk ramdisk (size 32000 ??). Then linux boots and I get these errors: Definitely not the right approach - that kernel and initrd are for the installed system. mesh: target 0 aborted scsi: device set offline - command error recover failed: host 0 channel 0 id 1 lun 0 ... (cut) scsi: device set offline - command error recover failed: host 0 channel 0 id 6 lun 0 Loading mac53c94 module /lib/mac53c94.o: init_module: No such device Hint: insmod (cut) ERROR: /bin/insmod exited abnormally ... (cut) pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2 ... (cut) Kernel panic: No init found. Try passing init= option to the kernel So I tryed to copy the files from the boot folder on the mdk cd, vmlinux to Systemfolder/Linux Kernels and all.gz to Systemfolder, and select them in bootx. Futher more I have to add boot:install-text to kernel args in bootx and select no video, else I can't get text install working. I select cdrom install, and the install program loads. Then I get a black screen saying: A little hard to resond with no line wrap on your message, but your BootX arguments are not correct. ramdisk size should be 34000 to do a text install, simply the work text So if I understand you correctly, stage1 loads, you select stage2 from CDROM, which loads, then you have a kernel panic? that's ort of an odd place, but if you didn't specify the above ramdisk size, you may have just overrun your ramdisk loading stage2. Oops: machine check, sig:7 ...(cut) and 10 lines of debuging output. If I switch to the first consol (Command-F1) I get the text installer. I work my way through the installation, partitions and package selection works, but after a fewl packages has been installed it crashes, debugin info flashes by, and the last line says: Kernel panic: Attempted to kill init! 0Rebooting in 180 seconds.. What to do?? I have no net access from the powerbook, nor does I have a floppy drive that works. Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
Re: Powerbook 3400: installer crash, everytime.
Yello On Tue, 02 Apr 2002 12:44:29 -0500 (EST) Stew Benedict [EMAIL PROTECTED] wrote: Definitely not the right approach - that kernel and initrd are for the installed system. Which one is the right one then?? I work ok with vmlinux and all.gz A little hard to resond with no line wrap on your message, but your BootX arguments are not correct. no line wrap? I have wrap set to 74 chars ramdisk size should be 34000 to do a text install, simply the work text Ok, done that. I just used the info on: http://www.linux-mandrake.com/en/demos/PPC/Install/pages/install5.php3 So if I understand you correctly, stage1 loads, you select stage2 from CDROM, which loads, then you have a kernel panic? that's ort of an odd place, but if you didn't specify the above ramdisk size, you may have just overrun your ramdisk loading stage2. The same thing happens. While installing libglib (I think that was the one) it crashes. -- Mvh. / Kind regards Henrik Farre enrique AT obel DOT auc DOT dk - If I where God, I would recompile the penguin with --enable-flying.
Re: Powerbook 3400: installer crash, everytime.
On Tue, Apr 02, 2002 at 08:34:43PM +0200, Henrik Farre wrote: no line wrap? I have wrap set to 74 chars That probably on wraps your display. You need to set your editor to wrap the lines for you before it sends them. And in case you don't beleive us: [breser@gyrus breser]$ wc --max-line-length email.henrik 298 email.henrik email.henrik was your previous email. The longest line was 298 characters. -- Ben Reser [EMAIL PROTECTED] http://ben.reser.org What difference does it make to the dead, the orphans, and the homeless, whether the mad destruction is wrought under the name of totalitarianism or the holy name of liberty and democracy? - Ghandi
Re: Powerbook 3400: installer crash, everytime.
On Tue, 2 Apr 2002, Henrik Farre wrote: Yello On Tue, 02 Apr 2002 12:44:29 -0500 (EST) Stew Benedict [EMAIL PROTECTED] wrote: Definitely not the right approach - that kernel and initrd are for the installed system. Which one is the right one then?? I work ok with vmlinux and all.gz Those are fine. A little hard to resond with no line wrap on your message, but your BootX arguments are not correct. no line wrap? I have wrap set to 74 chars OK, when I went to reply it was all one long line. No biggie. ramdisk size should be 34000 to do a text install, simply the work text Ok, done that. I just used the info on: http://www.linux-mandrake.com/en/demos/PPC/Install/pages/install5.php3 So if I understand you correctly, stage1 loads, you select stage2 from CDROM, which loads, then you have a kernel panic? that's ort of an odd place, but if you didn't specify the above ramdisk size, you may have just overrun your ramdisk loading stage2. The same thing happens. While installing libglib (I think that was the one) it crashes. How much RAM in this machine? I can't say I've ever seen a panic during package install either, but maybe something with your hardware and the kernel just don't get along. Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
Re: Powerbook 3400: installer crash, everytime.
On Tue, 02 Apr 2002 10:41:25 -0800 Ben Reser [EMAIL PROTECTED] wrote: On Tue, Apr 02, 2002 at 08:34:43PM +0200, Henrik Farre wrote: no line wrap? I have wrap set to 74 chars That probably on wraps your display. You need to set your editor to wrap the lines for you before it sends them. Thanx for the info I have fixed that. The longest line was 298 characters. Nasty -- Mvh. / Kind regards Henrik Farre enrique AT obel DOT auc DOT dk - If I where God, I would recompile the penguin with --enable-flying.
Re: Powerbook 3400: installer crash, everytime.
On Tue, 2 Apr 2002, Henrik Farre wrote: Yello On Tue, 02 Apr 2002 14:19:43 -0500 (EST) Stew Benedict [EMAIL PROTECTED] wrote: That should be enough. It could be something in the mdk kernel and your hardware, or something else going on. you could also try the 2.2 kernel and stage1 image, or post some details of the panic that happens during package install. If I try to use the 2.2 kernel the installer can't access the cdrom drive... I have tryed to insmod diffrent modules but they all fail. If mesh works for kernel2.4, it should be the same for 2.2. Ok here is what I do: Use vmlinux and all.gz from the mdk cd, ramdisk size 34000, kernel args set to text. I select: danish keymap expert install mesh scsi is installed, I select no to add another interface Busmouse|1 button ok to mouse button emulation (default settings) Dansk as keyboard layout High security Use exiting partitions. (have partitions set up) set hda9 as / (hda8 is swap) formats hda9 deselects have second cd (well I have, but lets get cd1 running first :) deselects everything else than other graphical envrioments Are you really unselecting everything but other graphical environments? You might want to try going with the recommended package list initially. just select ok in package selection ... the installer starts ... installes some packages then crashes at libglib, producing a lot of output (the screen scrolles): Oops: kernel access of bad area, sig: 11 NIP... (cut) TASk = c055a000[12] 'runinstall2' Last syscall: 107 ... (cut) install exited abnormally :-( -- recived signal 11 sending termination signals...Oops: kernel access of bad area, sig: 11 NIP... (cut) TASK = c0396000[11] 'linuxrc' Last syscall: 82 ... (cut) done sending kill signals...done unmounting...(cut) failed to umount some filesystems (the end) What to do now? If neither kernel works for you. there's not a lot I can do. The current kernel seems to work pretty well across a variety of machines. If you have a monolithic BenH kernele you built on one of your other distributions, you could give that a try. Other than that, I would start to suspect media or hardware problems, Stew Benedict -- MandrakeSoft PPC FAQ: http://www.linux-mandrake.com/en/demos/PPC/FAQ/
Re: Powerbook 3400: installer crash, everytime.
Yello On Tue, 02 Apr 2002 15:29:32 -0500 (EST) Stew Benedict [EMAIL PROTECTED] wrote: If mesh works for kernel2.4, it should be the same for 2.2. Yeah probaly, but I think the cdrom drive in the powerbook is ata? Are you really unselecting everything but other graphical environments? You might want to try going with the recommended package list initially. Have also tryed the default settings. If neither kernel works for you. there's not a lot I can do. The current kernel seems to work pretty well across a variety of machines. If you have a monolithic BenH kernele you built on one of your other distributions, you could give that a try. Other than that, I would start to suspect media or hardware problems, I will try that. If ydl and debian work, then mdk should work. -- Mvh. / Kind regards Henrik Farre enrique AT obel DOT auc DOT dk - If I where God, I would recompile the penguin with --enable-flying.
