Re: URGENT! SHOW STOPPER! moused is broken!
> > I am sorry. A report just came in, and I now have to conclude > > that the last minutes MFC of moused was ill-conceived. That supposed > > improvement on the 3 button emulation actually broke the wheel/roller > > support in moused ;-< (Moused is now broken in both -CURRENT and > > -STABLE.) > > Eek. OK, well, the release just finished this morning after laying > the tag down tonite but I haven't copied it anywhere yet. I'll slide > the tags forward in -stable and start the build over again. It won't > result in more than a 6 hour delay and 4 or 5 messages in my mailbox > wondering where 3.4-RELEASE is. :-) > > Don't worry about it, mistakes happen and we caught this one before > it became a real problem. Thanks for doing this Jordan! Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: URGENT (?) booting from CD on Atapi
Mike Smith once wrote: > > A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) would > > not boot from 3.3 CD if the SCSI disks are online. It would say: > > "Read Error" on the upper left of the screen -- where you'd normally > > see the spinning dash. I suspect, this is a loader's bug :(, which > > may make it to 3.4 ... > This is a bug in your BIOS, or your configuration of your system. The > loader is not running at that point; the 'Read Error' message is boot1 > trying to load boot2 and failing, typically due to a bad value in %dl > passed by the BIOS. Well, I figured, it is not the BIOS, who says "Read Error", but did not know which part of the boot process :) I was hoping to shed some light on the problem, that was reported shortly after the 3.3RELEASE, when some people were and some were not able to boot from their CD-ROMs. May be this (common?) BIOS' brokennes can be worked around in boot1? > > The workaround is to disconnect the SCSI chain at the boot time and > > connect it back when the /boot/loader gives the prompt -- the kernel > > will find the disks nicely. > > I assume that the system boots correctly from disk once FreeBSD is > installed? Yes. -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: URGENT! SHOW STOPPER! moused is broken!
I apologize again to anybody who have been waiting for 3.4-RELEASE for causing this delay. It was my fault that my last-minute MFC actually broke something. I will be more cautious in the future. Sorry. Kazu >> Eek. OK, well, the release just finished this morning after laying >> the tag down tonite but I haven't copied it anywhere yet. I'll slide >> the tags forward in -stable and start the build over again. It won't >> result in more than a 6 hour delay and 4 or 5 messages in my mailbox >> wondering where 3.4-RELEASE is. :-) >> >> Don't worry about it, mistakes happen and we caught this one before >> it became a real problem. > >Thanks for doing this Jordan! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
No Subject
To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: URGENT (?) booting from CD on Atapi
On Fri, 17 Dec 1999, Mikhail Teterin wrote: > Hello! > > This may be a bit late :-| > > A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) would not > boot from 3.3 CD if the SCSI disks are online. It would say: "Read > Error" on the upper left of the screen -- where you'd normally see the > spinning dash. I suspect, this is a loader's bug :(, which may make it > to 3.4 ... Don't see a problem with that here. I just booted the 3.3-R CD on an ATAPI CD ROM with no other IDE devices, and everything was fine. Tom Uniserve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Join FreeBSD Stable
subscribe freebsd-stable -- [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: URGENT (?) booting from CD on Atapi
Tom once stated: =On Fri, 17 Dec 1999, Mikhail Teterin wrote: = => Tom once stated: => => =On Fri, 17 Dec 1999, Mikhail Teterin wrote: => = => => A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) would => => not boot from 3.3 CD if the SCSI disks are online. It would say: => => "Read Error" on the upper left of the screen -- where you'd => => normally see the spinning dash. I suspect, this is a loader's bug => => :(, which may make it to 3.4 ... => = => = Don't see a problem with that here. I just booted the 3.3-R CD on => =an ATAPI CD ROM with no other IDE devices, and everything was fine. => => Do you have SCSI disks online at the boot time? = = Yes. Lucky you... Are the SCSI disks otherwise bootable? Is the CD on the primary or the secondary IDE channel? -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: URGENT (?) booting from CD on Atapi
> Mike Smith once wrote: > > > > A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) would > > > not boot from 3.3 CD if the SCSI disks are online. It would say: > > > "Read Error" on the upper left of the screen -- where you'd normally > > > see the spinning dash. I suspect, this is a loader's bug :(, which > > > may make it to 3.4 ... > > > This is a bug in your BIOS, or your configuration of your system. The > > loader is not running at that point; the 'Read Error' message is boot1 > > trying to load boot2 and failing, typically due to a bad value in %dl > > passed by the BIOS. > > Well, I figured, it is not the BIOS, who says "Read Error", but did not > know which part of the boot process :) I was hoping to shed some light > on the problem, that was reported shortly after the 3.3RELEASE, when > some people were and some were not able to boot from their CD-ROMs. May > be this (common?) BIOS' brokennes can be worked around in boot1? No. The 3.3-RELEASE issue (which was also detailed here) was another BIOS bug which prevented the CDROM from being recognised as bootable at all. If your code is never run, you can't 'work around' anything. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ld.so failed: Can't find shared library..
One of the servers I now manage is a 2.2.5-RELEASE server. I recently tried running cvsup from a shell and got: ld.so failed: Can't find shared library "libset.so.6.0" What is libset.so.6.0 a part of? I have also been having difficulty making the openssh port due to what appears to be a new flag to ld (--whole-archive) since the birth of this machine. What are my upgrade options? This is a production server with little tolerance for downtime and I haven't been a FreeBSD'er for long enough to know exactly how to fix these problems. -- Ben mailto:[EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: URGENT (?) booting from CD on Atapi
Mike Smith once stated: => Ok... So this is a different one, then... What information do I need => to provide for someone to be able to make a "work around" for _it_? = =It's not clear that you can; it's possible that your setup is just "too =broken" for us. = =A good start would be to test some other supposedly bootable CDROMs =(W96, NT4.0, RedHat 6.1) and see if they work. No, I can not afford rebooting this box :( It is a "production" machine. Only what I can get during run-time. But it can boot from the CDROM if there are no disks attached. Oh, yeah, the boot disk's SCSI id is set in the adapter's BIOS as 6, and the second disk has the id 8... -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
RE: ld.so failed: Can't find shared library..
On 18-Dec-99 Ben WIlliams wrote: >One of the servers I now manage is a 2.2.5-RELEASE server. I This system is excessively old.. you should upgrade it to a newer version, say, at least 3.1-RELEASE or later. > recently tried running cvsup from a shell and got: > > ld.so failed: Can't find shared library "libset.so.6.0" That looks like an a.out library.. >What is libset.so.6.0 a part of? I have also been having difficulty > making the openssh port due to what appears to be a new flag to ld > (--whole-archive) since the birth of this machine. Ports are not really guaranteed to work on any version of FreeBSD other than the latest -STABLE (and there are exceptions for that) and -CURRENT. Try upgrading this system to a newer version of FreeBSD. >What are my upgrade options? This is a production server with > little tolerance for downtime and I haven't been a FreeBSD'er for long > enough to know exactly how to fix these problems. That is understandable. I'd actually guessed it was a production server. You can minimize downtime by building the 3.x world and then dropping to single user mode to install the world. However, I've never really tried to upgrade from 2.2.x to 3.x. I just backup the machine and format and reinstall using 3.x CDs. 2.x -> 3.x is a HUGE upgrade.. your best bet would be to load balance the server's services among other servers while you upgrade it. Or to load a copy of 3.x on a new server, set it up, and transfer sensitive data to the new server, test it, then when it's ready, take the old one off and put the new one on. Sorry, I really can't offer any better ideas without further information. -- Will Andrews <[EMAIL PROTECTED]> GCS/E/S @d- s+:+>+:- a--->+++ C++ UB P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++> DI+++ D+ G++>+++ e-> h! r-->+++ y? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: URGENT (?) booting from CD on Atapi
On Fri, 17 Dec 1999, Mikhail Teterin wrote: > Tom once stated: > > =On Fri, 17 Dec 1999, Mikhail Teterin wrote: > = > => Tom once stated: > => > => =On Fri, 17 Dec 1999, Mikhail Teterin wrote: > => = > => => A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) would > => => not boot from 3.3 CD if the SCSI disks are online. It would say: > => => "Read Error" on the upper left of the screen -- where you'd > => => normally see the spinning dash. I suspect, this is a loader's bug > => => :(, which may make it to 3.4 ... > => = > => = Don't see a problem with that here. I just booted the 3.3-R CD on > => =an ATAPI CD ROM with no other IDE devices, and everything was fine. > => > => Do you have SCSI disks online at the boot time? > = > = Yes. > > Lucky you... Are the SCSI disks otherwise bootable? Is the CD on the > primary or the secondary IDE channel? The SCSI disk is bootable in that set in the BIOS to boot (I used "A: CD C:" boot order), but I don't think it has an OS on it. You could just have a boot order issue. Maybe the SCSI disk has a screwed up boot sector, and SCSI disk is earlier in the boot order ("A: C: CD"), so it never gets to the CD. > -mi > > Tom Uniserve To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message