2.2.17 i386 boot-floppies uploading
Frank Copeland
>I think we want new kernel images (2.2.10) for amiga and atari anyway, how
>much time do we have till 2.2.18 (hint for debian-68k: I need the patches to
>go in, without them I can not built kernel-images)?
What are the known problems with the existing 2.2.10 image on the
Amiga? I don't see any bug reports in the BTS. I know I can't boot my
A2000 with 2.2.10, although since I didn't try very hard I haven't
submitted a bug myself.
Frank
--
To UNSUBSCRIBE, email to debian-68...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Christian T. Steigies
> On 4 Oct 2000 20:12:19 +1100, Christian T. Steigies <c...@debian.org> wrote:
>
> >I think we want new kernel images (2.2.10) for amiga and atari anyway, how
> >much time do we have till 2.2.18 (hint for debian-68k: I need the patches to
> >go in, without them I can not built kernel-images)?
>
> What are the known problems with the existing 2.2.10 image on the
> Amiga? I don't see any bug reports in the BTS. I know I can't boot my
> A2000 with 2.2.10, although since I didn't try very hard I haven't
> submitted a bug myself.
with that, some clgen user has to spend work on that, but the DEBUG messages
should be gone.
Christian.
Frank Copeland
>On Wed, Oct 04, 2000 at 11:50:37AM +0000, Frank Copeland wrote:
>> What are the known problems with the existing 2.2.10 image on the
>> Amiga? I don't see any bug reports in the BTS. I know I can't boot my
>> A2000 with 2.2.10, although since I didn't try very hard I haven't
>> submitted a bug myself.
>The clgen driver is "ugly". Got the patch now. It does not work any better
>with that, some clgen user has to spend work on that, but the DEBUG messages
>should be gone.
OK, I'll make another effort in the next day or so and see if I can at
least get some sort of error message out of it. At the moment it seems
to be failing in amiboot or very early in the kernel load.
Frank
Frank Copeland
>On 4 Oct 2000 23:00:14 +1100, Christian T. Steigies <c...@debian.org> wrote:
>>On Wed, Oct 04, 2000 at 11:50:37AM +0000, Frank Copeland wrote:
>
>>> What are the known problems with the existing 2.2.10 image on the
>>> Amiga? I don't see any bug reports in the BTS. I know I can't boot my
>>> A2000 with 2.2.10, although since I didn't try very hard I haven't
>>> submitted a bug myself.
>
>>The clgen driver is "ugly". Got the patch now. It does not work any better
>>with that, some clgen user has to spend work on that, but the DEBUG messages
>>should be gone.
>
>OK, I'll make another effort in the next day or so and see if I can at
>least get some sort of error message out of it. At the moment it seems
>to be failing in amiboot or very early in the kernel load.
It turned out to be the 'video=' argument passed to the kernel by
amiboot. The format changed between 2.0.x and 2.2.x, and the argument
now appears to be mandatory for 2.2.x, which it wasn't for 2.0.x.
Christian T. Steigies
> It turned out to be the 'video=' argument passed to the kernel by
> amiboot. The format changed between 2.0.x and 2.2.x, and the argument
> now appears to be mandatory for 2.2.x, which it wasn't for 2.0.x.
correctly. Maybe clgen.txt is out of date, but nobody is working on the
driver. Since documentation is always written later than the code, I
wouldn't expect anything else.
You are welcome to update driver and/or documentation. Pleae send patches to
linux...@lists.linux-m68k.org
Christian.
Frank Copeland
>On Thu, Oct 05, 2000 at 01:47:35PM +0000, Frank Copeland wrote:
>> It turned out to be the 'video=' argument passed to the kernel by
>> amiboot. The format changed between 2.0.x and 2.2.x, and the argument
>> now appears to be mandatory for 2.2.x, which it wasn't for 2.0.x.
>It is set in the StartInstall_clgen script, and I am pretty sure it is set
>correctly. Maybe clgen.txt is out of date, but nobody is working on the
>driver.
In this case it doesn't have anything to do with clgen. The box is an
ECS A2000 with no graphics card, and the driver involved is amifb.
StartInstall_* doesn't come into the picture either, as I upgraded a
slink system to potato using apt-get. Unless I missed some message
during the upgrade (quite possible), there was no warning that the new
kernel required a change to the amiboot commandline. This is clearly a
documentation issue, but I'm not entirely sure what documentation needs
fixing.
Frank
Lars Hecking
> It is set in the StartInstall_clgen script, and I am pretty sure it is set
> correctly. Maybe clgen.txt is out of date, but nobody is working on the
> driver.
That is not fully correct.
The clgen driver as written by Frank Neumann and present in the 2.0.x
and 2.2.x series of kernels is not being maintained anymore.
Jeff Garzik has written a new clgen driver which was incorporated into
the 2.3.x kernels at some stage (I _think_ 2.3.12; it was definitely
between 2.3.6 and 2.3.22), and this driver does not yet seem to work
with Amiga clgen boards.
The latest version of the driver I have access to is in the 2.4.0-test-pre7
kernel (yes, it's really called that), but the compile dies at an early
stage on my machine. (I _could_ try this version of the driver with
something like 2.3.47, which IIRC does compile).
It might be worth backporting (and fixing :) Jeff's driver to 2.2.x.
Christian T. Steigies
> In this case it doesn't have anything to do with clgen. The box is an
> ECS A2000 with no graphics card, and the driver involved is amifb.
> StartInstall_* doesn't come into the picture either, as I upgraded a
> slink system to potato using apt-get. Unless I missed some message
> during the upgrade (quite possible), there was no warning that the new
> kernel required a change to the amiboot commandline. This is clearly a
> documentation issue, but I'm not entirely sure what documentation needs
> fixing.
for first time installations so far. I thought everybody using slink and
upgrading his kernel could be bothered to read the kernel source, it is
documented there, but of course not very obviously.
Care to write an upgrading document we could use?
The main problem is, m68k does not use lilo, so you have to copy vmlinux to
your amiga partition. And you probably have to adjust your startup script,
since you give the kernel-image a different name (it has a different name
when you install the kernel-image packge and if you build it yourself, you
should give it a different name, since you want to save your old, working
kernel). So it can not be changed automatically and I do not know of a way
how to include some warning into the kernel-image package other than in a
README, which probably most users will miss...
Anyhow, write something and we will find a place for it.
Christian
Frank Copeland
>Oh, right, we do not have an m68k-upgrading document it seems. We only cared
>for first time installations so far.
Actually the release notes cover upgrading quite well, pity I read them
*after* working out the problem...
>I thought everybody using slink and upgrading his kernel could be
>bothered to read the kernel source, it is documented there, but of
>course not very obviously.
I think its a bit much to require someone to consult the kernel source
just to upgrade a binary package, but perhaps you meant kernel-doc-*.
>Care to write an upgrading document we could use?
I think a small addition to the release notes should be enough. In
section 3.1 there's a bulleted list of issues for upgrading the kernel.
Maybe something like this could be added:
"Some kernel options have changed, and incorrect options may prevent
your system from booting. See your kernel's
Documentation/m68k/kernel-options.txt file for more information."
Frank