1 |
Francisco Ares wrote: |
2 |
> 2012/10/13 Dale <rdalek1967@×××××.com <mailto:rdalek1967@×××××.com>> |
3 |
> |
4 |
> Francisco Ares wrote: |
5 |
>> |
6 |
>> 2012/10/12 Dale <rdalek1967@×××××.com <mailto:rdalek1967@×××××.com>> |
7 |
>> |
8 |
>> Francisco Ares wrote: |
9 |
>> > |
10 |
>> > |
11 |
>> > Thanks for your reply, Dale. |
12 |
>> > |
13 |
>> > Yes, everything works as expected when using the old kernel. |
14 |
>> > |
15 |
>> > I decided to re-emerge some base libraries, and nothing |
16 |
>> worked, until |
17 |
>> > I remembered to re-emerge udev. After the build, it |
18 |
>> announced two |
19 |
>> > wrong lines in the new kernel "config" file: |
20 |
>> > |
21 |
>> > CONFIG_SYSFS_DEPRECATED=y |
22 |
>> > CONFIG_SYSFS_DEPRECATED_V2=y |
23 |
>> > |
24 |
>> > After correcting them and building the kernel again, now |
25 |
>> everything is |
26 |
>> > back to normal. |
27 |
>> > |
28 |
>> > Thanks again |
29 |
>> > Francisco |
30 |
>> > |
31 |
>> > |
32 |
>> > -- |
33 |
>> > "If you have an apple and I have an apple and we exchange |
34 |
>> apples then |
35 |
>> > you and I will still each have one apple. But if you have |
36 |
>> an idea and |
37 |
>> > I have one idea and we exchange these ideas, then each of |
38 |
>> us will have |
39 |
>> > two ideas." - George Bernard Shaw |
40 |
>> |
41 |
>> |
42 |
>> Do you use oldconfig or build each one from scratch? I use |
43 |
>> oldconfig so |
44 |
>> that I at least have what I know works. It's just a matter |
45 |
>> of if I need |
46 |
>> anything new enabled. Some claim oldconfig shouldn't be used |
47 |
>> but I have |
48 |
>> only had it to fail once in the last 10 years or so. Most |
49 |
>> everyone I |
50 |
>> know of uses oldconfig. |
51 |
>> |
52 |
>> Glad you got it going tho. |
53 |
>> |
54 |
>> Dale |
55 |
>> |
56 |
>> :-) :-) |
57 |
>> |
58 |
>> -- |
59 |
>> I am only responsible for what I said ... Not for what you |
60 |
>> understood or how you interpreted my words! |
61 |
>> |
62 |
>> |
63 |
>> |
64 |
>> |
65 |
>> I normally also use oldconfig. I think there might be a reason |
66 |
>> for it to be around. But this time I didn't, because the old |
67 |
>> kernel was version 2.6.39 and I thought oldconfig would mess |
68 |
>> things up more than help on the new 3.4.9. Don't know how right |
69 |
>> or wrong is this assumption, though. |
70 |
>> |
71 |
>> I just was lazy to upgrade the kernel, as it takes an hour or so |
72 |
>> to check most of menucofig. |
73 |
>> |
74 |
>> Francisco |
75 |
>> |
76 |
> |
77 |
> I would have tried it but that is a LOT of updates. It may be |
78 |
> faster to start from scratch in that case. I know a few years ago |
79 |
> there was some changes that kept oldconfig from working as it |
80 |
> should. That was the only time it failed me but I do upgrade more |
81 |
> often to avoid this sort of thing. I try to upgrade every couple |
82 |
> months. Now if I have long uptimes, I may not actually ever use |
83 |
> that kernel but I have a config file to copy over that is a bit |
84 |
> more up to date. |
85 |
> |
86 |
> I would suggest printing or something the output of the |
87 |
> following: lspci -k That tells you what you need for your |
88 |
> hardware, that is of course from a kernel where all your hardware |
89 |
> works. There may be some specific things for certain software |
90 |
> that is needed but at least you can boot up and have a system to |
91 |
> work with. I usually leave the rest to defaults unless I am sure |
92 |
> there is something I don't need. |
93 |
> |
94 |
> Glad you got it sorted out and working tho. |
95 |
> |
96 |
> Dale |
97 |
> |
98 |
> :-) :-) |
99 |
> |
100 |
> -- |
101 |
> I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |
102 |
> |
103 |
> |
104 |
> |
105 |
> Hi, Dale |
106 |
> |
107 |
> As my old kernel is from the 2.6 series and the new is from the 3.4, I |
108 |
> decided to do a "menuconfig" from scratch. I do use "lspci" and also I |
109 |
> always build the kernel allowing "/proc/config.gz", so it is easy to |
110 |
> get exactly what is working, although I keep my own bacup copies of |
111 |
> ".config", for future references. When I am building a kernel, I use |
112 |
> to open the latest ".config" in a separate console, for reference. |
113 |
> That has kept me of forgetting plenty of details. |
114 |
> |
115 |
> Thanks |
116 |
> Francisco |
117 |
> -- |
118 |
> "If you have an apple and I have an apple and we exchange apples then |
119 |
> you and I will still each have one apple. But if you have an idea and |
120 |
> I have one idea and we exchange these ideas, then each of us will have |
121 |
> two ideas." - George Bernard Shaw |
122 |
|
123 |
|
124 |
I can understand why. There would have been a huge number of new |
125 |
options to check on. Doing it from scratch with menuconfig could have |
126 |
been just as fast or maybe even faster. May have been worth trying but |
127 |
may have ended up with more issues. |
128 |
|
129 |
Using lspci -k does help. Someone posted about the -k option and I made |
130 |
a note of it since it gives the name of the driver. If we know the name |
131 |
of the driver, we know what to search for and enable. Makes life easier. |
132 |
|
133 |
The one time oldconfig failed, I had old kernel in one screen and new |
134 |
kernel in another and was going section by section. Sounds like what |
135 |
you have done so we ended up doing this the same way. It is sometimes |
136 |
the best way and we don't miss the important stuff. ;-) |
137 |
|
138 |
All things considered, turned out pretty good. Built a new kernel from |
139 |
scratch, had only one minor issue. Good day all around. lol |
140 |
|
141 |
Dale |
142 |
|
143 |
:-) :-) |
144 |
|
145 |
-- |
146 |
I am only responsible for what I said ... Not for what you understood or how you interpreted my words! |