Re: Cannot boot with newly compiled kernel, or kernel.old after upgrading to RELENG_6

2005-12-05 Thread Torgeir Hoffmann
 --On Monday, December 05, 2005 01:06:09 AM +0100 Torgeir Hoffmann
[EMAIL PROTECTED] wrote:

 AFAIK
 If the nvidia-driver is from the ports you will need to disable it so
you
 can later rebuild it in 6.0.
 You will probably find all the details you need with a search.

Ok, thanks. I'll try it as soon as I get back home. Of some reason, I
assumed that
the nvidia module was recompiled in the process :-p

Well, thanks again.

//Torgeir Hoffmann




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Cannot boot with newly compiled kernel, or kernel.old after upgrading to RELENG_6

2005-12-04 Thread Torgeir Hoffmann
Hi,

I have been so unfortunate to be left with a completely unusable system
after updating to RELENG_6 from RELENG_5.

I am quite sure that I followed the step from the handbook correctly, but
as mentioned the system is unbootable.

The error when trying to boot the new kernel makes the system reboots
after 15 seconds, so I haven't had the opportunity to write that one down.
However, the error message from when trying: unload, boot
/boot/kernel.old/kernel I was able to copy down in full (see bottom).

If I try to unload linux.ko by ' set linux_load=NO ', it goes a bit
further. I can only see acpi.ko: could not finalize loading flash by,
and several PNP0303 can't assign... error messages before it mounts, it
finishes to load ipfw2 and then suddenly it says

'Warning: Device driver  ' then nothing more on the line, then a similar
error message to the one at bottom follows. (page fault). Reboots after 15
seconds.


I really hope someone knows what this is all about - I have no idea why
this is happening. Further I cannot understand why kernel.old doesn't work
- after all I've used that kernel for 6 months without any issues. Mind
that this is the GENERIC kernel, and it was compiled with unmodified conf.

Hope for quick reply,

Best regards,

Torgeir Hoffmann



-- Error message --

link_elf: symbol VOP_READDIR_APV undefined
KLD file linux.ko - could not finalize loading.
kernel trap 12 with interups disabled

Fatal trap 12: page fault while in kernel mode.
fault virtual address = 0x8
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc060bdff
stack pointer = 0x10:0xc1020d24
frame pointer = 0x10:0xc1020d24
code segment = base 0x0, limit 0xf, type x1b
= DPL 0, pres 1, def32 1, gran 1
processlr elfags = resume, IOPL = 0
current process = 0 ()
trap number  = 12
panic: page fault
uptime: 1s

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Cannot boot with newly compiled kernel, or kernel.old after upgrading to RELENG_6

2005-12-04 Thread Kent Stewart
On Sunday 04 December 2005 11:43 am, Torgeir Hoffmann wrote:
 Hi,

 I have been so unfortunate to be left with a completely unusable
 system after updating to RELENG_6 from RELENG_5.


I read that the path was to RELENG_6_0_0_RELEASE and then to stable. I 
just finished upgrading 2 machines that way.

 I am quite sure that I followed the step from the handbook correctly,
 but as mentioned the system is unbootable.

Did you copy the 6.0 GENERIC config file into the one your buildkernel 
make uses?


 The error when trying to boot the new kernel makes the system reboots
 after 15 seconds, so I haven't had the opportunity to write that one
 down. However, the error message from when trying: unload, boot
 /boot/kernel.old/kernel I was able to copy down in full (see
 bottom).

You should only load the 5-stable kernel and the boot -s. You have a 
mixed kernel and userland. You can't expect kernel.old and your 
6-stable userland to work.


 If I try to unload linux.ko by ' set linux_load=NO ', it goes a bit
 further. I can only see acpi.ko: could not finalize loading flash
 by, and several PNP0303 can't assign... error messages before it
 mounts, it finishes to load ipfw2 and then suddenly it says

 'Warning: Device driver  ' then nothing more on the line, then a
 similar error message to the one at bottom follows. (page fault).
 Reboots after 15 seconds.


 I really hope someone knows what this is all about - I have no idea
 why this is happening. Further I cannot understand why kernel.old
 doesn't work - after all I've used that kernel for 6 months without
 any issues. Mind that this is the GENERIC kernel, and it was compiled
 with unmodified conf.


But that was for a 5-stable userland. Now, your userland is 6.0. 

 Hope for quick reply,

 Best regards,

 Torgeir Hoffmann



 -- Error message --

 link_elf: symbol VOP_READDIR_APV undefined
 KLD file linux.ko - could not finalize loading.
 kernel trap 12 with interups disabled

 Fatal trap 12: page fault while in kernel mode.
 fault virtual address = 0x8
 fault code = supervisor read, page not present
 instruction pointer = 0x8:0xc060bdff
 stack pointer = 0x10:0xc1020d24
 frame pointer = 0x10:0xc1020d24
 code segment = base 0x0, limit 0xf, type x1b
 = DPL 0, pres 1, def32 1, gran 1
 processlr elfags = resume, IOPL = 0
 current process = 0 ()
 trap number  = 12
 panic: page fault
 uptime: 1s

 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Cannot boot with newly compiled kernel, or kernel.old after upgrading to RELENG_6

2005-12-04 Thread Lars Kristiansen



--On Sunday, December 04, 2005 12:03:15 PM -0800 Kent Stewart 
[EMAIL PROTECTED] wrote:



On Sunday 04 December 2005 11:43 am, Torgeir Hoffmann wrote:

Hi,


Hei!


I have been so unfortunate to be left with a completely unusable
system after updating to RELENG_6 from RELENG_5.



I read that the path was to RELENG_6_0_0_RELEASE and then to stable. I
just finished upgrading 2 machines that way.


I am quite sure that I followed the step from the handbook correctly,
but as mentioned the system is unbootable.


Did you copy the 6.0 GENERIC config file into the one your buildkernel
make uses?



Think I saw some others reported problems with the new acpi on some 
hardware.

Try to boot without it, safe mode in the bootmenu, I think.
You may find some more in the archives for both this list and 
freebsd-stable.


--
Hilsen Lars



The error when trying to boot the new kernel makes the system reboots
after 15 seconds, so I haven't had the opportunity to write that one
down. However, the error message from when trying: unload, boot
/boot/kernel.old/kernel I was able to copy down in full (see
bottom).


You should only load the 5-stable kernel and the boot -s. You have a
mixed kernel and userland. You can't expect kernel.old and your
6-stable userland to work.



If I try to unload linux.ko by ' set linux_load=NO ', it goes a bit
further. I can only see acpi.ko: could not finalize loading flash
by, and several PNP0303 can't assign... error messages before it
mounts, it finishes to load ipfw2 and then suddenly it says

'Warning: Device driver  ' then nothing more on the line, then a
similar error message to the one at bottom follows. (page fault).
Reboots after 15 seconds.


I really hope someone knows what this is all about - I have no idea
why this is happening. Further I cannot understand why kernel.old
doesn't work - after all I've used that kernel for 6 months without
any issues. Mind that this is the GENERIC kernel, and it was compiled
with unmodified conf.



But that was for a 5-stable userland. Now, your userland is 6.0.


Hope for quick reply,

Best regards,

Torgeir Hoffmann



-- Error message --

link_elf: symbol VOP_READDIR_APV undefined
KLD file linux.ko - could not finalize loading.
kernel trap 12 with interups disabled

Fatal trap 12: page fault while in kernel mode.
fault virtual address = 0x8
fault code = supervisor read, page not present
instruction pointer = 0x8:0xc060bdff
stack pointer = 0x10:0xc1020d24
frame pointer = 0x10:0xc1020d24
code segment = base 0x0, limit 0xf, type x1b
= DPL 0, pres 1, def32 1, gran 1
processlr elfags = resume, IOPL = 0
current process = 0 ()
trap number  = 12
panic: page fault
uptime: 1s

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]


--
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Cannot boot with newly compiled kernel, or kernel.old after upgrading to RELENG_6

2005-12-04 Thread Torgeir Hoffmann
Hi,

thanks a lot for quick reply.

 Did you copy the 6.0 GENERIC config file into the one your buildkernel
make uses?

No, actually I didn't. From what I could see on
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html,
I didn't think it was necessary.

 The error when trying to boot the new kernel makes the system reboots
after 15 seconds, so I haven't had the opportunity to write that one
down. However, the error message from when trying: unload, boot
/boot/kernel.old/kernel I was able to copy down in full (see
 bottom).

 You should only load the 5-stable kernel and the boot -s. You have a
mixed kernel and userland. You can't expect kernel.old and your
 6-stable userland to work.

If I understand you correctly, that would mean that even if I haven't yet
done installworld, my userland is still 6.0? I'm terribly sorry if I
wasn't clear on that point.
Thanks for the boot command - it worked very well.

I thought I'd try to cvsup the sourcetree to RELENG_6_0 instead now, and
then try to recompile. Is that a good idea? I was thinking, since
installworld hasn't been done yet?


Many thanks,

Torgeir Hoffmann




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Cannot boot with newly compiled kernel, or kernel.old after upgrading to RELENG_6

2005-12-04 Thread Kent Stewart
On Sunday 04 December 2005 12:56 pm, Torgeir Hoffmann wrote:
 Hi,

 thanks a lot for quick reply.

  Did you copy the 6.0 GENERIC config file into the one your
  buildkernel

 make uses?

Probably GENERIC. I use the equivalent of 
make buildkernel KERNCONF=RUBY
make installkernel KERNCONF=RUBY
but I have then built into scripts.

If you have a KERNCONF entry in /etc/make.conf, it uses that. If it was 
your 5-stable config file, it used it.


 No, actually I didn't. From what I could see on
 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.h
tml, I didn't think it was necessary.

Everytime they do an upgrade, you need to check it. Options come and go.

I also turned off all of my processes (ports) that normal start such as 
apache and boinc-seti. They may run but you need to upgrade them to 
ports built on 6-stable.


  The error when trying to boot the new kernel makes the system
  reboots

 after 15 seconds, so I haven't had the opportunity to write that one
 down. However, the error message from when trying: unload, boot
 /boot/kernel.old/kernel I was able to copy down in full (see

  bottom).
 
  You should only load the 5-stable kernel and the boot -s. You have
  a

 mixed kernel and userland. You can't expect kernel.old and your

  6-stable userland to work.

 If I understand you correctly, that would mean that even if I haven't
 yet done installworld, my userland is still 6.0? I'm terribly sorry
 if I wasn't clear on that point.
 Thanks for the boot command - it worked very well.

If you haven't done an installworld, you shouldn't do anything but boot 
-s. 

You have to finish the install and then you can use the full boot.


 I thought I'd try to cvsup the sourcetree to RELENG_6_0 instead now,
 and then try to recompile. Is that a good idea? I was thinking, since
 installworld hasn't been done yet?

No idea on that. I always do the buildworld, make kernel, boot single 
user and installworld and run mergemaster. I have had kernels that 
would immediately panic and the boot to single user mode is to catch 
them. 

You have a new user called _dhcp that needs to be added to group and 
master.passwd. Then, you have what seems like 100's of files that need 
to be updated using mergemaster.

Kent


 Many thanks,

 Torgeir Hoffmann




 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to
 [EMAIL PROTECTED]

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Cannot boot with newly compiled kernel, or kernel.old after upgrading to RELENG_6

2005-12-04 Thread Kent Stewart
On Sunday 04 December 2005 01:18 pm, Kent Stewart wrote:
 On Sunday 04 December 2005 12:56 pm, Torgeir Hoffmann wrote:

I thought that I should pass on problems that I encountered during my 
update from 5-stable to 6-stable.

I cvsup to 6.0-release, copied GENERIC to RUBY. Ruby is the computer 
that I was upgrading. I cd'ed into /usr/obj and rm -rf *. You don't 
need to bother about changing the flags. /usr/obj/usr and descendants 
just disappeared.

After the cvsup, I cd'ed into /usr/src and did a make cleandir 2 
times. This was all before I did my first buildworld.

After, I finished the buildworld and kernel, I tried to do the boot -s 
but right now FreeBSD does not handle the Netgear GA311 1000baseT NIC 
properly. If I didn't do a power down in the transition it would panic. 
It isn't reseting the NIC properly. Windows XP does and FreeBSD 
doesn't. FreeBSD handles a power up just fine. Doing a power down and 
then booting to FreeBSD 6-stable only adds 20-30 seconds to the overall 
boot time. It is not that irritating :).

Ruby is my source machine. I do port builds on it and create packages. 
Not all packages will install and work properly. For example, KDE has 
never upgraded properly with packages that I build on ruby and move to 
my other computers. Right now, if I build packages on ruby and use 
them, kmail disappears. I use kmail 100% except for yahoo, gmail and 
hotmail. Both Yahoo and Hotmail are webmail. 

For the gmail account I use mozilla-thunderbird. Rain and shine 
thunderbird works. Even in the middle of the upgrade to 6-stable, I 
could use thunderbird. Kmail is part of a system and thunderbird is a 
standalone product. I would be surprised if thunderbird didn't work.

Updating my ports was a bit confusing. Openssl demands to be changed to 
openssl-stable. I finally let it. I found that later it would upgrade 
to the current version. Just ignore it for starters.

Ports with problems - Audio on FreeBSD 5-6 is a toss up. It doesn't 
matter which port you use. I have 3 computers with Creative sound cards 
and 5.1 speakers. The current emu10k1 drivers use the speakers behind 
me. It is kind of bothering to me to listen to audio when the sound is 
playing behind me :). 

It doesn't really affect me because I always have one of the computers 
on my kvm switch running XP and XP plays the audio out of the right 
speakers, i.e., the front ones :). If I use Windows Media Player, I can 
let my friends know who I am listenting to. So, I am sitting here 
listening to Mi sangre tour de Juanes on XP and working on my FreeBSD 
machines. FWIW, the cd has suround sound effects and having them come 
out of the correct speakers is not spatially confusing :).

With the exception of a confused sound setup, I have had no problems 
with 6-stable after I got all of my ports upgraded to 6-stable.

Kent

-- 
Kent Stewart
Richland, WA

http://users.owt.com/kstewart/index.html
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Cannot boot with newly compiled kernel, or kernel.old after upgrading to RELENG_6

2005-12-04 Thread Torgeir Hoffmann
 On Sunday 04 December 2005 12:56 pm, Torgeir Hoffmann wrote:

Hi again,

tried to rebuild the base once more, after syncing up with RELENG_6_0, and
as far as I can see it worked like a charm. However, I still can't boot
the system after building a new kernel. Even when booting the system with
boot -s, the new kernel throws a page fault, and reboots after 15
seconds.

I tried to follow the other lead concerning ACPI, although I haven't had
time to search thoroughly through lists. I tried using  unset acpi_load 
before boot -s, but it still produces the same result.

I'm starting suspect that it might have something to do with the nvidia,
as it is the last thing I see before the error occurs. I see:

output
nvidia0 //some stuff I didn't catch in time - I assume hardware
details
Warning: Device driver 
/output
(page fault error similar to the one posted earlier) Also, I have no idea
why it produces a single double-dash (  ).

  Did you copy the 6.0 GENERIC config file into the one your
  buildkernel
 make uses?

 Probably GENERIC. I use the equivalent of
 make buildkernel KERNCONF=RUBY
 make installkernel KERNCONF=RUBY
 but I have then built into scripts.

yes, I've had most things I needed in GENERIC, and loaded modules for the
sound  - that's it.

 If you have a KERNCONF entry in /etc/make.conf, it uses that. If it was
your 5-stable config file, it used it.

 Everytime they do an upgrade, you need to check it. Options come and go.
I didn't have a make.conf entry with KERNCONF - so I can only assume that
it uses GENERIC, and further I'd assume that I'd use the one that came
with the source checkout. Afterall, the world and kernel compiled fine,
the kernel does not, however, seem to be happy to boot.

 If you haven't done an installworld, you shouldn't do anything but boot -s.

 You have to finish the install and then you can use the full boot.
Unfortunately, the bottleneck still persists - and I have a gut feeling
that I won't get anywhere booting the RELENG_5 kernel and installing the
base. I guess that'd would only make it more of a mess, than what'd I've
already made it...

 I have had kernels that
 would immediately panic and the boot to single user mode is to catch them.

 You have a new user called _dhcp that needs to be added to group and
master.passwd. Then, you have what seems like 100's of files that need
to be updated using mergemaster.

Thanks for the tip - I ran mergemaster -p before buildworld, and that
_dhcp user was added.

Thanks for all help so far.

Best Regards,

Torgeir Hoffmann




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Cannot boot with newly compiled kernel, or kernel.old after upgrading to RELENG_6

2005-12-04 Thread Lars Kristiansen



--On Monday, December 05, 2005 01:06:09 AM +0100 Torgeir Hoffmann 
[EMAIL PROTECTED] wrote:



On Sunday 04 December 2005 12:56 pm, Torgeir Hoffmann wrote:


Hi again,

tried to rebuild the base once more, after syncing up with RELENG_6_0, and
as far as I can see it worked like a charm. However, I still can't boot
the system after building a new kernel. Even when booting the system with
boot -s, the new kernel throws a page fault, and reboots after 15
seconds.

I tried to follow the other lead concerning ACPI, although I haven't had
time to search thoroughly through lists. I tried using  unset acpi_load 
before boot -s, but it still produces the same result.

I'm starting suspect that it might have something to do with the nvidia,


AFAIK
If the nvidia-driver is from the ports you will need to disable it so you 
can later rebuild it in 6.0.

You will probably find all the details you need with a search.

--
Lars


as it is the last thing I see before the error occurs. I see:

output
nvidia0 //some stuff I didn't catch in time - I assume hardware
details
Warning: Device driver 
/output
(page fault error similar to the one posted earlier) Also, I have no idea
why it produces a single double-dash (  ).


 Did you copy the 6.0 GENERIC config file into the one your
 buildkernel
make uses?



Probably GENERIC. I use the equivalent of
make buildkernel KERNCONF=RUBY
make installkernel KERNCONF=RUBY
but I have then built into scripts.


yes, I've had most things I needed in GENERIC, and loaded modules for the
sound  - that's it.


If you have a KERNCONF entry in /etc/make.conf, it uses that. If it was

your 5-stable config file, it used it.


Everytime they do an upgrade, you need to check it. Options come and go.

I didn't have a make.conf entry with KERNCONF - so I can only assume that
it uses GENERIC, and further I'd assume that I'd use the one that came
with the source checkout. Afterall, the world and kernel compiled fine,
the kernel does not, however, seem to be happy to boot.


If you haven't done an installworld, you shouldn't do anything but boot
-s.

You have to finish the install and then you can use the full boot.

Unfortunately, the bottleneck still persists - and I have a gut feeling
that I won't get anywhere booting the RELENG_5 kernel and installing the
base. I guess that'd would only make it more of a mess, than what'd I've
already made it...


I have had kernels that
would immediately panic and the boot to single user mode is to catch
them.

You have a new user called _dhcp that needs to be added to group and

master.passwd. Then, you have what seems like 100's of files that need
to be updated using mergemaster.

Thanks for the tip - I ran mergemaster -p before buildworld, and that
_dhcp user was added.

Thanks for all help so far.

Best Regards,

Torgeir Hoffmann




___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]




--
Med vennlig hilsen
Lars Kristiansen

A D V E N T U R A S
Tlf: 22 20 59 90
Fax: 22 20 59 91
[EMAIL PROTECTED]
http://www.adventuras.no

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]