xl driver
After my latest cvsup/make world, I have this happening at boot: Sep 3 13:24:26 manatee /kernel: xl0: 3Com 3c900-COMBO Etherlink XL port 0x6c00-0x6c3f irq 11 at device 9.0 on pci0 Sep 3 13:24:26 manatee /kernel: xl0: Ethernet address: 00:60:97:58:92:e5 Sep 3 13:24:26 manatee /kernel: xl0: selecting 10baseT transceiver, half duplex Sep 3 13:24:26 manatee /kernel: xl1: 3Com 3c900-COMBO Etherlink XL port 0x6c00-0x6c3f irq 11 at device 9.0 on pci2 Sep 3 13:24:26 manatee /kernel: xl1: couldn't map ports/memory Sep 3 13:24:26 manatee /kernel: device_probe_and_attach: xl1 attach returned 6 I only have one ethernet card, so I'm confused why it's trying to set up two. Joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
perl built twice?
While doing a make world, I noticed that perl is built early on. When I came back later, I saw perl being built again along with all the other gnu.usr.bin stuff. Was I tripping or did perl really get built twice? Joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
mouse madness under X
This is a problem I've had starting with the last couple of builds. If I switch from X to a virtual console, then back again, *sometimes* the mouse cursor will be stuck on the right hand side of the screen. I can move it up and down, but not side to side. The way to cure the problem is to go back to the console, wait a few seconds, then come back into X. The problem goes away. At first I thought this was a problem with my wm, but I tried a different one and got the same result. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
panic at shutdown
I just built a new world/kernel yesterday, and now I get a panic when I shut down. I ran gdb on the dump: .. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 2998272 initial pcb at 25b1c0 panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking panic messages: --- --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:303 303 dumppcb.pcb_cr3 = rcr3(); To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: panic at shutdown
And Bill Fumerola spoke:
On Mon, Jul 31, 2000 at 10:37:48PM -0700, R Joseph Wright wrote:
I just built a new world/kernel yesterday, and now I get a panic when I shut
down. I ran gdb on the dump:
..
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 2998272
initial pcb at 25b1c0
panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking
panic messages:
---
---
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
303 dumppcb.pcb_cr3 = rcr3();
type 'bt', this tells us just about as much as if you said
"it crashed".
though, by the panic message, this seems to be a known bug..
--
Bill Fumerola - Network Architect, BOFH / Chimes, Inc.
[EMAIL PROTECTED] / [EMAIL PROTECTED]
Sorry :)
GNU gdb 4.18
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-unknown-freebsd"...
IdlePTD 2998272
initial pcb at 25b1c0
panicstr: lockmgr: pid 1, not exclusive lock holder 0 unlocking
panic messages:
---
---
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
303 dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0 boot (howto=256) at ../../kern/kern_shutdown.c:303
#1 0xc014bd28 in poweroff_wait (junk=0xc02010a0, howto=1)
at ../../kern/kern_shutdown.c:553
#2 0xc0146af0 in lockmgr (lkp=0xc0c50a00, flags=6, interlkp=0xc87108ac,
p=0xc7d4be00) at ../../kern/kern_lock.c:382
#3 0xc01779ab in vop_stdunlock (ap=0xc7d51e48) at ../../kern/vfs_default.c:255
#4 0xc01b6ccd in ufs_vnoperate (ap=0xc7d51e48)
at ../../ufs/ufs/ufs_vnops.c:2301
#5 0xc01b1bab in ufs_inactive (ap=0xc7d51e78) at vnode_if.h:865
#6 0xc01b6ccd in ufs_vnoperate (ap=0xc7d51e78)
at ../../ufs/ufs/ufs_vnops.c:2301
#7 0xc017a726 in vput (vp=0xc8710840) at vnode_if.h:794
#8 0xc01aee87 in ffs_sync (mp=0xc0ade800, waitfor=2, cred=0xc0721700,
p=0xc026d5e0) at ../../ufs/ffs/ffs_vfsops.c:955
#9 0xc017c605 in sync (p=0xc026d5e0, uap=0x0) at ../../kern/vfs_syscalls.c:551
#10 0xc014b777 in boot (howto=0) at ../../kern/kern_shutdown.c:225
#11 0xc014b578 in reboot (p=0xc7d4be00, uap=0xc7d51f80)
at ../../kern/kern_shutdown.c:146
#12 0xc01ecd21 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47,
tf_edi = -1077936612, tf_esi = -1077936624, tf_ebp = -1077936836,
tf_isp = -942333996, tf_ebx = -1077936732, tf_edx = -1, tf_ecx = 4,
tf_eax = 55, tf_trapno = 7, tf_err = 2, tf_eip = 134536452, tf_cs = 31,
tf_eflags = 643, tf_esp = -1077937056, tf_ss = 47})
at ../../i386/i386/trap.c:1128
#13 0xc01e1ab5 in Xint0x80_syscall ()
#14 0x80486ee in ?? ()
#15 0x8048478 in ?? ()
#16 0x8048139 in ?? ()
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: roots shell == /bin/sh please
On Thu, Jun 29, 2000 at 12:39:46PM -0700, Doug Barton wrote: On Thu, 29 Jun 2000, gnu not unix wrote: Hi. My vote is for root's shell to be /bin/sh if anyone's counting. This will never happen. This position was made clear in th erecent tcsh debate. Speaking of csh and tcsh, I noticed that /bin/csh is hard linked to /bin/tcsh, yet when I invoke tcsh, I get a different prompt than when I invoke csh. I find this rather odd. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
odd error in bioscall.s
I have this problem while building a kernel from sources cvsup'ed
today:
cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual
-fformat-extensions -ansi -g -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL
-include opt_global.h -elf -mpreferred-stack-boundary=2 ../../i386/i386/bioscall.s
{standard input}: Assembler messages:
{standard input}:774: Error: operands given don't match any known 386 instruction
{standard input}:839: Error: operands given don't match any known 386 instruction
*** Error code 1
Stop in /usr/src/sys/compile/MANATEE.
The file bioscall.s has only 163 lines. Where is it getting 774 and
839?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Motif is now Open Source 8)
On Tue, 16 May 2000, Sheldon Hearn wrote: On Mon, 15 May 2000 23:08:23 -0400, Donn Miller wrote: Check it out at: http://www.opengroup.org/openmotif/ Yes, that is great news! I tried compiling it, but I had trouble with lib/Xm/Scale.c. It wanted to include langinfo.h, which FreeBSD doesn't have. I've integrated NetBSD's langinfo and nl_types support into FreeBSD. I can send you patches if you haven't managed to work around this yet? That's interesting. I compiled it without problems. Why would it look for langinfo.h on one machine and not another? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gcc -Os optimisation broken (RELENG_4)
In contrast, I've been using -Os -march=pentium during the last three months for buildworld and the kernel. Never had problems whatsoever. Perhaps this is a bit off topic, but can the pentium optimisations be used for AMD K6 processors? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
single user mode problem
This has been going on for awhile, and I've looked everywhere for a solution. When I boot single user, the / filesystem gets mounted on wd0s4a even though /dev does not even have such an entry nor does /etc/fstab, since these have all been updated. This is not really such a problem until I try to exit from single user mode. Then, it tries to remount / on ad0s4a and can't find it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
This has been going on for awhile, and I've looked everywhere for a
solution. When I boot single user, the / filesystem gets mounted on
wd0s4a even though /dev does not even have such an entry nor does
/etc/fstab, since these have all been updated.
This is not really such a problem until I try to exit from single user
mode. Then, it tries to remount / on ad0s4a and can't find it.
Dear Joseph,
as I have recently written, I met an analogous problem while upgrading
to CURRENT: the "wdNsMa syndrome" appeared when I rebooted in s.u.m.
with the shining gleaming roaring freshly-made 4.0-CURRENT kernel in
order to (somehow) make installworld. Well, I did NOT care about it
and I went ahead ruthlessly ...
By the way, I made another kernel at the end of the process ("by the
book"). I suppose (?) this cleared the problem. In fact, I was able to
boot with no weird messages: all my filesystems were correctly
identified as adNsM (e.g. ad1s2a, ad1s2e ...)
Hi Salvo,
I did read your recent post on this. For me, however, the problem
persists even with a new kernel. I've looked through all the boot and
init files for some clue as to where it's getting the idea that / is on
wd0s4a but I can't find anything ):-(.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
Regardless, this is typically syptomatic of either a very old /boot/loader, non-use of the loader eg. through a /boot.config file, or an error in the entry for / in /etc/fstab. Isn't /boot/loader updated upon making a new world? If so, it ought to be current. I don't know any way of finding out since it's a binary file. /etc/fstab: /dev/ad0s4b noneswapsw 0 0 /dev/ad0s4a / ufs rw 1 1 /dev/ad0s4e /usrufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 /dev/ad0s1 /dosmsdos ro,noauto 0 0 proc/proc procfs rw 0 0 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: single user mode problem
On Fri, 10 Mar 2000, Walter Brameld wrote: On Fri, 10 Mar 2000, in a never-ending search for enlightenment, R Joseph Wright wrote: Regardless, this is typically syptomatic of either a very old /boot/loader, non-use of the loader eg. through a /boot.config file, or an error in the entry for / in /etc/fstab. Isn't /boot/loader updated upon making a new world? If so, it ought to be current. I don't know any way of finding out since it's a binary file. /etc/fstab: /dev/ad0s4b noneswapsw 0 0 /dev/ad0s4a / ufs rw 1 1 /dev/ad0s4e /usrufs rw 2 2 /dev/acd0c /cdrom cd9660 ro,noauto 0 0 /dev/ad0s1 /dosmsdos ro,noauto 0 0 proc/proc procfs rw 0 0 Shouldn't all those "4"s be "1"s ? No, because I'm using the 4th slice for FreeBSD. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
On Tue, 7 Mar 2000, William Woods wrote: Good god, I am saying that the files to merger dont existthere is nothing to merge... This is the eror I get when trying to run ssdd /etc/ssh/sshd_config: No such file or directory the file sshd_config does not exist on my system to merge... That's because it's not under /etc until *after* you've run mergemaster. Right now it's sitting in /var/tmp/tmproot/etc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no openssh after build
On Mon, 6 Mar 2000, R Joseph Wright wrote: On Mon, 6 Mar 2000, Kris Kennaway wrote: On Mon, 6 Mar 2000, R Joseph Wright wrote: I just built a new world today and openssh does not appear to be installed. I have the directories /etc/ssh and /etc/ssl but they are empty. There is no /usr/bin/ssh. I've been trying to follow the discussions on this issue and I understood that this is now part of the default base system. Do you have the crypto sources installed? I just re-cvsupped today with crypto and rebuilt. Everything went as smooth as summer butter. I'm really impressed with how quickly and cleanly you developers are able to make things happen. I've only been observing for a short time but it is very interesting. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sshd in current....no config files in /etc/ssh
On Tue, Mar 07, 2000 at 12:02:38PM +, FreeBSD mailing list wrote: You know people, it's quite sad that those with knowledge simply refuse to answer simple questions without "RTFM" attitudes and indirect (and more frequently direct) insults to intelligence and sensibilities. When you have more experience helping people on a frequent basis, perhaps you will revise this statement. Try helping folks out every day on IRC for 2 or 3 years and tell me what you think THEN. Alternative: answer every question asked on freebsd-questions for same period. You'll see the point once you accomplish this. There is absolutely no reason why you can't submit the help, with suggestion toward ones perception of "the Right Way" to do it, rather than beat the issue to death with superior posturing. There is absolutely no reason why people should lift a finger to help somebody else when said question/inquiry has been documented somewhere on the web or in the manpages, or someplace else. You're right. However, there is no reason to lift a finger to not help someone either. If you don't want to help, simply don't. You save everyone energy. Being a jerk isn't going to keep people from posting elementary questions, that's a fact. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
single user weirdness
A strange thing has happened while booting into single user mode. My / filesystem was mounted on wd0s4a even though I have updated /dev and /etc/fstab to use ad0s4a. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
no openssh after build
I just built a new world today and openssh does not appear to be installed. I have the directories /etc/ssh and /etc/ssl but they are empty. There is no /usr/bin/ssh. I've been trying to follow the discussions on this issue and I understood that this is now part of the default base system. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: no openssh after build
On Mon, 6 Mar 2000, Kris Kennaway wrote: On Mon, 6 Mar 2000, R Joseph Wright wrote: I just built a new world today and openssh does not appear to be installed. I have the directories /etc/ssh and /etc/ssl but they are empty. There is no /usr/bin/ssh. I've been trying to follow the discussions on this issue and I understood that this is now part of the default base system. Do you have the crypto sources installed? Why, that's a very good question. Why, no, I don't have them installed. :) It wasn't really clear to me, actually. From my tracking of the discussions, which can be very muddy and hard to follow, I thought that openssh was automagically installed but was not really an *active* thing unless the rsaref port was also installed. Thanks for your reply. Joseph To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Am I doing this right?
On Sun, 27 Feb 2000, Steve Kaczkowski wrote: I'm trying to upgrade a 3.4 Release box to the latest Release tree, but running into a few problems, I'm betting someone here can help me! :) I cvsup'd the the latest Release and all went well (no complaints), here's my supfile: *default host=cvsup3.freebsd.org *default base=/usr *default prefix=/usr *default release=cvs tag=. The expression "tag=." will get you the latest 4.0-CURRENT sources. If you want to track -STABLE, that should be changed to "tag=RELENG_3". *default delete use-rel-suffix src-all cvs-crypto Nothing too strange there so I'm assuming that's ok. I then remove the /usr/obj directory do the 'make buildworld' which churns for a while (Only a P166) All seems fine with the build, now here is where I run into some issues. I've found some conflicting infomation as to what the next step is. One source says that I should recompile my kernel, reboot into single user and do a 'make installworld'. Makes sense but I can't recompile my kernel, I get errors like: config GENERIC config: line 20: Unknown machine type config: line 20: syntax error config: line 21: syntax error config: line 22: syntax error ... Specify machine type, e.g. ``machine vax'' Etc,etc,etc,etc... It doesn't know ANY x86 CPU, funny enough it doesn't complain if I stick in 'machine vax'. This is happening because under 4.0, you no longer need quotes around options, for example if you have cpu "I586_CPU" it would be changed to cpu I586_CPU Now if I do the 'make buildworld' then drop directly to single users and attempt the 'make installworld' it'll go for a bit and then finally error out with: install-info --quiet --defsection="Programming development tools." --defentry="* libcom_err: (com_err).A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir install-info: unrecognized option `--defsection=Programming development tools.' Try `install-info --help' for a complete list of options. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Not quite sure what to check, I've done this probably 10 times now and it seems to do the same thing each time... Any hints? Upgrading to 4.0 from 3.x is a little bit more complicated than simply doing "make buildworld make installworld". The file /usr/src/UPDATING will tell you how to do it under the heading "COMMON ITEMS". Also, note that 4.0 has not yet been released and is still under development, meaning be prepared to have flames in your mailbox should you ask any questions that are "stupid". You should also subscribe to freebsd-current. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Am I doing this right?
Also, note that 4.0 has not yet been released and is still under development, meaning be prepared to have flames in your mailbox should you ask any questions that are "stupid". You should also subscribe to freebsd-current. Whoa there, I thought I was replying to -questions. I didn't make myself look stupid, did I? =) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
pcm and /dev/dsp
In 4.0, the pcm sound driver works with my es1371 chipset soundcard for playing cds. But I cannot play mp3s. When I use mpg123, I get the error message "can't open /dev/dsp!" This is an improvement over 3.4, however, where I could not get pcm to work at all. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm and /dev/dsp
On Wed, 23 Feb 2000, Brooks Davis wrote: On Wed, Feb 23, 2000 at 12:15:39PM -0800, R Joseph Wright wrote: In 4.0, the pcm sound driver works with my es1371 chipset soundcard for playing cds. But I cannot play mp3s. When I use mpg123, I get the error message "can't open /dev/dsp!" This is an improvement over 3.4, however, where I could not get pcm to work at all. The first pcm device is now pcm0 not pcm1 for PCI devices. Did you do a "MAKEDEV snd0" after upgrading. My es1371 is working great streaming mp3s off of my.mp3.com using xmms. Beautiful. Thank you :) What about for isa cards? Which one is used for them now? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: pcm and /dev/dsp
On Wed, 23 Feb 2000, Brooks Davis wrote: On Wed, Feb 23, 2000 at 12:27:49PM -0800, R Joseph Wright wrote: Beautiful. Thank you :) What about for isa cards? Which one is used for them now? I gave my only ISA sound card to Camran so I can't say for sure, but if you hardware the probe address the card ends up at that number and I think PnP cards would end up at pcm0 by default. However, Nick gave the more correct answer in that you should check dmesg and /dev/sndstat. I actually do not have an isa sound card, I was merely curious because in 3.x, pcm0 was reserved for isa cards and pcm1 was used for pci. Is it now set up so that it doesn't matter whether the card is isa or pci, you just use pcm0? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrade from 3.4 to 4.0...
On Tue, 22 Feb 2000, Alfred Perlstein wrote: * William Woods [EMAIL PROTECTED] [000222 21:27] wrote: I did read that document, and honestly, it dident make a lot of sence and it seemed to have some conflicting instructions.which is why I am asking here. It looks pretty concise to me, perhaps you can explain the confusion so that we may fix it so as to help other users? It seems like it contains good information for those who have been on the track for awhile, while being a bit cryptic for people new to the process. Since this is a development version, I suppose that's to be expected. I followed the instructions that someone else posted on -questions: make buildworld make buildkernel make installkernel Then reboot in single user mode make -DNOINFO installworld make buildkernel make installkernel (again) make installworld This worked for me perfectly. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Upgrade from 3.4 to 4.0...
On Tue, 22 Feb 2000, William Woods wrote: On 23-Feb-00 R Joseph Wright wrote: make buildworld make buildkernel make installkernel Then reboot in single user mode make -DNOINFO installworld make buildkernel make installkernel (again) make installworld This worked for me perfectly. Hmmm.the only question I have regarding this is does it handle the new devices corectly? It did, although I did eventually remake them. I did: mv /dev /dev.old mkdir /dev cp /usr/src/etc/MAKE* /dev sh MAKEDEV all I also had to make the partition entries for my IDE drive: sh MAKEDEV ad0s4a Then I edited /etc/fstab to reflect the new devices --Very Important! Of course I also ran mergemaster to update the /etc directory. That's it. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
devices under 4.0
I recently upgraded from 3.2 to 4.0. I use an ide hard disk, and would like to know how to change over the devices. I created the new devices by copying over /usr/src/etc/MAKEDEV to a new /dev directory and running it, but it didn't create any ata* devices such as is shown in the kernel config file. It did make devices ada1, ada2, ada3, and ada4, which would correspond to the four slices on my disk, but if there are no freebsd partitions shown, such as ada4a, etc. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
