Re: /etc/rc.conf, take 46!
On Sun, 21 Mar 1999 18:06:41 PST, Jordan K. Hubbard wrote:
if [ -f /etc/defaults/rc.conf ]; then
. /etc/defaults/rc.conf
-elif [ -f /etc/rc.conf ]; then
- . /etc/rc.conf
+ for i in ${rc_conf_files}; do
+ if [ -f $i ]; then
+ . $i
+ fi
+ done
fi
Hi Jordan,
What's the idea behind ignoring rc_conf_files just because we can't find
/etc/defaults/rc.conf?
Ciao,
Sheldon.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: /etc/rc.conf, take 46!
On Tue, 23 Mar 1999 12:49:52 +0200, Sheldon Hearn wrote: What's the idea behind ignoring rc_conf_files just because we can't find /etc/defaults/rc.conf? Please pretend I never said that. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /etc/rc.conf, take 46!
On Tue, Mar 23, 1999 at 12:49:52PM +0200, a little birdie told me
that Sheldon Hearn remarked
On Sun, 21 Mar 1999 18:06:41 PST, Jordan K. Hubbard wrote:
if [ -f /etc/defaults/rc.conf ]; then
. /etc/defaults/rc.conf
-elif [ -f /etc/rc.conf ]; then
- . /etc/rc.conf
+ for i in ${rc_conf_files}; do
+ if [ -f $i ]; then
+ . $i
+ fi
+ done
fi
Hi Jordan,
What's the idea behind ignoring rc_conf_files just because we can't find
/etc/defaults/rc.conf?
I have to jump in here and say 'Because that's where it's DEFINED'.
Sorry, I had to stick my nose in somewhere ;)
---
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
| Matthew Fuller http://www.over-yonder.net/ |
* fulle...@futuresouth.com fulle...@over-yonder.net *
| UNIX Systems Administrator Specializing in FreeBSD |
* FutureSouth Communications ISPHelp ISP Consulting *
| The only reason I'm burning my candle at both ends, |
*is because I haven't figured out how to light the*
| middle yet |
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Spontaneous reboots
For about the past week I've been getting spontaneous reboots on my machine. As far as I can tell, there's no obvious common connection - most recently my box was under load at the time, but the time before that all I did was move the mouse (shades of Windows :-) and nothing else much was running. This does only seem to happen when I'm using the machine - after a few hours, a reboot is pretty much guaranteed (sounds like a resource leak of some kind to me). Beyond that, I don't know. My kernel and machine config haven't changed recently. Has anyone else been seeing this? What kind of information would help to narrow the problem down? Kris - The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Spontaneous reboots
Kris Kennaway wrote: For about the past week I've been getting spontaneous reboots on my machine. As far as I can tell, there's no obvious common connection - most recently my box was under load at the time, but the time before that all I did was move the mouse (shades of Windows :-) and nothing else much was running. This does only seem to happen when I'm using the machine - after a few hours, a reboot is pretty much guaranteed (sounds like a resource leak of some kind to me). Beyond that, I don't know. My kernel and machine config haven't changed recently. Has anyone else been seeing this? What kind of information would help to narrow the problem down? The sort of thing we're looking for is, Which version of FreeBSD (I'd assume something -current because you posted to the -current mailing list, but how current?), what hardware (i.e. CPU type [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? Also, you say when I moved the mouse - does that mean your machine lives in X-Windows all the time? - Does it crash when it's not running X etc? What type of video card does your machine have? The more detail you can provide (without going too OTT :-) - The more likely someone will be able to help :-) I have two boxes here tracking 4.0-current, and so far (looking for a nice piece of wood to touch), I've not seen any reboots on either for quite a long time (i.emonths) :) -Karl To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Spontaneous reboots
Sounds like a NMI generated by memory parity errors or motherboard malfunction. Good Luck, Jerry Hicks wghi...@bellsouth.net From: Kris Kennaway kkenn...@physics.adelaide.edu.au Subject: Spontaneous reboots Date: Tue, 23 Mar 1999 23:32:28 +0930 (CST) For about the past week I've been getting spontaneous reboots on my machine. As far as I can tell, there's no obvious common connection - most recently my box was under load at the time, but the time before that all I did was move the mouse (shades of Windows :-) and nothing else much was running. This does only seem to happen when I'm using the machine - after a few hours, a reboot is pretty much guaranteed (sounds like a resource leak of some kind to me). Beyond that, I don't know. My kernel and machine config haven't changed recently. Has anyone else been seeing this? What kind of information would help to narrow the problem down? Kris - The Feynman problem-solving algorithm: 1. Write down the problem 2. Think real hard 3. Write down the solution To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ELF Question
Gus R Bourg wrote: I have a machine running a snap from back on 19981126. Is there still a problem moving from aout to elf. I remember a while back I had to on another machine do something weird to get the bootloader working. Read /usr/src/UPDATING -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.org Someone's trying to hack into our server. Wow... How flattering! I know. There must be some mistake. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
usb keyboard?
ls -ald /dev/kb* crw--- 1 root wheel 112, 0 Mar 23 23:29 /dev/kbd0 crw--- 1 root wheel 112, 1 Mar 23 23:29 /dev/kbd1 muadib# kbdcontrol -k /dev/kbd1 kbd1 ukbd0, type:generic (3) kbdcontrol: unable to set keyboard: Inappropriate ioctl for device Any clues as to how to switch from standard keyboard device to the usb keyboard? Tnks, Amancio To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Help needed with hangs associated with vfs locking
According to Greg Lehey: perform this kind of locking). I currently suspect that vinum acts as a catalyst by issuing disk multiple I/O requests in a very short space of time. I got two hanging processes too yesterday. rnews was unbatching news and I had a grep on my news log. syslogd was locked in inode as was grep. I had to reboot. I don't have more data sorry, I don't have a serial console yet. pidprocaddr uid ppid pgrp flag wchan stat comm wchan 65139 f3f6bd00 f3f6c0000 0 556 004006 3 ld inode f0bb3e00 My current is unfortunately a bit old (see below). -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #70: Sat Feb 27 09:43:08 CET 1999 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: usb keyboard?
Cool, I managed to get my usb board up and running. the problem was kbdcontrol or me 8) I try to switch keyboards at - usb however I needed an at keboard to make the switch so I attached an at keyboard to my system and issue the silly command: kbdcontrol -k /dev/kbd1 The last time I tried to set the usb keyboard as the default the system crash hard perhaps this time around it will work. Enjoy, Amancio To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: /etc/rc.conf, take 46!
I like it too... No code anywhere than needed. After all, if /etc/rc
doesn't exist, everything's messed up anyway, so you mideswell make it more
dependent upon that script.
-Original Message-
From: Chas cpinck...@dynasty.net
To: p...@originative.co.uk p...@originative.co.uk
Cc: r...@dataplex.net r...@dataplex.net; curr...@freebsd.org
curr...@freebsd.org
Date: Monday, March 22, 1999 5:12 PM
Subject: Re: /etc/rc.conf, take 46!
Now that sounz like a simple solution.:)) Paul...
An alternate, and perhaps cleaner approach would be to always suck in
/etc/defaults/rc.conf and /etc/rc.conf. Then suck in those
files specified
in ${additional_rc_conf_files}.
I still think we're chasing our tails with all this configuration stuff.
Why can't /etc/rc load /etc/defaults/rc.conf followed by /etc/rc.conf (if
present). Don't have anything in /etc/defaults.rc.conf except default
variable settings.
The local admin can do what the hell they want in /etc/rc.conf, including
putting in a bit of script to load /etc/rc.conf.local
/etc/rc.conf.flavour_of_month etc.
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: usb keyboard?
Did you add options KBD_INSTALL_CDEV in your kernel config? Nick On Tue, 23 Mar 1999, Amancio Hasty wrote: ls -ald /dev/kb* crw--- 1 root wheel 112, 0 Mar 23 23:29 /dev/kbd0 crw--- 1 root wheel 112, 1 Mar 23 23:29 /dev/kbd1 muadib# kbdcontrol -k /dev/kbd1 kbd1 ukbd0, type:generic (3) kbdcontrol: unable to set keyboard: Inappropriate ioctl for device Any clues as to how to switch from standard keyboard device to the usb keyboard? Tnks, Amancio To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- e-Mail: hi...@skylink.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: usb keyboard?
Yes, I have KBD_INSTALL_CDEV in my kernel config file. Actually, my problem was that the default keyboard is the AT keyboard what I need is to have my default keyboard be the USB keyboard. Tnks, Amancio To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Spontaneous reboots
On Tue, 23 Mar 1999, Karl Pielorz wrote: Kris Kennaway wrote: For about the past week I've been getting spontaneous reboots on my machine. As far as I can tell, there's no obvious common connection - most recently my box was under load at the time, but the time before that all I did was move the mouse (shades of Windows :-) and nothing else much was running. This does only seem to happen when I'm using the machine - after a few hours, a reboot is pretty much guaranteed (sounds like a resource leak of some kind to me). Beyond that, I don't know. My kernel and machine config haven't changed recently. Has anyone else been seeing this? What kind of information would help to narrow the problem down? The sort of thing we're looking for is, Which version of FreeBSD (I'd assume something -current because you posted to the -current mailing list, but how current?), what hardware (i.e. CPU type [Intel/AMD/Cyrix]) etc. - how much memory, what types of hard drive (SCSI vs. IDE) etc. - if you have any 'weird' hardware in there? Also, you say when I moved the mouse - does that mean your machine lives in X-Windows all the time? - Does it crash when it's not running X etc? What type of video card does your machine have? The more detail you can provide (without going too OTT :-) - The more likely someone will be able to help :-) I have two boxes here tracking 4.0-current, and so far (looking for a nice piece of wood to touch), I've not seen any reboots on either for quite a long time (i.emonths) :) -Karl To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message He should proviide a full dmesg from bootverbose mode. One thing I've seen is that K6-2's in write allocated mode have big problems. Brian Feldman_ __ ___ ___ ___ gr...@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ _ |___/___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Help needed with hangs associated with vfs locking
On Tuesday, 23 March 1999 at 8:00:10 +0100, Ollivier Robert wrote: According to Greg Lehey: perform this kind of locking). I currently suspect that vinum acts as a catalyst by issuing disk multiple I/O requests in a very short space of time. I got two hanging processes too yesterday. rnews was unbatching news and I had a grep on my news log. syslogd was locked in inode as was grep. I had to reboot. I don't have more data sorry, I don't have a serial console yet. If you can get a dump and let me look at it, it would help. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: usb keyboard?
ls -ald /dev/kb* crw--- 1 root wheel 112, 0 Mar 23 23:29 /dev/kbd0 crw--- 1 root wheel 112, 1 Mar 23 23:29 /dev/kbd1 muadib# kbdcontrol -k /dev/kbd1 kbd1 ukbd0, type:generic (3) kbdcontrol: unable to set keyboard: Inappropriate ioctl for device Any clues as to how to switch from standard keyboard device to the usb keyboard? You need to issue the kbdcontrol command from an vty. If you are running it from a serial or network terminal, redirect stdin as follows: kbdcontrol -k /dev/kbd1 /dev/ttyv0 Any vty should work. Make also sure that options KBD_INSTALL_CDEV is in your kernel configuration file. Kazu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: usb keyboard?
Cool, I managed to get my usb board up and running. the problem was kbdcontrol or me 8) I try to switch keyboards at - usb however I needed an at keboard to make the switch so I attached an at keyboard to my system and issue the silly command: kbdcontrol -k /dev/kbd1 The last time I tried to set the usb keyboard as the default the system crash hard perhaps this time around it will work. Enjoy, Amancio Would send me the output from `dmesg' and describe the crash in more details? Do you have crash dump? Kazu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
sound on es1371 based sound Cards?
Has anyone gotten a sound card based on the Ensoniq es1371 chipset to work under FreeBSD, if so what Entries did you have to put in the kernel config file? The card I have is the Creative Ensoniq Audio PCI, on IO E400-E43F and at IRQ 10.Any help on this woudl be apreciated. Thanks Seamus -- Seamus Wassman http://www.sparhawk.bc.ca sparh...@sparhawk.bc.ca To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: usb keyboard?
Yes, I have KBD_INSTALL_CDEV in my kernel config file. Actually, my problem was that the default keyboard is the AT keyboard what I need is to have my default keyboard be the USB keyboard. You want to use the USB keyboard as the only keyboard in the system, and want to get rid of the AT keyboard, right? Please try the following steps. I have not tested this configuration myself yet, but I expect it should work. 0. You said you have already done this, but I will write it for a record anyway... Make sure /dev/kbd* is present. If not go to /dev and ./MAKEDEV kbd0 kbd1 Also make sure options KBD_INSTALL_CDEV is included in your kernel configuration file. 1. Remove `atkbd0' from your kernel configuration file so that the AT keyboard won't be recognized. (Leave `atkbdc0' in, as it is used by the PS/2 mouse driver `psm'.) Then, you tell `syscons' to use the USB keyboard; this is necessary because the USB drivers have not been attached when syscons is being initialized, and syscons will not find the USB keyboard. Therefore, it will start without a keyboard and you have to explicitly tell syscons which keyboard to use. This can be done in one of the two ways. 2a. Explicitly run the following command as a part of start-up script (say, /etc/rc.i386). kbdcontrol -k /dev/kbd0 /dev/ttyv0 /dev/null Note that /dev/kbd0 is the USB keyboard as the AT keyboard will not be probed and attached. 2b. Specify a flag to `syscons' so that it will look for a keyboard. device sc0 at isa? tty flags 0x100 With this flag specified, `syscons' will periodically look for any available keyboard until it finds one. Kazu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: usb keyboard?
Cool ! kbdcontrol -k /dev/kbd1 /dev/ttyv0 Appears to work 8) Now I have to figure out how to add support for my mouse. Got no clue what protocol does it use . All I know is that is Macally USB mouse is going to be fun hunting for the mouse protocol 8) Enclosed is the output of dmesg: Enjoy, Amancio Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #5: Wed Mar 24 19:42:30 PST 1999 r...@muadib.star-gate.com:/usr/src/sys/compile/CIOLOCO Timecounter i8254 frequency 1193182 Hz Timecounter TSC frequency 451025177 Hz CPU: Pentium III (451.03-MHz 686-class CPU) Origin = GenuineIntel Id = 0x672 Stepping=2 Features=0x387f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,P AT,PSE36,b18,MMX,FXSR,b25 real memory = 134217728 (131072K bytes) avail memory = 127070208 (124092K bytes) Preloaded elf kernel kernel at 0xc0347000. Preloaded splash_image_data /boot/matrix.bmp at 0xc034709c. Preloaded elf module vesa.ko at 0xc03470ec. Preloaded elf module splash_bmp.ko at 0xc0347188. VESA: v0.20, 2560k memory, flags:0x731e, mode table:0xc0d78022 (50c000) VESA: NVidia module_register_init: module_register(splash_bmp, c03435dc, 0) error 19 Probing for devices on PCI bus 0: chip0: Intel 82443BX host to PCI bridge rev 0x03 on pci0.0.0 chip1: Intel 82443BX host to AGP bridge rev 0x03 on pci0.1.0 chip2: Intel 82371AB PCI to ISA bridge rev 0x02 on pci0.7.0 ide_pci0: Intel PIIX4 Bus-master IDE controller rev 0x01 on pci0.7.1 uhci0: Intel 82371AB/EB (PIIX4) USB Host Controller rev 0x01 int d irq 10 on pci0.7.2 usb0: USB version 1.0, interrupting at 10 intpm0: Intel 82371AB Power management controller rev 0x02 on pci0.7.3 intpm0: I/O mapped 5000 ALLOCED IRQ 0 intr IRQ 9 enabled revision 0 intsmb0: Intel PIIX4 SMBUS Interface smbus0: System Management Bus on intsmb0 smb0: SMBus general purpose I/O on smbus0 intpm0: PM I/O mapped 4000 bktr0: BrookTree 848 rev 0x11 int a irq 11 on pci0.15.0 bti2c0: bt848 Hard/Soft I2C controller iicbb0: I2C generic bit-banging driver on bti2c0 iicbus0: Philips I2C bus on iicbb0 master-only iicsmb0: I2C to SMB bridge on iicbus0 smbus1: System Management Bus on iicsmb0 smb1: SMBus general purpose I/O on smbus1 iic0: I2C general purpose I/O on iicbus0 smbus2: System Management Bus on bti2c0 smb2: SMBus general purpose I/O on smbus2 Hauppauge WinCast/TV, Philips NTSC tuner, dbx stereo. pn0: 82c168/82c169 PNIC 10/100BaseTX rev 0x20 int a irq 11 on pci0.20.0 pn0: Ethernet address: 00:a0:cc:40:f0:5f pn0: autoneg complete, link status good (half-duplex, 10Mbps) Probing for devices on PCI bus 1: vga0: VGA-compatible display device rev 0x04 int a irq 11 on pci1.0.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color 16 virtual consoles, flags=0x0 ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0 at atkbd0 psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa wdc0: unit 0 (wd0): Maxtor 90845D4, DMA, 32-bit, multi-block-16 wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): ATAPI 40X CDROM DRIVE/VER-3.4A, removable, accel, dma, iordis wdc0: ATAPI CD-ROMs not configured wdc1 not found at 0x170 ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode plip0: PLIP network interface on ppbus 0 ppi0: generic parallel i/o on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa npx0 on motherboard npx0: INT 16 interface usbd_match usb0: Intel 82371AB/EB (PIIX4) USB Host Controller usbd_attach usbd_new_device bus=0xc0d7c000 depth=0 lowspeed=0 usbd_new_device: adding unit addr=1, rev=100, class=9, subclass=0, protocol=0, maxpacket=64, ls=0 usbd_new_device: new dev (addr 1), dev=0xc0d87e00, parent=0xc0d82c40 uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 usbd_set_config_index: (addr 1) attr=0x40, selfpowered=1, power=0, powerquirk=0 usbd_set_config_index: set config 1 usbd_set_config_index: setting new config 1 uhub0: 2 ports with 2 removable, self powered usbd_init_port: adding hub port=1 status=0x0301 change=0x0001 usbd_init_port: adding hub port=2 status=0x0301 change=0x0001 uhub_explore: status change hub=1 port=1 usbd_new_device bus=0xc0d7c000 depth=1 lowspeed=512 usbd_new_device: adding unit addr=2, rev=100, class=0, subclass=0, protocol=0, maxpacket=8, ls=1 usbd_new_device: new dev (addr 2), dev=0xc0d87b00, parent=0xc0d75be0 usbd_probe_and_attach: no device specific driver found usbd_set_config_index: (addr 2) attr=0x80, selfpowered=0, power=100, powerquirk=0 usbd_set_config_index: set config 1 usbd_set_config_index: setting new config 1 ums0 ums0: vendor 0x0618
Re: usb keyboard?
Cool ! kbdcontrol -k /dev/kbd1 /dev/ttyv0 Appears to work 8) Now I have to figure out how to add support for my mouse. Got no clue what protocol does it use . All I know is that is Macally USB mouse is going to be fun hunting for the mouse protocol 8) No, you don't need to find out protocol :-) Run moused to see how it recognizes the USB mouse: moused -i all -p /dev/ums0 It will print some info. Then start the mouse daemon as: moused -p /dev/ums0 kbdcontrol -m on The mouse pointer is now available in the text console. In order to use the USB mouse in the X session, you tell the X server that the mouse is at /dev/sysmouse and its protocol type is Auto Device /dev/sysmouse Protocol Auto If you decide not to use the mouse daemon and let the X sever directly read from the USB mouse, you still tell the X server the mouse protocol type is Auto. Device /dev/ums0 Protocol Auto (If you are using XFree86 3.3.1 or earlier, the protocol type is MouseSystems.) Kazu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: usb keyboard?
Okay, I owe you lots of kudos !! Did as you instructed: moused -p /dev/ums0 In my XF86Config file: Device /dev/sysmouse Protocol Auto One thing though: kbdcontrol appears not to have option : -m on So in summary I have my usb keyboard and usb mouse up and running and it works with X 8) Tnks! Amancio Cool ! kbdcontrol -k /dev/kbd1 /dev/ttyv0 Appears to work 8) Now I have to figure out how to add support for my mouse. Got no clue what protocol does it use . All I know is that is Macally USB mouse is going to be fun hunting for the mouse protocol 8) No, you don't need to find out protocol :-) Run moused to see how it recognizes the USB mouse: moused -i all -p /dev/ums0 It will print some info. Then start the mouse daemon as: moused -p /dev/ums0 kbdcontrol -m on The mouse pointer is now available in the text console. In order to use the USB mouse in the X session, you tell the X server that the mouse is at /dev/sysmouse and its protocol type is Auto Device /dev/sysmouse Protocol Auto If you decide not to use the mouse daemon and let the X sever directly read from the USB mouse, you still tell the X server the mouse protocol type is Auto. Device /dev/ums0 Protocol Auto (If you are using XFree86 3.3.1 or earlier, the protocol type is MouseSystems.) Kazu To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Problems with ELF Emacs
I'm running -current from a couple of weeks ago. I recently re-compiled XFree86 to ELF - which works, and re-compiled emacs-19.34b - which won't work with X11, though it does work inside an Xterm. My old aout emacs still works (with old aout libraries - the re-compiled aout libraries seem to be missing a symbol). When running as an X11 client, emacs opens the window and then nothing happens. Looking at a ktrace, it seems to be continuously sending GetInputFocus commands to the X-server, which are being correctly replied to (as far as I can tell). I haven't bumped into this problem with any other X clients. Has anyone else seen this, or have any ideas? Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: usb keyboard?
On Tue, 23 Mar 1999, Amancio Hasty wrote: One thing though: kbdcontrol appears not to have option : -m on Should be vidcontrol -m on I think. - alex To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: usb keyboard?
On Tue, 23 Mar 1999, Amancio Hasty wrote: One thing though: kbdcontrol appears not to have option : -m on Should be vidcontrol -m on I think. - alex Yes, it is . Kazutaka YOKOTA just mailed me the correction. I suggest someone should summarize and stick the USB setup information either on a web page or a README file. Best Regards, Amancio To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: usb keyboard? (fwd)
Thanks for doing that :-) Send me the webpage and I'll stick on the back of www.etla.net/~n_hibma/usb/usb.pl If you want of course. Nick Yes, it is . Kazutaka YOKOTA just mailed me the correction. I suggest someone should summarize and stick the USB setup information either on a web page or a README file. Best Regards, Amancio To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- e-Mail: hi...@skylink.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
