Re: Trouble with 5.0-RELEASE boot floppies

[Daniel Herring]

Hi all, thanks for your input.
For now, I have upgraded the machine to 4.7, but I am still interested in
getting 5.0 installed...

> > Machine: 150MHz Pentium, 16MB ram, 1.5Gig HD
>
> Well that's not much memory.  5.0 needs much more minimum memory than 4.x
(oops... the machine is only a P133... :)

Where are the system requirements for 5.0 listed? (I didn't find
memory/HD/processor specs in the early-adopter's guide or other places...)

Since PC133 is so cheap, I'm loathe to scrap around for/buy old SIMM's...

> what does a dmesg from 4.3 look like?

(already upgraded to 4.7)
* dmesg start *
Copyright (c) 1992-2002 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 4.7-RELEASE #1: Mon Feb 24 17:44:20 CST 2003
[EMAIL PROTECTED]:/usr/src/sys/compile/CUSTOM
Timecounter "i8254"  frequency 1193182 Hz
CPU: Pentium/P54C (132.96-MHz 586-class CPU)
  Origin = "GenuineIntel"  Id = 0x52c  Stepping = 12
  Features=0x1bf
real memory  = 16777216 (16384K bytes)
config> di pcic0
No such device: pcic0
Invalid command or syntax.  Type `?' for help.
config> di sn0
config> di lnc0
config> di ie0
config> di fe0
No such device: fe0
Invalid command or syntax.  Type `?' for help.
config> di ed0
No such device: ed0
Invalid command or syntax.  Type `?' for help.
config> di cs0
config> di bt0
No such device: bt0
Invalid command or syntax.  Type `?' for help.
config> di aic0
No such device: aic0
Invalid command or syntax.  Type `?' for help.
config> di aha0
No such device: aha0
Invalid command or syntax.  Type `?' for help.
config> di adv0
No such device: adv0
Invalid command or syntax.  Type `?' for help.
config> q
avail memory = 13819904 (13496K bytes)
Preloaded elf kernel "kernel" at 0xc02b3000.
Preloaded userconfig_script "/boot/kernel.conf" at 0xc02b309c.
Intel Pentium detected, installing workaround for F00F bug
md0: Malloc disk
npx0:  on motherboard
npx0: INT 16 interface
pcib0:  on motherboard
pci0:  on pcib0
isab0:  at device 7.0 on pci0
isa0:  on isab0
pci0:  at 8.0 irq 11
wb0:  port 0xf880-0xf8ff mem
0xfffbf800-0xfffbf87f irq 10 at device 17.0 on pci0
wb0: Ethernet address: 00:10:61:b0:58:ae
miibus0:  on wb0
amphy0:  on miibus0
amphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc0:  port 0xfc00-0xfcff mem
0xfffbfc00-0xfffb irq 10 at device 19.0 on pci0
dc0: Ethernet address: 00:04:5a:43:1e:5b
miibus1:  on dc0
ukphy0:  on miibus1
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
orm0:  at iomem 0xc-0xc7fff,0xed000-0xedfff on isa0
fdc0:  at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0
ata1 at port 0x170-0x177,0x376 irq 15 on isa0
atkbdc0:  at port 0x60,0x64 on isa0
atkbd0:  flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0:  irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0:  at port 0x3c0-0x3df iomem 0xa-0xb on isa0
sc0:  at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
sio4:  at port 0x2f8-0x2ff irq 3 on isa0
sio4: type 16550A
IP packet filtering initialized, divert enabled, rule-based forwarding
enabled, default to deny, unlimited logging
ata1-slave: ATAPI identify retries exceeded
ad0: 1549MB  [3148/16/63] at ata0-master BIOSPIO
acd0: CDROM  at ata1-master BIOSPIO
Mounting root from ufs:/dev/ad0s1a
*  dmesg end  *

As I mentioned before, the boot floppies start to launch sysinstall, and
then everything locks up.
Is there anything I could to to work around this (short of upgrading the
system)?

Thanks,
Daniel Herring
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: Trouble with 5.0-RELEASE boot floppies

[Kevin Stevens]

On Sun, 23 Feb 2003, taxman wrote:

> On Sunday 23 February 2003 08:07 pm, Daniel Herring wrote:
> > Here's the situation:
> > Machine: 150MHz Pentium, 16MB ram, 1.5Gig HD
>
> Well that's not much memory.  5.0 needs much more minimum memory than 4.x
> Your best bet is to put more memory in and see how that goes first.
> next, try to get -current boot floppies and see if the same error is there.
> 5.0 is stil not production material, so re-read the early adopters guide and
> be prepared to go to work if you really want 5.0 on this machine.  You may be
> better off upgrading to 4.7rel or 4.8 when it comes out.

FWIW, I've just been fooling with 5.0 on a similar machine; 150P, 32MB
ram, 2.0GB.  My dmesg looks similar to yours, and the machine boots and
runs fine.  I don't have a way to reduce memory to 16MB or I'd check for
you.

KeS

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message

Re: Trouble with 5.0-RELEASE boot floppies

[taxman]

On Sunday 23 February 2003 08:07 pm, Daniel Herring wrote:
> Here's the situation:
> Machine: 150MHz Pentium, 16MB ram, 1.5Gig HD

Well that's not much memory.  5.0 needs much more minimum memory than 4.x
Your best bet is to put more memory in and see how that goes first.
next, try to get -current boot floppies and see if the same error is there.
5.0 is stil not production material, so re-read the early adopters guide and 
be prepared to go to work if you really want 5.0 on this machine.  You may be 
better off upgrading to 4.7rel or 4.8 when it comes out.

> Current OS: FreeBSD 4.3-RELEASE

what does a dmesg from 4.3 look like?

> Desired OS: FreeBSD 5.0-RELEASE
>
> I downloaded and copied "kern.flp" and "mfsroot.flp" onto two
> freshly-formatted floppies (no errors).
> Boot the machine.  It loads both floppies, starts the kernel, prepares for
> sysinstall, and freezes.
> After this, the machine doesn't respond to any keyboard events (Excape,
> Num-lock, 3-fingered-salute, ...).
>
> Here's the last screen before it dies:
> | sc0: VGA <16 virtual consoles, flags=0x300>
> | sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
> | sio0: type 16550A
> | sio1: configured irq 3 not in bitmap of probed irqs 0
> | sio1: port may not be enabled
> | vga0:  at port 0x2f8-0x307 irq 3 on isa 0
> | sio4:  at port 0x2f8-0x307 irq 3 in isa0
> | sio4: type 16550A
> | unknown:  can't assign resources (port)

Are you sure you disabled pnp? 

> | unknown:  can't assign resources (irq)
> | 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)
> | Time counters tick every 10.000 msec
> | ata1_slave: timeout waiting for interrupt
> | ata1_slave: ATAPI identify failed
> | ad0: 1549MB  [3148/16/63] at ata0-master BIOSPIO
> | acd0: CDROM  at ata1-master BIOSPIO
> | Mounting root from ufs:/dev/md0
> | /stand/sysinstall running as init on vty0
>
> Does anyone have any idea what is wrong or how I can avoid this?
> I successfully installed version 4-3 from boot floppies a couple years
> ago...
> Version 4.3 still boots fine...
> This happens even if I disconnect the HD...
> I've enabled and disabled most of the BIOS settings (ports, PNP OS, ...)
>
> Also, these boot floppies successfully load on my other computer.

well what hardware differences are there?

I don't know what's wrong, but some more info may be helpful to others.

Tim

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message