Re: Undefined symbol on boot
> From: [EMAIL PROTECTED] > Date: Wed, 27 Dec 2000 21:55:51 -0500 (EST) > ::md0: Malloc disk > ::WARNING: Driver mistake: destroy_dev on 154/0 > ::** what's this? * > > I'm not sure about this one. It looks like a bug in the 'asr' driver. Mark - I'm guessing that you have a codepath that's calling destroy_dev() even though no adapters have been found/probed/etc. This isn't entirely bad, it just generates this slightly confusing warning. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Undefined symbol on boot
[EMAIL PROTECTED] writes: > I'm not sure if this is the correct list or not - apologies if > it's wrong. There's no substitute for reading /usr/src/UPDATING. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Undefined symbol on boot
On Thu, Dec 28, 2000 at 12:33:29PM +0900, Munehiro Matsuda thus spoke: > From: [EMAIL PROTECTED] > Date: Wed, 27 Dec 2000 21:55:51 -0500 (EST) > ::md0: Malloc disk > ::WARNING: Driver mistake: destroy_dev on 154/0 > ::** what's this? * > > I'm not sure about this one. > > ::Mounting root from ufs:/dev/ad0s2a > ::link_elf: symbol tsleep undefined > ::*** < first error > ::Old-style KLD file fire_saver found > ::link_elf: symbol exit undefined > :: ::pid 215 (ldconfig), uid 0: exited on signal 11 (core dumped) > ::* <3rd > ::link_elf: symbol tsleep undefined > :: You must have old modules in /modules directory. > Rename /modules to something else or remove everything in it. > On 5-Current, kernel and kernel modules now live in /boot/kernel/. > But /modules and /boot/modules are searched first. > Hope this helps, Thanks a lot. That fixed it. I really appreciate this. Bill -- Bill Vermillion - bv @ wjv . com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Undefined symbol on boot
On Thu, Dec 28, 2000 at 01:15:38PM +1000, Sleepless in Brisbane thus spoke: > On Wed, 27 Dec 2000 [EMAIL PROTECTED] wrote: > > Reply to: [EMAIL PROTECTED] > > X-Mailer: ELM [version 2.5 PL3] > > MIME-Version: 1.0 > > Content-Type: text/plain; charset=us-ascii > > Content-Transfer-Encoding: 7bit > > I'm not sure if this is the correct list or not - apologies if > > it's wrong. > > I just updated a machine with cvsup for the first time - and may > > have done something wrong. > > When I rebuilt everything and boot a uname gives me 5.0-CURRENT. > > [I picked the wrong one as I guess I wanted release - but that's > > not the problem]. > Umm.. that is the problem. There is a lot more hassle normally > involved in going from a RELEASE kernel to a CURRENT one than > usually a make world can fix. Do you really want to be doing this > if you are just after an updated kernel? If not - I suggest going > back to STABLE. I found where the errors are coming from - it's in the compatibility modules. If I take out compatibility for linux, sysv, and ibcs, things run just as they are supposed to. So how do I fix the compats - or is that something coming later. I don't really need it at the moment.1 -- Bill Vermillion - bv @ wjv . com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Undefined symbol on boot
From: [EMAIL PROTECTED] Date: Wed, 27 Dec 2000 21:55:51 -0500 (EST) ::md0: Malloc disk ::WARNING: Driver mistake: destroy_dev on 154/0 ::** what's this? * I'm not sure about this one. ::Mounting root from ufs:/dev/ad0s2a ::link_elf: symbol tsleep undefined ::*** < first error ::Old-style KLD file fire_saver found ::link_elf: symbol exit undefined ::
Re: Undefined symbol on boot
On Thu, Dec 28, 2000 at 01:15:38PM +1000, Sleepless in Brisbane thus spoke: > On Wed, 27 Dec 2000 [EMAIL PROTECTED] wrote: > > Reply to: [EMAIL PROTECTED] > > X-Mailer: ELM [version 2.5 PL3] > > MIME-Version: 1.0 > > Content-Type: text/plain; charset=us-ascii > > Content-Transfer-Encoding: 7bit > > I'm not sure if this is the correct list or not - apologies if > > it's wrong. > > I just updated a machine with cvsup for the first time - and may > > have done something wrong. > > When I rebuilt everything and boot a uname gives me 5.0-CURRENT. > > [I picked the wrong one as I guess I wanted release - but that's > > not the problem]. > Umm.. that is the problem. There is a lot more hassle normally > involved in going from a RELEASE kernel to a CURRENT one than > usually a make world can fix. Do you really want to be doing this > if you are just after an updated kernel? If not - I suggest going > back to STABLE. Well I don't hvae a problem with going to this release. The machine was originally booted with a 4.1 - the one with the keyboard problem, and I upgraded it to a 4.2 - but since it was an upgrade it didn't let me put new sources on. >From what I read you could complete move up, buy removing everything, and preforming the bmildworld, buildkernel, installkernel, and installworld. This should have removed every trace of any 4.[12] on the system, should it not. The machine is to replace this one - whose motherboard is getting tired and cranky. It's just that one undefinded symbol and exit. If I KNEW where that was coming from it might help. So this machine is a 4.0 - the machine where I posted from was a 4.1 > 4.2 > 5.0 I figured I'd better learn this cvs method - and this seemed like a good time. Bill -- Bill Vermillion - bv @ wjv . com To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Undefined symbol on boot
On Wed, 27 Dec 2000 [EMAIL PROTECTED] wrote: > Reply to: [EMAIL PROTECTED] > X-Mailer: ELM [version 2.5 PL3] > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > I'm not sure if this is the correct list or not - apologies if > it's wrong. > > I just updated a machine with cvsup for the first time - and may > have done something wrong. > > When I rebuilt everything and boot a uname gives me 5.0-CURRENT. > [I picked the wrong one as I guess I wanted release - but that's > not the problem]. Umm.. that is the problem. There is a lot more hassle normally involved in going from a RELEASE kernel to a CURRENT one than usually a make world can fix. Do you really want to be doing this if you are just after an updated kernel? If not - I suggest going back to STABLE. -- Snowy Maslov aka Snowpony My... [ www.vulpine.pp.se/cgi-bin/furcode ] |\= http://snowy.furart.org/Art FEHuw3acdm A+ C- Dm++ H+++ M P+++ - - = http://www.furryfaire.org/ Life R++ T+++ W- Z++ Sf# RLCT/M a cbu$ '- http://www.furart.org/ Dreams d- e+ f+++ h+ iwf+++$ j+ p* sm#>f# To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
