Re: [Cooker] Install Problem - DrakX v1.709
Andy Neillans [EMAIL PROTECTED] writes: [...] The installer crashes out with: in second stage install TOTO ??? install exited abnormally :-( sending termination signals...done sending kill signals...done [...] Any suggestions? try booting installation with linux noauto
RE: [Cooker] Install Problem - DrakX v1.709
try booting installation with linux noauto Now got a slightly different error, but it makes more sense! in second stage install unable to open /proc/bus/pci/devices You may have passed a wrong argument to the -p option. fopen() sets errno to: No such file or directory install exited abnormally :-( etc Well, the 'Shuttle' devices only have two PCI slots, both of which are empty on my machine. Not sure if the Onboard sound and NIC are 'PCI' devices... Andy
RE: [Cooker] Install problem
This seems to be the standard since 8.0 Tom -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Chris Edwards Sent: Wednesday, August 29, 2001 5:34 PM To: Cooker@Linux-Mandrake. Com Subject:[Cooker] Install problem When I mount a partition to root (/) it says it can't mount the partition (An error occured: mount failed: Device or resource busy). I have tried changing the partition type, I have tried it in text mode, and everything.. And still no work. It works fine when i mount it to a different location... ie /inst or /test or something, but then i can't proceed with install, cause i need a root partition... anyone else getting this? I'm using Cooker August 29th. From about 2 hours ago sync. -Chris
RE: [Cooker] Install problem
This seems to be the standard since 8.0 It was working fine for me a few weeks ago, but now it hates me :(. -chris
RE: [Cooker] Install problem
I tried again in expert mode. I got a message box in the boot install section : no such pseudo-hash field 'hds' When I look at the log by ctrl F3, I find the error : no such pseudo-hash field 'hds' /usr/bin/perl-install/any.pm line 92, line 7 I install from my hard disk. Could someone tell me what install script I can modify to skip the boot loader setup (I will boot from floppy). Jean-Claude -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]De la part de Jean-Claude Tual Envoyé : samedi 18 août 2001 13:18 À : [EMAIL PROTECTED] Objet : [Cooker] Install problem I just tried to nstall the last version of cooker. When arriving in the boot loader install, I got first a message concerning a db rpm and then a message box indicatng a bad hds hash. Impossible to continue, allways the message box. What going wrong ? Jean-Claude
Re: [Cooker] Install problem
Jean-Claude Tual [EMAIL PROTECTED] writes: I just tried to nstall the last version of cooker. When arriving in the boot loader install, I got first a message concerning a db rpm and then a message box indicatng a bad hds hash. Impossible to continue, allways the message box. What going wrong ? rpmlib seems to go crazy in same case. I don't understand why. In some case, it seems creating a local user made the bug disappear. But it was for printer configuration. I don't know :-( as for the bad hds hash, i need to know which fileline. You can find it in console 3.
Re: [Cooker] Install problem
Jean-Claude Tual [EMAIL PROTECTED] writes: When I look at the log by ctrl F3, I find the error : no such pseudo-hash field 'hds' /usr/bin/perl-install/any.pm line 92, line 7 ok, fixed.
Re: [Cooker] Install problem
Jean-Claude Tual [EMAIL PROTECTED] writes: When I look at the log by ctrl F3, I find the error : no such pseudo-hash field 'hds' /usr/bin/perl-install/any.pm line 92, line 7 ok, fixed.
RE: [Cooker] Install problem
The file line is : /usr/bin/perl-install/any.pm line 92, line 7 Jean-Claude -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Envoye : samedi 18 aout 2001 16:36 A : [EMAIL PROTECTED] Objet : Re: [Cooker] Install problem Jean-Claude Tual [EMAIL PROTECTED] writes: I just tried to nstall the last version of cooker. When arriving in the boot loader install, I got first a message concerning a db rpm and then a message box indicatng a bad hds hash. Impossible to continue, allways the message box. What going wrong ? rpmlib seems to go crazy in same case. I don't understand why. In some case, it seems creating a local user made the bug disappear. But it was for printer configuration. I don't know :-( as for the bad hds hash, i need to know which fileline. You can find it in console 3.
Re: [Cooker] Install problem with ATA/100
So sprach Peter Ruskin am Mon, Mar 05, 2001 at 09:30:44PM +: I have a Gigabyte GA-6BXE with two onboard controllers (diaabled) and a Promise Ultra 100 With 2.2 it's like this: Promise 1: hde, hdf Promise 2: hdg, hdh With 2.4 it's like this: Promise 1: hde, hdf Promise 2: hdg, hdh But that's not the default, is it? I have a Gigabyte BX2000 mobo, and I have the exact situation the original poster mentioned. Alexander Skwar -- How to quote: http://learn.to/quote (german) http://quote.6x.to (english) Homepage: http://www.digitalprojects.com | http://www.iso-top.de iso-top.de - Die guenstige Art an Linux Distributionen zu kommen Uptime: 2 days 14 hours 55 minutes
Re: [Cooker] Install problem with ATA/100
Mark Wormgoor wrote: There is a bug in the Mandrake 8.0 installation. The bug: the installation uses a 2.2 kernel, while 8.0 is on 2.4 Why this matters: I have an Asus P2BF with two onboard controllers and a Promise Ultra 100 with the second onboard disabled. With 2.2 it's like this: onboard 1: hda, hdb promise 1: hde, hdf promise 2: hdg, hdh With 2.4 it's like this: onboard 1: hda, hdb promise 1: hdc, hdd promise 2: hde, hdf This is very interesting, thanks! Ever since Promise appeared it has become obvious that Linux has to get away from absolute drive location naming and only name (hd?) devices in the order in which they are actually encountered, like Windows does. It seems that 2.4 kernel does this. Good! This results in a kernel panic on first boot. Need to boot using root= and edit lilo.conf and fstab manually. Second problem with the Promise Ultra 100 is that it needs ide3=noautotune (which has my cd-rom on it). Otherwise, it results in read errors on the cdrom and segmentation faults in rpm installations. You should shift your cdrom to the mobo secondary IDE and enable the secondary IDE in the BIOS. Promise does not include cdroms as permitted devices on IDE3 or IDE4. This would solve your other problems as well. -- Regards, Ron. [au]
Re: [Cooker] Install problem with ATA/100
Mark Wormgoor wrote: There is a bug in the Mandrake 8.0 installation. The bug: the installation uses a 2.2 kernel, while 8.0 is on 2.4 Why this matters: I have an Asus P2BF with two onboard controllers and a Promise Ultra 100 with the second onboard disabled. With 2.2 it's like this: onboard 1: hda, hdb promise 1: hde, hdf promise 2: hdg, hdh With 2.4 it's like this: onboard 1: hda, hdb promise 1: hdc, hdd promise 2: hde, hdf This is very interesting, thanks! Ever since Promise appeared it has become obvious that Linux has to get away from absolute drive location naming and only name (hd?) devices in the order in which they are actually encountered, like Windows does. It seems that 2.4 kernel does this. Good! I see you never have experienced the adding a harddrive syndrome. Absolute pads are way easier. What happens when you add an other drive on the onboard controller? This results in a kernel panic on first boot. Need to boot using root= and edit lilo.conf and fstab manually. Second problem with the Promise Ultra 100 is that it needs ide3=noautotune (which has my cd-rom on it). Otherwise, it results in read errors on the cdrom and segmentation faults in rpm installations. You should shift your cdrom to the mobo secondary IDE and enable the secondary IDE in the BIOS. Promise does not include cdroms as permitted devices on IDE3 or IDE4. This would solve your other problems as well. -- Regards, Ron. [au]
Re: [Cooker] Install problem with ATA/100
On Monday 05 March 2001 17:42, Ron Stodden wrote: Mark Wormgoor wrote: [] Why this matters: I have an Asus P2BF with two onboard controllers and a Promise Ultra 100 with the second onboard disabled. With 2.2 it's like this: onboard 1: hda, hdb promise 1: hde, hdf promise 2: hdg, hdh With 2.4 it's like this: onboard 1: hda, hdb promise 1: hdc, hdd promise 2: hde, hdf I have a Gigabyte GA-6BXE with two onboard controllers (diaabled) and a Promise Ultra 100 With 2.2 it's like this: Promise 1: hde, hdf Promise 2: hdg, hdh With 2.4 it's like this: Promise 1: hde, hdf Promise 2: hdg, hdh You can make the Promise use hda, hdb, hdc and hdd by configuring the kernel (use off-board chipsets first) or by using kernel boot parameters hd0= , etc. -- Linux Mandrake release 7.2 (Odyssey) for i586 KDE 2.1 Linux 2.2.17-27mdkWin4Lin, Uptime 3 hours 19 minutes
Re: [Cooker] install problem
Christopher Larson [EMAIL PROTECTED] writes: Not sure if this is an existing bug or not but I did an install on a machine with a Matrox g100 card in it and on the easy install it got to configuring X and looped on could not install XFree86 - RPM. yeah i know, bash me! Seems like this is quite old bug that i discovered yesterday, late, too late :( It is a Matrox Millenium 4mb agp card with the latest bios loaded from Matrox. you can workaround this in expert by choosing no pci probe.
Re: [Cooker] install problem
Pixel wrote: Christopher Larson [EMAIL PROTECTED] writes: Not sure if this is an existing bug or not but I did an install on a machine with a Matrox g100 card in it and on the easy install it got to configuring X and looped on could not install XFree86 - RPM. yeah i know, bash me! Seems like this is quite old bug that i discovered yesterday, late, too late :( I hope Mandrake 7 isn't final, there's still many bugs reported on this list that have not been resolved :( -- Sincerely, David Walluck [EMAIL PROTECTED]
