You are not logged in.
Pages: 1
Iv downloaded the kernel 2.6.0 package and compiled it without any problems copied over the system.map26 and bzimage to the boot directory iselect the new 2.6.0 entry i put in lilo.. the kernel boots says alot of stuff then the kernel says
"Unable to open an initial console" and then reboots 3 seconds after
iv tried many settings and get the same problem.. what can be causing this?
-bolero
Offline
add to /etc/fstab:
none /dev/pts devpts defaults 0 0
and enjoy 2.6.0
The impossible missions are the only ones which succeed.
Offline
i did do that, it is in my fstab.. i know kernel 2.6.0 works because iv used the Arch package of 2.6.0 but i want to compile it myself and it gives me that error
-bolero
Offline
ok, didnt know that ...
if you have access to your / , have a look at
/var/log/kernel for more info --- maybe there can be found more detailed info what happens
The impossible missions are the only ones which succeed.
Offline
Yeah, search for that exact error message. People had exactly the same problem using the test kernels. You didn't compile in something you should have.
I have discovered that all of mans unhappiness derives from only one source, not being able to sit quietly in a room
- Blaise Pascal
Offline
theres nothing in my logs that says anything about kernel 2.6.0 kernel only 2.4 entries are in
im not sure what i should enable then?
-bolero
Offline
theres nothing in my logs that says anything about kernel 2.6.0 kernel only 2.4 entries are in
im not sure what i should enable then?-bolero
there is no difference in 2.6.0 and 2.4.x entries ... they look the same ... having a look at the time-stamp, you can say, what entries are from what boot/kernel ... have a look at these .. and the last ones from a boot with your 2.6.0 should be informative for solving your problem
The impossible missions are the only ones which succeed.
Offline
well theres a ton of crap in this file.. i know when to start looking timewise on Jan 2 as thats when i tried but every new entry from then on is the same from a 2.4 boot, i know im overlooking somthing. But in the boot, it doesnt even get to starting anything.. when the kernel spits out all that random crap at the begining it imediatly sais cannot initiate console, doesnt get into loading any services or mounthing the file system or anything
-bolero
Offline
you forgot to compile in devfs support and for it to come up at boot.
as xentac said there ARE plenty of 2.6 kernel posts that have this error and the solution listed.
well then, i appologise
Offline
Pages: 1