Re: DP2 (I think!) crash booting from floppies
Hi, On Fri, Nov 22, 2002 at 02:30:34PM -, local.freebsd.current wrote: > All goes well until I get "Extracting base into / directory" then > "Write failure on transfer. Wrote -1 bytes of 240640" and at the > bottom of the screen "/mnt: write failed, filesystem is full". I had exactly the same problems with 4.x recently; and it turned out that the problem was caused by a bad floppy. dd hat written all the data without reporting errors, but when I tried to boot from the floppy... b00m. Try to read the floppy back on the system where you created it, i.e. dd if=/dev/fd0 of=verify.dat and then compare the md5 checksums of the original .flp file and this file. If they do not match or if dd aborts with an error message, you know where your problems are coming from. /s/Udo -- "The only reasonable alternative we can come up with is to close off the Internet to America Online users until they have passed an entrance test. But that would break federal laws that prohibit discrimination against the intellectually challenged." - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 (I think!) crash booting from floppies
On Fri, 22 Nov 2002 14:31:04 -, [EMAIL PROTECTED]
("local.freebsd.current") wrote:
>Alt-F2 shows:
>pid 85 (cpio) uid 0, inumber 5278 on /mnt: filesystem full
>/stand/cpio: write error: No space left on device
>/stand/gunzip: failed fwrite
>
>I think I saw something about that in a recent posting so I
>guess the fix hasn't made it into the floppies yet.
But of course the fact that I had only given / 50Mb might
have had something to do with it :-)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: DP2 (I think!) crash booting from floppies
On Wed, 20 Nov 2002 17:11:42 -, [EMAIL PROTECTED] (Robert Watson) wrote: >This is not actually DP2, it's about a week earlier. That said, I'm not >sure that bug was fixed in the missing week. If you can, try booting off >of the 5.0-DP2 ISOs found at: > > ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-i386/5.0-DP2 > >Or using the floppies: > > ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/5.0-DP2/floppies OK thanks for the correction. Using these floppies I can get much further. I get this during the boot: unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: can't assign resources (port) unknown: can't assign resources (port) Then I get into sysinstall OK, partition the disk, set up the network via DHCP and choose to install via passive FTP from ftp.freebsd.org. All goes well until I get "Extracting base into / directory" then "Write failure on transfer. Wrote -1 bytes of 240640" and at the bottom of the screen "/mnt: write failed, filesystem is full". Alt-F2 shows: pid 85 (cpio) uid 0, inumber 5278 on /mnt: filesystem full /stand/cpio: write error: No space left on device /stand/gunzip: failed fwrite I think I saw something about that in a recent posting so I guess the fix hasn't made it into the floppies yet. jim To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 (I think!) crash booting from floppies
On Thu, 21 Nov 2002, Mitsuru IWASAKI wrote: > Nate Lawson wrote: > > Can someone get the memory detection (int 12) back to stable? The > > conservative approach seems to only have the limitation of "losing" 640k > > whereas the experimental approach causes panics. > > > > Can we take such critical experiments out of the base system and let them > > mature as a patch? I heard something about a release coming up or > > something like that. > > I already got the memory detection (int 12) back to STABLE and CURRENT. > After all, nothing had changed there except for having new loader tunable. > > If you find 'Fatal trap 12: page fault while in vm86 mode' message at > early kernel boot stage, your BIOS probably has broken INT 12H (in my > case, it was not implemented by BIOS writer). > The loader tunable 'hw.hasbrokenint12' is workaround for it. > Try this at loader prompt: > ok set hw.hasbrokenint12="1" Ah, thank you very much. I didn't know this had been reverted. The tunable should be documented in the errata section as I'm sure other users would appreciate that. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 (I think!) crash booting from floppies
Hi, > On Wed, 20 Nov 2002, Terry Lambert wrote: > > "local.freebsd.current" wrote: > > > I got a pair of floppies from: > > > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies/ > > > > > > and booted them on a Dell Dimension XPS D300 which is currently > > > running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an > > > STB Riva graphics card. > > > > > > When booting the kernel off the second floppy I get: > > > > > > Booting [/kernel]... > > > / > > > > > > Fatal trap 12: page fault while in vm86 mode > > > fault virtual address = 0x9f800 > > > instruction pointer= 0xf000:0x8c3e > > > > Patch which was never integrated. Build a new kernel. > > > > >http://docs.freebsd.org/cgi/getmsg.cgi?fetch=341812+0+archive/2002/freebsd-current/20021027.freebsd-current > > Can someone get the memory detection (int 12) back to stable? The > conservative approach seems to only have the limitation of "losing" 640k > whereas the experimental approach causes panics. > > Can we take such critical experiments out of the base system and let them > mature as a patch? I heard something about a release coming up or > something like that. I already got the memory detection (int 12) back to STABLE and CURRENT. After all, nothing had changed there except for having new loader tunable. If you find 'Fatal trap 12: page fault while in vm86 mode' message at early kernel boot stage, your BIOS probably has broken INT 12H (in my case, it was not implemented by BIOS writer). The loader tunable 'hw.hasbrokenint12' is workaround for it. Try this at loader prompt: ok set hw.hasbrokenint12="1" Thanks To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 (I think!) crash booting from floppies
On Wed, 20 Nov 2002, Terry Lambert wrote: > "local.freebsd.current" wrote: > > I got a pair of floppies from: > > > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies/ > > > > and booted them on a Dell Dimension XPS D300 which is currently > > running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an > > STB Riva graphics card. > > > > When booting the kernel off the second floppy I get: > > > > Booting [/kernel]... > > / > > > > Fatal trap 12: page fault while in vm86 mode > > fault virtual address = 0x9f800 > > instruction pointer= 0xf000:0x8c3e > > Patch which was never integrated. Build a new kernel. > > >http://docs.freebsd.org/cgi/getmsg.cgi?fetch=341812+0+archive/2002/freebsd-current/20021027.freebsd-current Can someone get the memory detection (int 12) back to stable? The conservative approach seems to only have the limitation of "losing" 640k whereas the experimental approach causes panics. Can we take such critical experiments out of the base system and let them mature as a patch? I heard something about a release coming up or something like that. -Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 (I think!) crash booting from floppies
On 20-Nov-2002 local.freebsd.current wrote:
> On Wed, 20 Nov 2002 11:32:29 -, [EMAIL PROTECTED]
> ("local.freebsd.current") wrote:
>
>>I got a pair of floppies from:
>>
>>ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies
> /
>>
>>and booted them on a Dell Dimension XPS D300 which is currently
>>running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an
>>STB Riva graphics card.
>
> I've now tried a third machine, one whose disk I can overwrite.
> This is a PII/400 (MSI 6119 board) with two IDE drives, an IDE
> CD, a Kingston (Realtek) NIC and ATI graphics.
>
> I can get as far as FDISK but when I hit A to use the entire
> disk, nothing happens. It doesn't respond to the keyboard at
> all. Numlock still toggles the light so *something* is there,
> but not a lot.
Can you use Alt-F2 to switch to the debug terminal and see if there
is any output? You probably want to switch before you do the fdisk,
then switch again afterwards to see if there is any new output. You
can get back to the main screen from the debug terminal by using
Alt-F1.
--
John Baldwin <[EMAIL PROTECTED]> <>< http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: DP2 (I think!) crash booting from floppies
This is not actually DP2, it's about a week earlier. That said, I'm not sure that bug was fixed in the missing week. If you can, try booting off of the 5.0-DP2 ISOs found at: ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-i386/5.0-DP2 Or using the floppies: ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/5.0-DP2/floppies Robert N M Watson FreeBSD Core Team, TrustedBSD Projects [EMAIL PROTECTED] Network Associates Laboratories On Wed, 20 Nov 2002, local.freebsd.current wrote: > I got a pair of floppies from: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies/ > > and booted them on a Dell Dimension XPS D300 which is currently > running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an > STB Riva graphics card. > > When booting the kernel off the second floppy I get: > > Booting [/kernel]... > / > > Fatal trap 12: page fault while in vm86 mode > fault virtual address = 0x9f800 > fault code = user read, page not present > instruction pointer= 0xf000:0x8c3e > stack pointer = 0x0:0xfcc > frame pointer = 0x0:0xfd4 > code segment = base 0x0, limit 0x0, type 0x0 >= DPL 0, pres 0, def32 0, gran 0 > processor eflags = interrupt enabled, resume, vm86, IOPL = 0 > current process= 0 () > trap number= 12 > panic: page fault > Uptime: 1s > > The same floppies work fine on another machine, up to the point > of launching sysinstall. > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 (I think!) crash booting from floppies
"local.freebsd.current" wrote: > I got a pair of floppies from: > > ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies/ > > and booted them on a Dell Dimension XPS D300 which is currently > running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an > STB Riva graphics card. > > When booting the kernel off the second floppy I get: > > Booting [/kernel]... > / > > Fatal trap 12: page fault while in vm86 mode > fault virtual address = 0x9f800 > instruction pointer= 0xf000:0x8c3e Patch which was never integrated. Build a new kernel. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=341812+0+archive/2002/freebsd-current/20021027.freebsd-current -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DP2 (I think!) crash booting from floppies
On Wed, 20 Nov 2002 11:32:29 -, [EMAIL PROTECTED]
("local.freebsd.current") wrote:
>I got a pair of floppies from:
>
>ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies
/
>
>and booted them on a Dell Dimension XPS D300 which is currently
>running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an
>STB Riva graphics card.
I've now tried a third machine, one whose disk I can overwrite.
This is a PII/400 (MSI 6119 board) with two IDE drives, an IDE
CD, a Kingston (Realtek) NIC and ATI graphics.
I can get as far as FDISK but when I hit A to use the entire
disk, nothing happens. It doesn't respond to the keyboard at
all. Numlock still toggles the light so *something* is there,
but not a lot.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
DP2 (I think!) crash booting from floppies
I got a pair of floppies from: ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/5.0-20021103-SNAP/floppies/ and booted them on a Dell Dimension XPS D300 which is currently running 4.7. It's a PII/300 with an Adaptec 2940 SCSI and an STB Riva graphics card. When booting the kernel off the second floppy I get: Booting [/kernel]... / Fatal trap 12: page fault while in vm86 mode fault virtual address = 0x9f800 fault code = user read, page not present instruction pointer= 0xf000:0x8c3e stack pointer = 0x0:0xfcc frame pointer = 0x0:0xfd4 code segment = base 0x0, limit 0x0, type 0x0 = DPL 0, pres 0, def32 0, gran 0 processor eflags = interrupt enabled, resume, vm86, IOPL = 0 current process= 0 () trap number= 12 panic: page fault Uptime: 1s The same floppies work fine on another machine, up to the point of launching sysinstall. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
