Re: Recent bootloaders not working also on FIC PA-2005 board

2008-04-10 Thread John Baldwin
On Wednesday 09 April 2008 04:32:48 pm Marcin Cieslak wrote:
 
  It would be these changes.  Debugging this will be hard. :(  Are you 
familiar 
  with x86 assembly at all?
  
 
 I have a bit different problem: The box (old Pentium-MMX PC with the FIC
 PA-2005 board using VT82C580 (Apollo VP) chipset. The machine had 16MB
 RAM only, recently upgraded to 256MB.
 
 I have installed the newest BIOS version available, so the CD-ROM
 booting works properly. I can boot Solaris 8 for Intel CD and NetBSD 4.0
 install CD, but FreeBSD CDROMs from 5.5-RELEASE, 7.0-RELEASE and March
 2007 8.0-CURRENT bootloaders fail in the same way:
 
 - A /boot/loader menu appears. The cursor runs like around 10 seconds
 countdown, like 10 was printed and then 3 backspaces and 10 printed
 again, no countdown takes place.
 
 - Pressing some keys like Enter, Space and 3 - nothing happens, but if
 you persist long enough (with 3 or Enter) you can make the counter
 running down.
 
 - After the counter expires, the |/-\|/- progress meter (how do we call
 this thing?) appears for a while and then the system resets.
 
 How can I try to debug this? I have tried to attach serial console
   with AT keyboard unplugged I still get message that VGA console will
 be used. The serial port is working correctly (verified with Windows and
 later with NetBSD).

CD-ROM booting uses a separate bootstrap (src/sys/boot/i386/cdboot/cdboot.s).  
It does depend on a non-ancient BIOS.  NT 4.0 uses the same CD booting method 
that newer FreeBSD snaps use FWIW.  To debug this you would need to hack on 
cdboot.s to find out when and where it dies.

-- 
John Baldwin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Recent bootloaders not working also on FIC PA-2005 board

2008-04-09 Thread Marcin Cieslak


It would be these changes.  Debugging this will be hard. :(  Are you familiar 
with x86 assembly at all?




I have a bit different problem: The box (old Pentium-MMX PC with the FIC
PA-2005 board using VT82C580 (Apollo VP) chipset. The machine had 16MB
RAM only, recently upgraded to 256MB.

I have installed the newest BIOS version available, so the CD-ROM
booting works properly. I can boot Solaris 8 for Intel CD and NetBSD 4.0
install CD, but FreeBSD CDROMs from 5.5-RELEASE, 7.0-RELEASE and March
2007 8.0-CURRENT bootloaders fail in the same way:

- A /boot/loader menu appears. The cursor runs like around 10 seconds
countdown, like 10 was printed and then 3 backspaces and 10 printed
again, no countdown takes place.

- Pressing some keys like Enter, Space and 3 - nothing happens, but if
you persist long enough (with 3 or Enter) you can make the counter
running down.

- After the counter expires, the |/-\|/- progress meter (how do we call
this thing?) appears for a while and then the system resets.

How can I try to debug this? I have tried to attach serial console
 with AT keyboard unplugged I still get message that VGA console will
be used. The serial port is working correctly (verified with Windows and
later with NetBSD).

Can I get serial console while booting from CDROM - do I need to remove
VGA card for this?

Soon I should receive a firewire controller, but I am not sure if any
low-level debugging can be done with this.

Below please find dmesg output from NetBSD (upgraded to -CURRENT).

--Marcin

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
2006, 2007, 2008
The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
The Regents of the University of California.  All rights reserved.

NetBSD 4.99.58 (PONIATOWSKI) #1: Tue Apr  8 01:27:38 CEST 2008
[EMAIL 
PROTECTED]:/usr/netbsd/obj/usr/netbsd/src/sys/arch/i386/compile/PONIATOWSKI
total memory = 254 MB
avail memory = 239 MB
timecounter: Timecounters tick every 10.000 msec
timecounter: Timecounter i8254 frequency 1193182 Hz quality 100
Generic PC
PCI BIOS rev. 2.1 found at 0xfb3f0
pcibios: config mechanism [1][x], special cycles [1][x], last bus 0
PCI BIOS has 5 Interrupt Routing table entries
--
  device vendor product pin PIRQ IRQ stage
--
--
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel Pentium/MMX (586-class), 166.11 MHz, id 0x543
cpu0: features 8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8
cpu0: features 8001bfMMX
cpu0: Initial APIC ID 0
cpu0: Cluster/Package ID 0
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0
pchb0: VIA Technologies VT82C580 (Apollo VP) Host-PCI Bridge (rev. 0x10)
pcib0 at pci0 dev 7 function 0
pcib0: VIA Technologies VT82C586 PCI-ISA Bridge (rev. 0x02)
viaide0 at pci0 dev 7 function 1
viaide0: VIA Technologies VT82C586 (Apollo VP) ATA33 controller
viaide0: bus-master DMA support present
viaide0: primary channel configured to compatibility mode
viaide0: primary channel interrupting at irq 14
atabus0 at viaide0 channel 0
viaide0: secondary channel configured to compatibility mode
viaide0: secondary channel interrupting at irq 15
atabus1 at viaide0 channel 1
vga1 at pci0 dev 11 function 0: ATI Technologies 3D Rage II+ (rev. 0x9a)
wsdisplay0 at vga1 kbdmux 1: console (80x25, vt100 emulation)
wsmux1: connecting to wsdisplay0
direct rendering for vga1 unsupported
isa0 at pcib0
lpt0 at isa0 port 0x378-0x37b irq 7
com0 at isa0 port 0x3f8-0x3ff irq 4: ns16550a, working fifo
com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo
pckbc0 at isa0 port 0x60-0x64
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
attimer0 at isa0 port 0x40-0x43: AT Timer
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker (CPU-intensive output)
sysbeep0 at pcppi0
isapnp0 at isa0 port 0x279: ISA Plug 'n Play device support
npx0 at isa0 port 0xf0-0xff
npx0:  reported by CPUID; using exception 16
fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2
attimer0: attached to pcppi0
isapnp0: read port 0x203
sb1 at isapnp0 port 0x220/16,0x388/4,0x500/16 irq 5 drq 1,0
sb1: Analog Devices AD1816A : dsp v3.02
sb1: WARNING: powerhook_establish is deprecated
audio0 at sb1: half duplex, mmap, independent
opl0 at sb1: model OPL3
midi1 at opl0: SB Yamaha OPL3 (CPU-intensive output)
mpu0 at isapnp0 port 0x300/2 irq 9
mpu0: Analog Devices AD1816A
midi2 at mpu0: Roland MPU-401 MIDI UART (CPU-intensive output)
joy0 at isapnp0 port 0x200/8
joy0: Analog Devices AD1816A
joy0: joystick not connected
timecounter: Timecounter clockinterrupt frequency 100 Hz quality 0
fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec
wd0 at atabus0 drive 0: SAMSUNG WN316025A (1.6 GB)
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 

Re: Recent bootloaders not working also on FIC PA-2005 board

2008-04-09 Thread Greg Byshenk
On Wed, Apr 09, 2008 at 10:32:48PM +0200, Marcin Cieslak wrote:

 It would be these changes.  Debugging this will be hard. :(  Are you 
 familiar with x86 assembly at all?

In relation to John Baldwin's question, I (at least) have basically zero
knowledge of x86 assembler.  :-(
 

But this bit caught my eye:

 How can I try to debug this? I have tried to attach serial console
 with AT keyboard unplugged I still get message that VGA console will
 be used. The serial port is working correctly (verified with Windows and
 later with NetBSD).

 Can I get serial console while booting from CDROM - do I need to remove
 VGA card for this?

When my error occurs (with the Asus TR-DLS), I get the message about
using internal console (vga?), even when the machine is set to 
use a serial console.  I don't know if this is relevant, but in my
case I can't use serial.


I can also add that -- though I am not much of a progammer -- I will
happily test anything that anyone might suggest.  My machine is not
in production (I built it to do some testing with FreeBSD7 and ZFS),
and I can break it without any real consequences.


-- 
greg byshenk  -  [EMAIL PROTECTED]  -  Leiden, NL
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]