can't boot 2.4.0-t9

can't boot 2.4.0-t9

[Giuliano Pochini]

I can't boot kernel 2.4.0-test9 because it fails configuration
of my scsi cards (resource collisions). The hack of removing the
"return -EINVAL" I used in test7 doesn't work anymore.  Anyway,
I'm just curious to know why there are not such problems in 2.2.
How can I dump what it writes during boot ?  It's too fast, I
haven't the time to copy it by hand...

Another little thing: compilation fails because CONFIG_ADB_KEYBOARD
doesn't exist anymore, so I replaced it with CONFIG_PPC in
devices/input/keybdev.c. I also had to compile with CONFIG_PMAC_PBOOK
enabled, otherwise it complains the lack of the function
mediabay.c:media_bay_set_ide_infos() in ide-pmac.c

(blue-G3/350, 2 Adaptec 2930U in busses 2 and 3)

Bye.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: can't boot 2.4.0-t9

[Topi Kanerva]

On Sun, 8 Oct 2000, Giuliano Pochini wrote:

>I can't boot kernel 2.4.0-test9 because it fails configuration
>of my scsi cards (resource collisions). The hack of removing the
>"return -EINVAL" I used in test7 doesn't work anymore.  Anyway,
>I'm just curious to know why there are not such problems in 2.2.

is this the plain 2.4.0-test9 or linuxcare devel version?
If I were you, I'd try to backport the test7 scsi code to make
the hack work again.
I don't know about the drivers/scsi stuff, because I have a pismo
(and hence no scsi), but for sure none of the 2.4.0-testx kernels
have worked for me in terms of X: if I start X (4.0.1c), the
lcd screen goes black, or then just completely wild.

Can anyone else with a pismo confirm this?

-topi


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: can't boot 2.4.0-t9

[Michel Dänzer]

Topi Kanerva wrote:

> I don't know about the drivers/scsi stuff, because I have a pismo
> (and hence no scsi), but for sure none of the 2.4.0-testx kernels
> have worked for me in terms of X: if I start X (4.0.1c), the
> lcd screen goes black, or then just completely wild.
>
> Can anyone else with a pismo confirm this?

Not me. It has always worked fine for me. But then I use the other distro (see
.sig ;)


Michel


--
Earthling Michel Dänzer (MrCooper)  \  CS student and free software enthusiast
Debian GNU/Linux (powerpc,i386) user \   member of XFree86 and the DRI project

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: can't boot 2.4.0-t9

[Benjamin Herrenschmidt]

>
>is this the plain 2.4.0-test9 or linuxcare devel version?
>If I were you, I'd try to backport the test7 scsi code to make
>the hack work again.
>I don't know about the drivers/scsi stuff, because I have a pismo
>(and hence no scsi), but for sure none of the 2.4.0-testx kernels
>have worked for me in terms of X: if I start X (4.0.1c), the
>lcd screen goes black, or then just completely wild.
>
>Can anyone else with a pismo confirm this?

For the SCSI resources problem, I have to check is the main tree is up-
to-date with the latest PPC fixes. You may want to try with the PPC
bitkeeper tree.

For the X 4 vs. 2.4 issue, I've been biten by this for a long time (on a
Pismo too and on a G4) until I figured out that the X server dies when
looking up font path. I had a broken font path in my /etc/X11/XF86Config,
removing it fixed the problem. (It's the last one in the list, it used to
give an error with older X servers).

Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: can't boot 2.4.0-t9

[Giuliano Pochini]

>>I can't boot kernel 2.4.0-test9 because it fails configuration
>>of my scsi cards (resource collisions). The hack of removing the
>>"return -EINVAL" I used in test7 doesn't work anymore.  Anyway,
>>I'm just curious to know why there are not such problems in 2.2.
>
> is this the plain 2.4.0-test9 or linuxcare devel version?

Plain version, d/l fron kernel.org

> If I were you, I'd try to backport the test7 scsi code to make
> the hack work again.

A function (I don't remember which) have a different number of
parameters and it doe't compile. I'll try again this night.


Bye.
    Giuliano Pochini ->)|(<- Shiny Corporation {AS6665} ->)|(<-


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: can't boot 2.4.0-t9

[Giuliano Pochini]

>>is this the plain 2.4.0-test9 or linuxcare devel version?
>>If I were you, I'd try to backport the test7 scsi code to make
>>the hack work again.
>>I don't know about the drivers/scsi stuff, because I have a pismo
>>(and hence no scsi), but for sure none of the 2.4.0-testx kernels
>>have worked for me in terms of X: if I start X (4.0.1c), the
>>lcd screen goes black, or then just completely wild.
>>
>>Can anyone else with a pismo confirm this?
>
> For the SCSI resources problem, I have to check is the main tree is up-
> to-date with the latest PPC fixes. You may want to try with the PPC
> bitkeeper tree.

Can I download only the arch/ppc tree ?

> For the X 4 vs. 2.4 issue, I've been biten by this for a long time (on a
> Pismo too and on a G4) until I figured out that the X server dies when
> looking up font path.

4.0.0 works fine here (test7).


Bye.
    Giuliano Pochini ->)|(<- Shiny Corporation {AS6665} ->)|(<-


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: can't boot 2.4.0-t9

[Michael Schmitz]

> > For the X 4 vs. 2.4 issue, I've been biten by this for a long time (on a
> > Pismo too and on a G4) until I figured out that the X server dies when
> > looking up font path.
>
> 4.0.0 works fine here (test7).

4.0.1 runs fine here on -test9, slightly patched to restore adbmouse
function.

BTW: has the cputemp diff been posted for 2.4 already? If not I'd be happy
to provide it. There's been some discussion on what CPU clock to use if we
can't get the clock from OF - is there a max. CPU clock known for such
machines?

	Michael


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: can't boot 2.4.0-t9

[Michel Lanners]

On   9 Oct, this message from Michael Schmitz echoed through cyberspace:
> BTW: has the cputemp diff been posted for 2.4 already? If not I'd be happy
> to provide it.

See if it's on sourceforge. If not, put it there.

> There's been some discussion on what CPU clock to use if we
> can't get the clock from OF - is there a max. CPU clock known for such
> machines?

Getting the right clock is absolutely non-critical, only the code blocks
the CPU longer than necessary if the clock is assumed too high.

Other than that, it might be a good idea to just hardcode something like
600 MHz in there for now... We can always change that later if somebody
comes up with a CPU clock detection that always works...

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: can't boot 2.4.0-t9

[Giuliano Pochini]

Giuliano Pochini wrote:
>
> I can't boot kernel 2.4.0-test9 because it fails configuration
> of my scsi cards (resource collisions). The hack of removing the
> "return -EINVAL" I used in test7 doesn't work anymore.  Anyway,
> I'm just curious to know why there are not such problems in 2.2.
> How can I dump what it writes during boot ?  It's too fast, I
> haven't the time to copy it by hand...

Ok, I've just hacked pci.c from test7 to compile in test9. It still
doesn't work.

Bye.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/