Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Jan 1997 02:27:12 +0200 (EET)
From:      Andrew Stesin <stesin@gu.net>
To:        current@freebsd.org
Subject:   Who Caught My PS/2 mouse?! + unknown PCI bridge + DD mode
Message-ID:  <Pine.BSF.3.95.970110015228.226A-100000@trifork.gu.net>

next in thread | raw e-mail | index | archive | help

Hello people,

what goes on here: a "Packard Bell" machine, GENERIC 2.2-BETA kernel
after pretty successfull ftp install done on Jan 3.

On PCI. This PB machine has a vertical card where expansion
slots are mounted, expansion cards are laying on the side,
just like in early Intel 486 boxes;
trifork.gu.net has one with 2 PCI slots and a square chip
(PCI bridge?) on it.  While booting, PB's BIOS reports:

	PB450MH PCI release 1.0A

No wonder, this strange chip isn't known to FreeBSD,
so probably someone will be interested in adding
it's vendor recognized as "Packard Bell"?

Here what FreeBSD kernel says after boot -v (I'm skipping
uninformative entries from disabled devices):

FreeBSD 2.2-BETA_A #0: Tue Dec 24 03:41:49  1996
    jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC
Calibrating clock(s) relative to mc146818A clock ... i8254 clock: 1193313 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
CPU: AMD Am5x86 Write-Back (486-class CPU)
  Origin = "AuthenticAMD"  Id = 0x4f4
real memory  = 25165824 (24576K bytes)
avail memory = 22237184 (21716K bytes)
pcibus_setup(1):	mode 1 addr port (0x0cf8) is 0x8000f000
pcibus_setup(1a):	mode1res=0x80000000 (0x80000000)
pcibus_check:	device 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 is there (id=c8221045)
Probing for devices on PCI bus 0:
	configuration mode 1 allows 32 devices.
chip0 <generic PCI bridge (vendor=1045 device=c822 subclass=0)> rev 1 on pci0:16
ncr0 <ncr 53c810a scsi> rev 17 int a irq 9 on pci0:18
	mapreg[10] type=1 addr=0000fc00 size=0100.
	mapreg[14] type=0 addr=fefffc00 size=0100.
	reg20: virtual=0xf4bc5c00 physical=0xfefffc00 size=0x100
ncr0: restart (scsi reset).
ncr0 scanning for targets 0..6 (V2 pl24 96/12/14)
ncr0 waiting for scsi devices to settle
(ncr0:0:0): "HP C3325A 5293" type 0 fixed SCSI 2
sd0(ncr0:0:0): Direct-Access 
sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 8)
2069MB (4238836 512 byte sectors)
sd0(ncr0:0:0): with 3703 cyls, 9 heads, and an average 127 sectors/track
pci0: uses 256 bytes of memory from fefffc00 upto fefffcff.
pci0: uses 256 bytes of I/O space from fc00 upto fcff.
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
psm0: current command byte:0047
psm0: status after reset 00 02 64
psm: status 00 00 64 (get_mouse_buttons)
psm0: status 00 02 64
psm0 at 0x60-0x64 irq 12 on motherboard
psm0: device ID 0, 2 buttons?
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: NEC 72065B
fd0: 1.44MB 3.5in
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <QUANTUM TRB850A>
wd0: 810MB (1660176 sectors), 1647 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 on isa
wdc1: unit 0 (atapi): <CD-ROM CDU55E/1.0u>, removable, accel, dma, iordy
1 3C5x9 board(s) on ISA found at 0x300
ep0 at 0x300-0x30f irq 10 on isa
ep0: aui/utp/bnc[*BNC*] address 00:20:af:cd:01:0d
npx0 on motherboard
npx0: INT 16 interface
imasks: bio c000c240, tty c0031492, net c0031492
BIOS Geometries:
 0:03351f3f 0..821=822 cylinders, 0..31=32 heads, 1..63=63 sectors
 0 accounted for
Device configuration finished.
Considering FFS root f/s.
configure() finished.
wd0s1: type 0xa5, start 0, end = 1660175, size 1660176 
wd0s1: C/H/S end 103/86/63 (570023) != end 1660175: invalid
sd0s1: type 0xa5, start 0, end = 4238835, size 4238836 
sd0s1: C/H/S end 263/218/7 (404711) != end 4238835: invalid

Please note the following:

-- both drives have some unexpected geometry choosed by DD mode;
   It All Works but complains a bit. Be it so, but strange anyway.

-- ps/2 mouse is recognized Ok by the kernel (???)
   Though I can't get moused working. Here is a duplicate
   of messages seen while rebooting, done from a root' vty:

# moused -cdf -p /dev/psm0 -t ps/2
moused: rodent is ps/2
moused: read returned -1 : Resource temporarily unavailable exiting

   or:

# cat < /dev/psm0
cat: stdin: Resource temporarily unavailable

   Makes me wonder -- Who Caught My Mouse? :-)

No X11 yet because of no mouse, of course... what a pity.

--



Best regards,
Andrew Stesin

nic-hdl: ST73-RIPE





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.970110015228.226A-100000>