1. The kernel compiled from GENERIC doesn't find my PS2 mouse.
2. 'options XSERVER' renders the kernel incapable of booting. The
config file is included below.
3. Adding 'device pcm0' also makes the kernel unable to boot. The
bootloader loads, tries to load the kernel and freezes up.
machine i386
cpu I686_CPU
ident FORSYTHE
maxusers 128
#makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols
options INET #InterNETworking
options FFS #Berkeley Fast Filesystem
options FFS_ROOT #FFS usable as root device [keep this!]
options NFS #Network Filesystem
options MSDOSFS #MSDOS Filesystem
options CD9660 #ISO 9660 Filesystem
options PROCFS #Process filesystem
options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=1000 #Delay (in ms) before probing SCSI
options UCONSOLE #Allow users to grab the console
options USERCONFIG #boot -c editor
options VISUAL_USERCONFIG #visual boot -c editor
options KTRACE #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options P1003_1B #Posix P1003_1B real-time extentions
options _KPOSIX_PRIORITY_SCHEDULING
options ICMP_BANDLIM #Rate limit bad replies
options DDB
device isa
device pci
device fdc0 at isa? port IO_FD1 irq 6 drq 2
device fd0 at fdc0 drive 0
device fd1 at fdc0 drive 1
device ata0 at isa? port IO_WD1 irq 14
device ata1 at isa? port IO_WD2 irq 15
device ata
device atadisk # ATA disk drives
device atapicd # ATAPI CDROM drives
device atapifd # ATAPI floppy drives
options ATA_STATIC_ID #Static device numbering
#options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices
device ahc # AHA2940 and onboard AIC7xxx devices
device scbus # SCSI bus (required)
device da # Direct Access (disks)
device pass # Passthrough device (direct SCSI access)
device atkbdc0 at isa? port IO_KBD
device atkbd0 at atkbdc? irq 1
device psm0 at atkbdc? irq 12
device vga0 at isa?
pseudo-device splash
options XSERVER # support for X server **Adding this causes a
crash**
device npx0 at nexus? port IO_NPX irq 13
device sio0 at isa? port IO_COM1 flags 0x10 irq 4
device ppc0 at isa? irq 7
device ppbus # Parallel port bus (required)
device lpt # Printer
device miibus # MII bus support
device dc # DEC/Intel 21143 and various workalikes
pseudo-device loop # Network loopback
pseudo-device ether # Ethernet support
pseudo-device tun # Packet tunnel.
pseudo-device pty # Pseudo-ttys (telnet etc)
pseudo-device bpf #Berkeley packet filter
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) [000214 12:22]:
> In <[EMAIL PROTECTED]> Kazutaka YOKOTA
><[EMAIL PROTECTED]> wrote:
> >>>>>>> Possible Problem 3
> >>During setup, I configure my Intellimouse as an "Intellimouse" on port
> >>"ps/2". The mouse cursor works as it should but during boot I get the
> >>following diagnostic:
> >>
> >>rc.i386 configuring syscons: blank_time mousedmoused: mouse type mismatch
> >>(ps/2 != intellimouse), ps/2 is assumed
> >
> > If you read the notice in the mouse configuration screen, you should
> > have understood that you should ALWAYS choose the type "Auto" for ANY
> > mouse connected to the PS/2 mouse port, regardless of the brand and
> > model of the mouse. The type "IntelliMouse" is for the SERIAL
> > IntelliMouse.
>
> On my Fujitsu Lifebook 535Tx I also set 'moused_type="glidepoint"'
> along with the 'moused_port="/dev/psm0"' in /etc/rc.conf and receive the
> abovementioned message on every reboot, BUT with such settings I can
> 'tap' and receive button event where as without setting moused_type to
> glidepoint this 'tapping' not works.
>
> N.Dudorov
>
>
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
>
--
Hasan Diwan [[EMAIL PROTECTED]] :)
Rensselaer Polytechnic Institute
Computer Science Department
PGP signature
