1 |
Hi Steve, |
2 |
thanks again for the fast response. udev worked real slick. |
3 |
|
4 |
I realized my system clock was set to ~1953 (perhaps this has some thing |
5 |
to do with the mysterious crashes). |
6 |
|
7 |
I will read up on cross-compiling over the holiday and give my own |
8 |
kernel build a shot. |
9 |
|
10 |
-have a good one |
11 |
Andy |
12 |
|
13 |
|
14 |
On Tue, 2004-12-07 at 10:03, Stephen P. Becker wrote: |
15 |
> Andrew Finley wrote: |
16 |
> > Hi Steve (didn't know if this should go to the list or not), |
17 |
> > |
18 |
> > I have had a few crashes with the fallowing kernel error (this is the |
19 |
> > binary kernel you sent me): |
20 |
> > |
21 |
> > [<ffffffffffffff8045d758>]_set_up_early_setup_test+0xfffffeefef0000.... |
22 |
> > Code: a400000 .... |
23 |
> > kernel panic - not syncing: Aiee, killing interrupt handler! |
24 |
> |
25 |
> I have not seen this even once with my kernel. Perhaps you have a |
26 |
> really old prom version that is doing something funky, but I just don't |
27 |
> know. You didn't try to do something funky with objcopy to change the |
28 |
> address or something did you? |
29 |
> |
30 |
> > |
31 |
> > I noticed some funny things during the boot sequence: |
32 |
> > |
33 |
> > 1) |
34 |
> > *Setting system clock to hardware clock [UTC]... |
35 |
> > |
36 |
> > FATAL: Could not load /lib/modules/2.6.10-rc1/modules.dep: No such file |
37 |
> > or directory |
38 |
> > |
39 |
> > *Failed to set system clock to hardware clock |
40 |
> |
41 |
> This is a known problem. The O2 rtc has been broken since 2.6.9 |
42 |
> somehow. I've talked to somebody that said they haven't seen this |
43 |
> problem at all. I'm wondering if it is a result of a) the gentoo |
44 |
> toolchain or b) a patch I'm using. |
45 |
> |
46 |
> Also, my kernel wasn't compiled with module support at all...in fact, I |
47 |
> think mine is 2.6.10-rc2. I know why you are getting the error (kernel |
48 |
> looking to autoload rtc module probably), but I don't know why it is |
49 |
> looking for the module at all. |
50 |
> |
51 |
> > |
52 |
> > 2) |
53 |
> > "ERROR: Problem starting needed services. "bootmisc" was not started" |
54 |
> > |
55 |
> |
56 |
> Not sure what the deal is here without more information, but it isn't |
57 |
> fatal. You probably have some service set up to start which isn't |
58 |
> installed or is broken. Check your boot logs. |
59 |
> |
60 |
> > |
61 |
> > I tried several other precompiled kernels (for the o2), but none have |
62 |
> > DEVFS support, which I understand gentoo requires. |
63 |
> |
64 |
> Gentoo most certainly doesn't require devfs. Our stages ship with a |
65 |
> static /dev directory. You can boot with "gentoo=nodevfs" to avoid an |
66 |
> annoying error about devfs on boot. However, what is even better is |
67 |
> udev. Just "emerge udev" and boot a 2.6 kernel...and Gentoo's init |
68 |
> scripts take care of the rest. |
69 |
> |
70 |
> > |
71 |
> > Do you know what the problem might be? If so how might I fix it, short |
72 |
> > of compiling my own kernel. |
73 |
> |
74 |
> You really should learn to build your own kernel anyway. I would |
75 |
> recommend the latest mips-sources-2.6.9 ebuild instead of being thrown |
76 |
> into the fire right away with checking cvs out and tracking down the |
77 |
> right patches. You can't just use the standard kernel.org tarball for |
78 |
> mips machines really. You should also stop by our irc channel |
79 |
> (#gentoo-mips, irc.freenode.net) sometime if you haven't already. |
80 |
> |
81 |
> > |
82 |
> > Thanks again for your help. |
83 |
> > Regards- |
84 |
> > Andy |
85 |
> > |
86 |
> > |
87 |
> |
88 |
> |
89 |
> -- |
90 |
> gentoo-mips@g.o mailing list |
91 |
> |
92 |
> |
93 |
|
94 |
-- |
95 |
gentoo-mips@g.o mailing list |