RE: [expert] Booting from HPT366 drive...
..just wondering what motherboard you have?? abit BE6?? I to was trying to install via udma66, but I wasn't sure how to use the udma66 package when I was installing?? I was thinking it could be done in expert mode, but I am no expert yet. Let me know if/how your install went, Thanks. Tim Wojtaszek -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Axalon Bloodstone Sent: Saturday, October 23, 1999 2:03 AM To: [EMAIL PROTECTED] Subject: Re: [expert] Booting from HPT366 drive... On Fri, 22 Oct 1999, Steve Philp wrote: > Axalon Bloodstone wrote: > > > > On Fri, 22 Oct 1999, Axalon Bloodstone wrote: > > > > > On Fri, 22 Oct 1999, Steve Philp wrote: > > > > > > [big snip] > > > > > > > So, I've now moved the UDMA/66 drive onto the normal cable and the > > > > install there went just fine. Booting works also, so I'll wait a bit > > > > before I screw it up again. :) > > > > > > I'll have info in .. installer says 9mins > > > Will let ya know > > > > Ok i was successfull. > > Just tryed to isolate if it was bios boot sequence and it has zero effect. > > What was your ide layout, i've already moved cdrom to 2nd slave, was there > > still hd's on the dma33 chains? > > Nope, no other HD's. The only things in the system when I attempted the > install/boot on the UDMA/66 interface were the Zip drive on hdc and the > CDROM on hdd. ide zip drive? I finally got the 'Li' i installed a drive onto the primary ide and reinstalled lilo, you get the warning 'hde is not the first harddrive' (note just crawled out of bed so thats posibly not exact) I had to remove the drive, boot from floppy and reinstall lilo, reinstall the drive, and she boots. Now if only i could remeber the lilo option to tell it hde is the bios boot drive we'd both be all set -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
Re: [expert] Booting from HPT366 drive...
On Sat, Oct 23, 1999 at 01:02:59AM -0600, Axalon Bloodstone wrote: > On Fri, 22 Oct 1999, Steve Philp wrote: > > > Axalon Bloodstone wrote: > > > > > > On Fri, 22 Oct 1999, Axalon Bloodstone wrote: > > > > > > > On Fri, 22 Oct 1999, Steve Philp wrote: > > > > > > > > [big snip] > > > > > > > > > So, I've now moved the UDMA/66 drive onto the normal cable and the > > > > > install there went just fine. Booting works also, so I'll wait a bit > > > > > before I screw it up again. :) > > > > > > > > I'll have info in .. installer says 9mins > > > > Will let ya know > > > > > > Ok i was successfull. > > > Just tryed to isolate if it was bios boot sequence and it has zero effect. > > > What was your ide layout, i've already moved cdrom to 2nd slave, was there > > > still hd's on the dma33 chains? > > > > Nope, no other HD's. The only things in the system when I attempted the > > install/boot on the UDMA/66 interface were the Zip drive on hdc and the > > CDROM on hdd. > > ide zip drive? Yup. I can move it off this system if it's going to make a difference. > I finally got the 'Li' i installed a drive onto the primary ide and > reinstalled lilo, you get the warning 'hde is not the first harddrive' > (note just crawled out of bed so thats posibly not exact) I had to remove > the drive, boot from floppy and reinstall lilo, reinstall the drive, and > she boots. Now if only i could remeber the lilo option to tell it hde is > the bios boot drive we'd both be all set Was it that "bios=0x80" thing? I tried it, but might have gotten the option wrong, I think I used "bios=0x84" since it was actually hde. Maybe I'll give it another try with the drive on the UDMA/66 interface and put that bios=0x80 into LILO. The bad part is that I'm having to muck with all of this _after_ an installation, but before I can actually boot the system. To work with the system, I'm starting the installation CD routing up to the mounting the installation CD, then switching to VC 2 and mounting the hde partition onto mount, chroot /mnt /bin/bash and you've got yourself working in your newly installed system! I'll play with the thing a bit more tonight, I haven't built up enough "junk" in this install to worry about wiping it in the name of "research" :) Thanks for the help Axalon! -- Steve Philp Network Administrator Advance Packaging Corporation [EMAIL PROTECTED]
Re: [expert] Booting from HPT366 drive...
On Fri, 22 Oct 1999, Steve Philp wrote: > Axalon Bloodstone wrote: > > > > On Fri, 22 Oct 1999, Axalon Bloodstone wrote: > > > > > On Fri, 22 Oct 1999, Steve Philp wrote: > > > > > > [big snip] > > > > > > > So, I've now moved the UDMA/66 drive onto the normal cable and the > > > > install there went just fine. Booting works also, so I'll wait a bit > > > > before I screw it up again. :) > > > > > > I'll have info in .. installer says 9mins > > > Will let ya know > > > > Ok i was successfull. > > Just tryed to isolate if it was bios boot sequence and it has zero effect. > > What was your ide layout, i've already moved cdrom to 2nd slave, was there > > still hd's on the dma33 chains? > > Nope, no other HD's. The only things in the system when I attempted the > install/boot on the UDMA/66 interface were the Zip drive on hdc and the > CDROM on hdd. ide zip drive? I finally got the 'Li' i installed a drive onto the primary ide and reinstalled lilo, you get the warning 'hde is not the first harddrive' (note just crawled out of bed so thats posibly not exact) I had to remove the drive, boot from floppy and reinstall lilo, reinstall the drive, and she boots. Now if only i could remeber the lilo option to tell it hde is the bios boot drive we'd both be all set -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
Re: [expert] Booting from HPT366 drive...
Axalon Bloodstone wrote: > > On Fri, 22 Oct 1999, Axalon Bloodstone wrote: > > > On Fri, 22 Oct 1999, Steve Philp wrote: > > > > [big snip] > > > > > So, I've now moved the UDMA/66 drive onto the normal cable and the > > > install there went just fine. Booting works also, so I'll wait a bit > > > before I screw it up again. :) > > > > I'll have info in .. installer says 9mins > > Will let ya know > > Ok i was successfull. > Just tryed to isolate if it was bios boot sequence and it has zero effect. > What was your ide layout, i've already moved cdrom to 2nd slave, was there > still hd's on the dma33 chains? Nope, no other HD's. The only things in the system when I attempted the install/boot on the UDMA/66 interface were the Zip drive on hdc and the CDROM on hdd. -- Steve Philp Network Administrator Advance Packaging Corporation [EMAIL PROTECTED]
Re: [expert] Booting from HPT366 drive...
Axalon Bloodstone wrote: > > On Thu, 21 Oct 1999 [EMAIL PROTECTED] wrote: > > > I picked up an 18G Western Digital drive today that hangs off the Ultra66 > > interface of my BP6 board. > > > > I've taken a rather circuitous route in putting this drive into service > > because it doesn't appear that the 6.1 CD uses a boot kernel that recognizes > > the interface. I ended up booting on my old drive, mounting the new one, > > and copying everything over. That part went fine. > > > > In order to boot from the drive, I needed to get LILO into the MBR. No > > problem, edit /etc/lilo.conf and /etc/fstab and write the new boot block, > > right? It looked that way. I ended up with just 'LI' on the screen. > > > > Booted with the install CD and got that fixed up (remind me sometime to post > > about how to use the install CD for rescueing boot problems!) > > > > I've now got a system that shows only the /dev/hde (the new drive) being > > mounted, yet file accesses are _really_ going to the old /dev/hda. Okay, > > boot with "linux root=/dev/hde3" and we're off. > > > > I edited /etc/lilo.conf and ensured that everything mentioned /dev/hde as > > well as ensuring that /etc/fstab was correcty. Reran LILO and rebooted the > > system. > > > > All I get is 01's rolling through the screen. I'm now just using "linux > > root=/dev/hde3" to boot my machine and use the new drive. It'll work until > > I can get this sorted out... > > > > I'm sure it's something incredibly stupid, but what have I missed? > > I haven't installed onto hde yet, but thanks to someone on cooker list i > remebered howto get hde recognised without the ide patchs. > use 'ide2=0xd800 ide3=0xec00' when you boot from cd, and insert them when > lilo asks for appends. > There is also a trick for makeing it think it's hda but it escapes me ATM Yup, there's an UltraDMA howto out there in web-world that had that trick in it. It works extremely well. The problem is that after installation, I just get 'LI' on the screen. :( -- Steve Philp Network Administrator Advance Packaging Corporation [EMAIL PROTECTED]
Re: [expert] Booting from HPT366 drive...
[EMAIL PROTECTED] wrote: > > I recently ran into trouble getting a large drive to work. I was not using > UDMA/66; nevertheless, it ended up being a BIOS upgrade that was needed. Seeing > that is is UDMA/66 you are using, it would not surprise me if the support for it is > in its young stages. Check the BIOS and eliminate it as a cause. Thanks for the pointer Tim. I've picked up the latest BIOS to give that a try. Now it's just a matter of figuring out how I'm going to get that installed... I got no DOS here... :) > Steve Philp wrote: > > > Civileme wrote: > > > > > > [EMAIL PROTECTED] wrote: > > > > > > > I picked up an 18G Western Digital drive today that hangs off the Ultra66 > > > > interface of my BP6 board. > > > > > > > > I've taken a rather circuitous route in putting this drive into service > > > > because it doesn't appear that the 6.1 CD uses a boot kernel that recognizes > > > > the interface. I ended up booting on my old drive, mounting the new one, > > > > and copying everything over. That part went fine. > > > > > > > > In order to boot from the drive, I needed to get LILO into the MBR. No > > > > problem, edit /etc/lilo.conf and /etc/fstab and write the new boot block, > > > > right? It looked that way. I ended up with just 'LI' on the screen. > > > > > > > > Booted with the install CD and got that fixed up (remind me sometime to post > > > > about how to use the install CD for rescueing boot problems!) > > > > > > > > I've now got a system that shows only the /dev/hde (the new drive) being > > > > mounted, yet file accesses are _really_ going to the old /dev/hda. Okay, > > > > boot with "linux root=/dev/hde3" and we're off. > > > > > > > > I edited /etc/lilo.conf and ensured that everything mentioned /dev/hde as > > > > well as ensuring that /etc/fstab was correcty. Reran LILO and rebooted the > > > > system. > > > > > > > > All I get is 01's rolling through the screen. I'm now just using "linux > > > > root=/dev/hde3" to boot my machine and use the new drive. It'll work until > > > > I can get this sorted out... > > > > > > > > I'm sure it's something incredibly stupid, but what have I missed? > > > > > > > > -- > > > > Steve Philp > > > > Network Administrator > > > > Advance Packaging Corporation > > > > [EMAIL PROTECTED] > > > > > > I've seen 01s before, on disks that were scored by air freight handlers (just > > > got one in today on a Digital Celebris 6200. the speaker was bounding around > > > inside, as well as a few other small parts. > > > > > > The other suggestion I have heard is when your system and your BIOS think the > > > disk is configured in different ways, like Normal vs LBA or perhaps Large. > > > > The thing is, I don't see a way to adjust the mapping of the UDMA/66 > > drives like I'd have for a normal drive. > > > > I finally just took out the old drive and attempted an install onto the > > new drive. There's some LILO stuff you can pass to get it to recognize > > the extra controller. But, after installation, I get just the 'LI' when > > trying to boot. > > > > So, I've now moved the UDMA/66 drive onto the normal cable and the > > install there went just fine. Booting works also, so I'll wait a bit > > before I screw it up again. :) > > > > -- > > Steve Philp > > Network Administrator > > Advance Packaging Corporation > > [EMAIL PROTECTED] -- Steve Philp Network Administrator Advance Packaging Corporation [EMAIL PROTECTED]
Re: [expert] Booting from HPT366 drive...
I recently ran into trouble getting a large drive to work. I was not using UDMA/66; nevertheless, it ended up being a BIOS upgrade that was needed. Seeing that is is UDMA/66 you are using, it would not surprise me if the support for it is in its young stages. Check the BIOS and eliminate it as a cause. Tim Steve Philp wrote: > Civileme wrote: > > > > [EMAIL PROTECTED] wrote: > > > > > I picked up an 18G Western Digital drive today that hangs off the Ultra66 > > > interface of my BP6 board. > > > > > > I've taken a rather circuitous route in putting this drive into service > > > because it doesn't appear that the 6.1 CD uses a boot kernel that recognizes > > > the interface. I ended up booting on my old drive, mounting the new one, > > > and copying everything over. That part went fine. > > > > > > In order to boot from the drive, I needed to get LILO into the MBR. No > > > problem, edit /etc/lilo.conf and /etc/fstab and write the new boot block, > > > right? It looked that way. I ended up with just 'LI' on the screen. > > > > > > Booted with the install CD and got that fixed up (remind me sometime to post > > > about how to use the install CD for rescueing boot problems!) > > > > > > I've now got a system that shows only the /dev/hde (the new drive) being > > > mounted, yet file accesses are _really_ going to the old /dev/hda. Okay, > > > boot with "linux root=/dev/hde3" and we're off. > > > > > > I edited /etc/lilo.conf and ensured that everything mentioned /dev/hde as > > > well as ensuring that /etc/fstab was correcty. Reran LILO and rebooted the > > > system. > > > > > > All I get is 01's rolling through the screen. I'm now just using "linux > > > root=/dev/hde3" to boot my machine and use the new drive. It'll work until > > > I can get this sorted out... > > > > > > I'm sure it's something incredibly stupid, but what have I missed? > > > > > > -- > > > Steve Philp > > > Network Administrator > > > Advance Packaging Corporation > > > [EMAIL PROTECTED] > > > > I've seen 01s before, on disks that were scored by air freight handlers (just > > got one in today on a Digital Celebris 6200. the speaker was bounding around > > inside, as well as a few other small parts. > > > > The other suggestion I have heard is when your system and your BIOS think the > > disk is configured in different ways, like Normal vs LBA or perhaps Large. > > The thing is, I don't see a way to adjust the mapping of the UDMA/66 > drives like I'd have for a normal drive. > > I finally just took out the old drive and attempted an install onto the > new drive. There's some LILO stuff you can pass to get it to recognize > the extra controller. But, after installation, I get just the 'LI' when > trying to boot. > > So, I've now moved the UDMA/66 drive onto the normal cable and the > install there went just fine. Booting works also, so I'll wait a bit > before I screw it up again. :) > > -- > Steve Philp > Network Administrator > Advance Packaging Corporation > [EMAIL PROTECTED]
Re: [expert] Booting from HPT366 drive...
On Fri, 22 Oct 1999, Axalon Bloodstone wrote: > On Fri, 22 Oct 1999, Steve Philp wrote: > > [big snip] > > > So, I've now moved the UDMA/66 drive onto the normal cable and the > > install there went just fine. Booting works also, so I'll wait a bit > > before I screw it up again. :) > > I'll have info in .. installer says 9mins > Will let ya know Ok i was successfull. Just tryed to isolate if it was bios boot sequence and it has zero effect. What was your ide layout, i've already moved cdrom to 2nd slave, was there still hd's on the dma33 chains?
Re: [expert] Booting from HPT366 drive...
On Fri, 22 Oct 1999, Steve Philp wrote: [big snip] > So, I've now moved the UDMA/66 drive onto the normal cable and the > install there went just fine. Booting works also, so I'll wait a bit > before I screw it up again. :) I'll have info in .. installer says 9mins Will let ya know -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
Re: [expert] Booting from HPT366 drive...
Civileme wrote: > > [EMAIL PROTECTED] wrote: > > > I picked up an 18G Western Digital drive today that hangs off the Ultra66 > > interface of my BP6 board. > > > > I've taken a rather circuitous route in putting this drive into service > > because it doesn't appear that the 6.1 CD uses a boot kernel that recognizes > > the interface. I ended up booting on my old drive, mounting the new one, > > and copying everything over. That part went fine. > > > > In order to boot from the drive, I needed to get LILO into the MBR. No > > problem, edit /etc/lilo.conf and /etc/fstab and write the new boot block, > > right? It looked that way. I ended up with just 'LI' on the screen. > > > > Booted with the install CD and got that fixed up (remind me sometime to post > > about how to use the install CD for rescueing boot problems!) > > > > I've now got a system that shows only the /dev/hde (the new drive) being > > mounted, yet file accesses are _really_ going to the old /dev/hda. Okay, > > boot with "linux root=/dev/hde3" and we're off. > > > > I edited /etc/lilo.conf and ensured that everything mentioned /dev/hde as > > well as ensuring that /etc/fstab was correcty. Reran LILO and rebooted the > > system. > > > > All I get is 01's rolling through the screen. I'm now just using "linux > > root=/dev/hde3" to boot my machine and use the new drive. It'll work until > > I can get this sorted out... > > > > I'm sure it's something incredibly stupid, but what have I missed? > > > > -- > > Steve Philp > > Network Administrator > > Advance Packaging Corporation > > [EMAIL PROTECTED] > > I've seen 01s before, on disks that were scored by air freight handlers (just > got one in today on a Digital Celebris 6200. the speaker was bounding around > inside, as well as a few other small parts. > > The other suggestion I have heard is when your system and your BIOS think the > disk is configured in different ways, like Normal vs LBA or perhaps Large. The thing is, I don't see a way to adjust the mapping of the UDMA/66 drives like I'd have for a normal drive. I finally just took out the old drive and attempted an install onto the new drive. There's some LILO stuff you can pass to get it to recognize the extra controller. But, after installation, I get just the 'LI' when trying to boot. So, I've now moved the UDMA/66 drive onto the normal cable and the install there went just fine. Booting works also, so I'll wait a bit before I screw it up again. :) -- Steve Philp Network Administrator Advance Packaging Corporation [EMAIL PROTECTED]
Re: [expert] Booting from HPT366 drive...
Oh yeah, you'll get things like - hdc: IRQ probe failed (0) hdd: IRQ probe failed (0) hdd: IRQ probe failed (0) hdg: probing with STATUS(0x00) instead of ALTSTATUS(0xff) hdg: probing with STATUS(0xa1) instead of ALTSTATUS(0xff) hdg: no response (status = 0xa1), resetting drive - It's not quite as bad as it looks :) -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
Re: [expert] Booting from HPT366 drive...
On Thu, 21 Oct 1999 [EMAIL PROTECTED] wrote: > I picked up an 18G Western Digital drive today that hangs off the Ultra66 > interface of my BP6 board. > > I've taken a rather circuitous route in putting this drive into service > because it doesn't appear that the 6.1 CD uses a boot kernel that recognizes > the interface. I ended up booting on my old drive, mounting the new one, > and copying everything over. That part went fine. > > In order to boot from the drive, I needed to get LILO into the MBR. No > problem, edit /etc/lilo.conf and /etc/fstab and write the new boot block, > right? It looked that way. I ended up with just 'LI' on the screen. > > Booted with the install CD and got that fixed up (remind me sometime to post > about how to use the install CD for rescueing boot problems!) > > I've now got a system that shows only the /dev/hde (the new drive) being > mounted, yet file accesses are _really_ going to the old /dev/hda. Okay, > boot with "linux root=/dev/hde3" and we're off. > > I edited /etc/lilo.conf and ensured that everything mentioned /dev/hde as > well as ensuring that /etc/fstab was correcty. Reran LILO and rebooted the > system. > > All I get is 01's rolling through the screen. I'm now just using "linux > root=/dev/hde3" to boot my machine and use the new drive. It'll work until > I can get this sorted out... > > I'm sure it's something incredibly stupid, but what have I missed? I haven't installed onto hde yet, but thanks to someone on cooker list i remebered howto get hde recognised without the ide patchs. use 'ide2=0xd800 ide3=0xec00' when you boot from cd, and insert them when lilo asks for appends. There is also a trick for makeing it think it's hda but it escapes me ATM -- MandrakeSoft http://www.mandrakesoft.com/ --Axalon
Re: [expert] Booting from HPT366 drive...
[EMAIL PROTECTED] wrote: > I picked up an 18G Western Digital drive today that hangs off the Ultra66 > interface of my BP6 board. > > I've taken a rather circuitous route in putting this drive into service > because it doesn't appear that the 6.1 CD uses a boot kernel that recognizes > the interface. I ended up booting on my old drive, mounting the new one, > and copying everything over. That part went fine. > > In order to boot from the drive, I needed to get LILO into the MBR. No > problem, edit /etc/lilo.conf and /etc/fstab and write the new boot block, > right? It looked that way. I ended up with just 'LI' on the screen. > > Booted with the install CD and got that fixed up (remind me sometime to post > about how to use the install CD for rescueing boot problems!) > > I've now got a system that shows only the /dev/hde (the new drive) being > mounted, yet file accesses are _really_ going to the old /dev/hda. Okay, > boot with "linux root=/dev/hde3" and we're off. > > I edited /etc/lilo.conf and ensured that everything mentioned /dev/hde as > well as ensuring that /etc/fstab was correcty. Reran LILO and rebooted the > system. > > All I get is 01's rolling through the screen. I'm now just using "linux > root=/dev/hde3" to boot my machine and use the new drive. It'll work until > I can get this sorted out... > > I'm sure it's something incredibly stupid, but what have I missed? > > -- > Steve Philp > Network Administrator > Advance Packaging Corporation > [EMAIL PROTECTED] I've seen 01s before, on disks that were scored by air freight handlers (just got one in today on a Digital Celebris 6200. the speaker was bounding around inside, as well as a few other small parts. The other suggestion I have heard is when your system and your BIOS think the disk is configured in different ways, like Normal vs LBA or perhaps Large. Could /dev/hda and /dev/hde have different logical arrangements? If so, where does the MBR booting you come from? I have been working with someone who had root=/dev/hdc1 running in 6.0, in his lilo.conf In 6.1, he had to hand edit lilo.conf to get root=/dev/hdc1 into it. Once there, it seemed to have no effect. Civileme
[expert] Booting from HPT366 drive...
I picked up an 18G Western Digital drive today that hangs off the Ultra66 interface of my BP6 board. I've taken a rather circuitous route in putting this drive into service because it doesn't appear that the 6.1 CD uses a boot kernel that recognizes the interface. I ended up booting on my old drive, mounting the new one, and copying everything over. That part went fine. In order to boot from the drive, I needed to get LILO into the MBR. No problem, edit /etc/lilo.conf and /etc/fstab and write the new boot block, right? It looked that way. I ended up with just 'LI' on the screen. Booted with the install CD and got that fixed up (remind me sometime to post about how to use the install CD for rescueing boot problems!) I've now got a system that shows only the /dev/hde (the new drive) being mounted, yet file accesses are _really_ going to the old /dev/hda. Okay, boot with "linux root=/dev/hde3" and we're off. I edited /etc/lilo.conf and ensured that everything mentioned /dev/hde as well as ensuring that /etc/fstab was correcty. Reran LILO and rebooted the system. All I get is 01's rolling through the screen. I'm now just using "linux root=/dev/hde3" to boot my machine and use the new drive. It'll work until I can get this sorted out... I'm sure it's something incredibly stupid, but what have I missed? -- Steve Philp Network Administrator Advance Packaging Corporation [EMAIL PROTECTED]
