Re: ethercons: ethernet console driver for 5-current
Robert Watson wrote: I had a fair amount of time over the last week running in disconnected operation, and realized I had too many cables under my desk, so I spent a bit of time exploring the FreeBSD console code. Robert, I just tried this out (version 0.4) and I like it!! Thanks for the great work. Couple of things I noticed, (sorry if you are aware of them), When logged on via miniterm the 'w' command doesn't show the ethercons user. 'Who' does. The output from top is a bit jumbled. I would definitely like to see this functionality added to the base system, once it is ready. Cheers, Cameron PS I tried logging into the same machine twice and the two miniterm's mirror each other! Not sure if that is intended but it is fun :) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: boot -s change in -current?
On Fri, 2003-09-26 at 19:42, Scott Long wrote: > On Fri, 26 Sep 2003, Aaron Wohl wrote: > > > I just cvsuped -current/build/install. Now boot -s doesnt work, it > > ignores the -s. Do I need to do something to enable -s nowadays? Or how > > to get into standalone now? > > I have no idea what the cause is, but does the 'boot single user' option > of the loader work? > > Scott No it has the same result. Cam signature.asc Description: This is a digitally signed message part
Re: cannot boot -s
I have the same here from this morning's -current but I also see this on boot up: *snip* mounting root from ufs:/dev/ad0s2a pid 87 (fsck_ufs), uid 0: exited on signal 8 pid 88 (fsck_ufs), uid 0: exited on signal 8 The machine then displays the login prompt, but not the missing startup messages. Cam On Fri, 2003-09-26 at 17:16, Jonathan Fosburgh wrote: > On Friday 26 September 2003 10:32 am, Shin-ichi Yoshimoto wrote: > > Hi, After new kernel installing, I cannot boot -s. > > This kernel always runs multiuser mode. > > > > What's happen ?? > I have the same thing from this morning's sources. Also, shutdown -s just > brings me back up into single-user mode. Also, the output from startup and > shutdown scripts is no longer being echoed to the console. Now, the system > so far appears to be running fine and everything does seem to have started. > Still, seems a little strange ... signature.asc Description: This is a digitally signed message part
Re: Network problems
On Sun, 2003-09-21 at 00:16, Scott Likens wrote: > On Sat, 2003-09-20 at 16:04, Cameron Murdoch wrote: > > On Sat, 2003-09-20 at 23:50, Scott Likens wrote: > > > First, do you use DHCP? > > > > No, not on this laptop. > > > > > What are you doing exactly when it looses 'net or 'ip? > > > > Nothing specific that I can see. Sometimes nothing, sometimes an nfs > > installworld, which was a bit dangerous seeing as the connection would > > drop every few mins/secs. > > > > Have you tried to replace the network card with a different one to see > if you get the same results? > > either the same type of card, or a different type? > > It might be a weird bug in that card, or in the driver. It is an integrated card, so no :) As Warner said in another email, this card normally works flawlessly. I have many pci versions of it in other machines running current which do not have this problem, so it could be hardware, but it seems a little strange to me. Cheers, Cam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network problems
On Sat, 2003-09-20 at 23:50, Scott Likens wrote: *snip* > First, do you use DHCP? No, not on this laptop. > What are you doing exactly when it looses 'net or 'ip? Nothing specific that I can see. Sometimes nothing, sometimes an nfs installworld, which was a bit dangerous seeing as the connection would drop every few mins/secs. > Is there any messages on the console or viewable via 'dmesg'? None at all. Cheers, Cam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Network problems
On Sat, 2003-09-20 at 23:10, Cameron Murdoch wrote: > When the connection gets dropped doing an ifconfig down/up on the > interface does ? This was supposed to say that ifconfig down/up does not help, only removing/inserting the network cable. Also, sorry about the wrong email address in the privious email, I got a little trigger happy! Cam ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Network problems
I have a strange problem with my Dell Inspiron Laptop. The network card will stop responding to all network traffic. This happens very regulally, though without any obvious pattern. Sometimes it only appears as slight packet lose though normally the network connection goes completly. But then at other times the connection stays up for a resonable time. I have tried different cables, hubs, etc but to no avail. Link status doesn't seem to get dropped, only IP. When the connection gets dropped doing an ifconfig down/up on the interface does ? Unplugging and then inserting the network cable will restore the connection for at least a few seconds. I am running a recent current: FreeBSD opal.macaroon.net 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Fri Sep 19 21:59: 12 BST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/OPAL i386 The network card is an integrated intel card, (fxp0): fxp0: flags=8843 mtu 1500 options=3 inet 10.1.10.200 netmask 0xff00 broadcast 10.1.10.255 ether 00:20:e0:69:50:3c media: Ethernet autoselect (100baseTX ) status: active Unfortunatly I can't remember when it started happening. I have been tracking current weekly for the past few months. It certainly seems to be getting worse though. Any help would be much appriciated. Cameron ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
psmintr: out of sync
Hi, Not sure what happened to the original message, sorry for the noise! I am running a recent current: FreeBSD opal.macaroon.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Wed Mar 26 16:18:16 GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 The machine is a Dell Inspiron 4000 laptop. It is running XFree86-4.3.0 It has both a trackpad and a pointing stick (?what is the real name for this, I always call them nipples?), and it is seems to be the mouse I am having a problem. Every now and again, but with great regularity the screen will freeze up, so that nothing works, not even the caps lock light. However, it isn't a crash as leaving the machine alone for a random amount of time will normally fix it. Sometimes this delay is a matter of seconds, other times I have left if for about 20+mins. Interestingly enough, pinging the laptop from another computer will always unfreeze it immediately. As this occurs the following is printed to the console: Mar 27 11:23:57 opal kernel: psmintr: out of sync (00c0 != ). Mar 27 11:23:58 opal kernel: psmintr: discard a byte (1). The above appears for each freeze, and every now and again this appears: Mar 27 11:23:57 opal kernel: psmintr: out of sync (00c0 != ). Mar 27 11:23:58 opal kernel: psmintr: discard a byte (1). Mar 27 11:23:58 opal kernel: psmintr: out of sync (0040 != ). Mar 27 11:23:58 opal kernel: psmintr: discard a byte (2). Mar 27 11:23:58 opal kernel: psmintr: out of sync (00c0 != ). Mar 27 11:23:58 opal kernel: psmintr: re-enable the mouse. When the re-enable the mouse message happens then the pointing stick stops working and only the trackpad functions. This started happening with 5-RELEASE though not when -RELEASE was first installed. I am not sure what has caused it. Probably completely unrelated but the below appears on boot up, (GENERIC kernel - ie, WITNESS and INVARIANTS) pci0: at device 7.3 (no driver attached) pcm0: port 0xc800-0xc8ff mem 0xf9ffe000-0xf9ff irq 5 at device 8.0 on pci0 pcm0: malloc() of "64" with the following non-sleepablelocks held: exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322 malloc() of "16" with the following non-sleepablelocks held: exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322 malloc() of "16" with the following non-sleepablelocks held: exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322 malloc() of "16" with the following non-sleepablelocks held: exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322 malloc() of "64" with the following non-sleepablelocks held: exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322 malloc() of "16" with the following non-sleepablelocks held: exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322 malloc() of "16" with the following non-sleepablelocks held: exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322 malloc() of "16" with the following non-sleepablelocks held: exclusive sleep mutex pcm0:mixer (pcm mixer) r = 0 (0xc332c6c0) locked @ /usr/src/sys/dev/sound/pcm/mixer.c:322 pcib2: at device 16.0 on pci0 Thanks a lot! -- Cameron Murdoch <[EMAIL PROTECTED]> ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
psmintr: out of sync
___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
could sleep with pcm0:mixer
Hi all, Source upgraded my laptop to current a little while ago. Generally it has been quite solid though there are a couple of niggles, since upgrade and with a recent cvsup. Machine is a Dell Inspiron 4000 laptop: [cameron@opal]$ uname -a FreeBSD opal.macaroon.net 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Fri Nov 29 21:25:40 GMT 2002 root@:/usr/obj/usr/src/sys/GENERIC i386 Upon booting the following messages are displayed: pcm0: port 0xc800-0xc8ff mem 0xf9ffe000-0xf9ff irq 5 at device 8.0 on pci0 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 /usr/src/sys/vm/uma_core.c:1330: could sleep with "pcm0:mixer" locked from /usr/src/sys/dev/sound/pcm/mixer.c:330 These have been there since the upgrade and originally I wasn't sure what they were and just ignored them :) However, the computer has occasionally been locking up so that I can't even break into the debugger, (no serial console). I had also stupidly compiled out witness support though that is back in now as I am running with a generic kernel. I noticed that a couple of days ago the following went into the tree: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=496485+0+current/cvs-all I have cvsup'd since then and have verified that the above is in my local tree but the could sleep messages still appear. I am no coder but would be happy to help in whatever way I can if required. Alternativly if the messages are harmless then don't hesitate to tell me to shut up! Other point is I am seeing this pop up on the console quite a bit: Nov 30 00:29:21 opal kernel: psmintr: out of sync (00c0 != ). Nov 30 00:29:21 opal kernel: psmintr: discard a byte (14). Nov 30 00:29:21 opal kernel: psmintr: out of sync (00c0 != ). Nov 30 00:29:21 opal kernel: psmintr: discard a byte (15). Nov 30 00:29:27 opal kernel: psmintr: out of sync (0080 != ). Nov 30 00:29:27 opal kernel: psmintr: discard a byte (16). Nov 30 00:29:27 opal kernel: psmintr: out of sync (0080 != ). Nov 30 00:29:27 opal kernel: psmintr: discard a byte (17). Nov 30 00:29:27 opal kernel: psmintr: out of sync (0080 != ). Nov 30 00:29:27 opal kernel: psmintr: discard a byte (18). Not sure if it is related or not. Full dmesg is attached if it helps. Cameron Murdoch 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 5.0-CURRENT #0: Fri Nov 29 21:25:40 GMT 2002 root@:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc06d3000. Preloaded elf module "/boot/kernel/snd_maestro3.ko" at 0xc06d30a8. Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc06d315c. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc06d3208. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 851934223 Hz CPU: Pentium III/Pentium III Xeon/Celeron (851.93-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383f9ff real memory = 402501632 (383 MB) avail memory = 383660032 (365 MB) Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 9 entries at 0xc00fbd70 Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_cpu0: on acpi0 acpi_tz0: on acpi0 acpi_acad0: on acpi0 acpi_cmbat0: on acpi0 acpi_cmbat1: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xf000-0xf3ff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) cbb0: at device 3.0 on pci0 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcib0: slot 3 INTA is routed to irq 11 cbb1: at device 3.1 on pci0 cardbus1: on cbb1 pccard1: <16-bit PCCard bus> on cbb1
