cannot boot 2.5.67

cannot boot 2.5.67

[Pau Aliagas]

I have a rh9 installation, grub is properly configured, and when I select 
to boot a 2.5 kernel it does not even decompress it. It stops even before 
printing the kernel version.

What am I doing wrong?
Pau

Re: cannot boot 2.5.67

[Paul Rolland]

Got the same starting with 2.5.67...
I took the .config from the booting 2.5.66, made a 2.5.67 kernel,
and when booting, booh :-(

It was a RH8 base, Lilo... I'll try tonite to find out which option
is responsible of that...

Regards,
Paul

> I have a rh9 installation, grub is properly configured, and 
> when I select 
> to boot a 2.5 kernel it does not even decompress it. It stops 
> even before 
> printing the kernel version.
> 

Re: cannot boot 2.5.67

[Mads Christensen]

[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]

You have to get 
CONFIG_INPUT=y, CONFIG_VT=y and CONFIG_VT_CONSOLE=y
inorder for you to see anything =)

On tor, 2003-04-17 at 19:16, Paul Rolland wrote:
> Got the same starting with 2.5.67...
> I took the .config from the booting 2.5.66, made a 2.5.67 kernel,
> and when booting, booh :-(
> 
> It was a RH8 base, Lilo... I'll try tonite to find out which option
> is responsible of that...
> 
> Regards,
> Paul
> 
> > I have a rh9 installation, grub is properly configured, and 
> > when I select 
> > to boot a 2.5 kernel it does not even decompress it. It stops 
> > even before 
> > printing the kernel version.
> > 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
-- 
===================================================
| Mads F. Christensen     ||                      |
| Email:                  || mfc@krycek.org       |
| Webdesign Development   || www.krycek.org       |
===================================================


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: cannot boot 2.5.67

[Randy.Dunlap]

There was also a thread about 1 week ago that indicated that
if CONFIG_LOG_BUF_SHIFT=<some very large number here>,
the kernel won't boot and won't tell you why.

E.g., if someone sets CONFIG_LOG_BUF_SHIFT to a buffer size in bytes
(or KB) instead of a shift value, it causes a very large log buffer
declaration and that's about all she wrote.

~Randy


On 17 Apr 2003 19:46:34 +0200 Mads Christensen <mfc@krycek.org> wrote:

| You have to get 
| CONFIG_INPUT=y, CONFIG_VT=y and CONFIG_VT_CONSOLE=y
| inorder for you to see anything =)
| 
| On tor, 2003-04-17 at 19:16, Paul Rolland wrote:
| > Got the same starting with 2.5.67...
| > I took the .config from the booting 2.5.66, made a 2.5.67 kernel,
| > and when booting, booh :-(
| > 
| > It was a RH8 base, Lilo... I'll try tonite to find out which option
| > is responsible of that...
| > 
| > Regards,
| > Paul
| > 
| > > I have a rh9 installation, grub is properly configured, and 
| > > when I select 
| > > to boot a 2.5 kernel it does not even decompress it. It stops 
| > > even before 
| > > printing the kernel version.

Re: cannot boot 2.5.67

[Paul Rolland]

Hello,

> There was also a thread about 1 week ago that indicated that
> if CONFIG_LOG_BUF_SHIFT=<some very large number here>,
> the kernel won't boot and won't tell you why.
> 
Gosh !!! You are right.... How stupid I am !!!

I wanted to increase the log size I saw without thinking it
was a SHIFT... So I moved from 16 to 32, dreaming it was a move
from 16K to 32K...

Sh*t.... I read that on the list a few days ago, laught a lot, and
now I'm cooked ;-(

Regards,
Paul

Re: cannot boot 2.5.67

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 365 bytes --]

On Thu, 17 Apr 2003 19:46:34 +0200, Mads Christensen <mfc@krycek.org>  said:

> You have to get
> CONFIG_INPUT=y, CONFIG_VT=y and CONFIG_VT_CONSOLE=y
> inorder for you to see anything =)

OK.. Can we *please* fix the 2.5.68 Kconfig to default these 3 values
so we don't have to keep saying this?  The embedded people that want
'n' or 'm' can type it themselves. ;)

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: cannot boot 2.5.67

[Pau Aliagas]

On Thu, 17 Apr 2003 Valdis.Kletnieks@vt.edu wrote:

> On Thu, 17 Apr 2003 19:46:34 +0200, Mads Christensen <mfc@krycek.org>  said:
> 
> > You have to get
> > CONFIG_INPUT=y, CONFIG_VT=y and CONFIG_VT_CONSOLE=y
> > inorder for you to see anything =)
> 
> OK.. Can we *please* fix the 2.5.68 Kconfig to default these 3 values
> so we don't have to keep saying this?  The embedded people that want
> 'n' or 'm' can type it themselves. ;)

After fixing these parametres (make oldconfig did not set them), I still 
cannot boot 2.5.68. I've tried it with pci=noapci and also with apci=off, 
as the boot message suggestes.

I have a Dell Latitude Laptop with a Xircom Cardbus ethernet + modem card.
If I boot with the card inserted booting stops like this:
........
socket status = 30000006

Even SysRq does not work.

If I remove it I see:
socket status = 30000020
Intel PCIC probe: not found.
Unable to open initial console.
Kernel panic: No init found. Try passing init= option to kernel.

Here SysRq works.

I assume it must be a FAQ but cannot find it.

Pau

Re: cannot boot 2.5.67

[Valdis.Kletnieks]

[-- Attachment #1: Type: text/plain, Size: 387 bytes --]

On Tue, 22 Apr 2003 17:28:18 +0200, Pau Aliagas <linuxnow@newtral.org>  said:

> I have a Dell Latitude Laptop with a Xircom Cardbus ethernet + modem card.
> If I boot with the card inserted booting stops like this:
> ........
> socket status = 30000006

That's a known bug with pcmcia - Russel posted a fix which seems to be in:

  http://patches.arm.linux.org.uk/pcmcia-20030421.diff


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

Re: cannot boot 2.5.67

[Russell King]

On Tue, Apr 22, 2003 at 01:03:17PM -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 22 Apr 2003 17:28:18 +0200, Pau Aliagas <linuxnow@newtral.org>  said:
> 
> > I have a Dell Latitude Laptop with a Xircom Cardbus ethernet + modem card.
> > If I boot with the card inserted booting stops like this:
> > ........
> > socket status = 30000006
> 
> That's a known bug with pcmcia - Russel posted a fix which seems to be in:
> 
>   http://patches.arm.linux.org.uk/pcmcia-20030421.diff

Linus isn't particularly enthralled with the fix there, so I'm working on
a replacement version.  (Hell, I'm not that happy with that fix either,
but it does fix the problem.)

The replacement version is something I was planning on doing anyway, just
that its happening earlier than I really wanted it.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html

Re: cannot boot 2.5.67

[Bill Davidsen]

On Tue, 22 Apr 2003, Russell King wrote:

> Linus isn't particularly enthralled with the fix there, so I'm working on
> a replacement version.  (Hell, I'm not that happy with that fix either,
> but it does fix the problem.)
> 
> The replacement version is something I was planning on doing anyway, just
> that its happening earlier than I really wanted it.

How about an "ugly patches" repository? Some central place for patches
which solve problems but are not esthetically pleasing. There would be
multiple benefits; those who want a fix and don't care if it will go
forward can get their system working, the ugly patch will remain as a flag
that the problem needs to be properly fixed, and the content of the patch
may help someone else understand and beautify the solution or come up with
a whole new solution based on better understanding.

-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

Re: cannot boot 2.5.67

[Paul Rolland]

Hello,

> You have to get 
> CONFIG_INPUT=y, CONFIG_VT=y and CONFIG_VT_CONSOLE=y
> inorder for you to see anything =)
Yes, I guess I have that, as I'm using the .config from a 2.5.66
that was booting quite fine...

Anyhow, you are right, maybe that moving .config from a release to
another one is not 100% safe...

Regards,
Paul

Re: cannot boot 2.5.67

[Mads Christensen]

[-- Attachment #1: Type: text/plain, Size: 860 bytes --]

Common mistake i guess - but dude, never move old .config files to new
kernel dirs - patch the kernel, review the config (make menuconfig) and
recompile!

Regards

On tor, 2003-04-17 at 20:16, Paul Rolland wrote:
> Hello,
> 
> > You have to get 
> > CONFIG_INPUT=y, CONFIG_VT=y and CONFIG_VT_CONSOLE=y
> > inorder for you to see anything =)
> Yes, I guess I have that, as I'm using the .config from a 2.5.66
> that was booting quite fine...
> 
> Anyhow, you are right, maybe that moving .config from a release to
> another one is not 100% safe...
> 
> Regards,
> Paul
-- 
===================================================
| Mads F. Christensen     ||                      |
| Email:                  || mfc@krycek.org       |
| Webdesign Development   || www.krycek.org       |
===================================================


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: cannot boot 2.5.67

[Felipe Alfaro Solana]

On Thu, 2003-04-17 at 19:16, Paul Rolland wrote:
> Got the same starting with 2.5.67...
> I took the .config from the booting 2.5.66, made a 2.5.67 kernel,
> and when booting, booh :-(
> 
> It was a RH8 base, Lilo... I'll try tonite to find out which option
> is responsible of that...

I had to disable APIC support in order to be able to boot 2.5.67-mm2.
Don't know if this is your case, but I think it's worth trying :-)

-- 
Please AVOID sending me WORD, EXCEL or POWERPOINT attachments.
See http://www.fsf.org/philosophy/no-word-attachments.html
Linux Registered User #287198

Re: cannot boot 2.5.67

[John Bradford]

> I have a rh9 installation, grub is properly configured, and when I select 
> to boot a 2.5 kernel it does not even decompress it. It stops even before 
> printing the kernel version.
> 
> What am I doing wrong?

Are you sure that Grub is configured correctly?  Have you tried older
2.5 kernels until you find one that works?

John.