Debian2.2 and clgen on Amiga3000
Michael Schaffner
(I'm new to this list, but not new to linux-m68k in general.)
I've recently installed Debian-m68k (2.2) on my Amiga3000.
I was running Debian 2.0 before (i installed that a long time
ago and didn't use it that much; after switching from SuSE
to Debian on my PC, i remembered the Debian-Linux on my Amiga
again :-))
So far, the system works ok, but i've big problems using the
fbdev device (Alt-Tab and/or X). My Gfx-Card is a PicassoIV,
so i need the clgen-driver (so my problems are more clgen-
than fbdevrelated)
1.) The whole driver seems to run in some kind of "debug-mode",
printing messages on the screen each time x is started, the
console is changed via Alt-Tab and worst : every time the
screen blanks or unblanks :-(
The system is nearly unusable -> while running the installation,
the screen blanks,unblanks,blanks,... After coming home a few
hours later you can't even read the messages from the installation
you have to answer, only debug-messages from clgen.
How can i switch this off ?
2.) In my old setup i could set the resolution used by the driver
in text- and gfx-mode using something like
"video=clgen:monitorcap:55;90;31;64,mode:high"
in the amiboot-start-line
Clgen in the Kernel from Debian 2.2 seems to ignore all this :-(
The "official" amiboot-line uses "video=clgen". I tried to change
this without any visible effects. Changing the textmode with fbset
works, though.
3.) Using the mouse under X hangs quite often for half a second or
even longer (maybe this is related to the debug-messages ?!)
What am I doing wrong ? Is there nobody with a clgen-gfx-card
using debian anymore ?
Bye..
Michael
--
To UNSUBSCRIBE, email to debian-68...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Lars Hecking
> 1.) The whole driver seems to run in some kind of "debug-mode",
> printing messages on the screen each time x is started, the
> console is changed via Alt-Tab and worst : every time the
> screen blanks or unblanks :-(
> The system is nearly unusable -> while running the installation,
> the screen blanks,unblanks,blanks,... After coming home a few
> hours later you can't even read the messages from the installation
> you have to answer, only debug-messages from clgen.
> How can i switch this off ?
Check the list archives. Michael Fedrowitz posted a kernel patch for
this a few weeks ago. I installed a minimum system, compiled a new
kernel, and reinstalled using the new kernel.
> 2.) In my old setup i could set the resolution used by the driver
> in text- and gfx-mode using something like
> "video=clgen:monitorcap:55;90;31;64,mode:high"
> in the amiboot-start-line
> Clgen in the Kernel from Debian 2.2 seems to ignore all this :-(
> The "official" amiboot-line uses "video=clgen". I tried to change
> this without any visible effects. Changing the textmode with fbset
> works, though.
Not sure about this. I'm starting Debian from the bootblock installed
via lilo from RedHat/m68k ...
> 3.) Using the mouse under X hangs quite often for half a second or
> even longer (maybe this is related to the debug-messages ?!)
Same here (A3000/040, clgen). I don't think this is related to the
debug messages, I'm still getting it with the patched kernel. I also
don't think this is a kernel problem, as the problem does not occur
under RedHat, running the same kernel.
> What am I doing wrong ? Is there nobody with a clgen-gfx-card
> using debian anymore ?
Christian T. Steigies
On Sun, Sep 24, 2000 at 09:00:38PM +0200, Michael Schaffner wrote:
> 1.) The whole driver seems to run in some kind of "debug-mode",
> printing messages on the screen each time x is started, the
> console is changed via Alt-Tab and worst : every time the
> screen blanks or unblanks :-(
Right, thats how the "official" m68k kernel source comes. Maybe we should
build a new kernel-image with this patch applied?
> The system is nearly unusable -> while running the installation,
> the screen blanks,unblanks,blanks,... After coming home a few
> hours later you can't even read the messages from the installation
> you have to answer, only debug-messages from clgen.
> How can i switch this off ?
Huh, unusable? Blanking? I did not experience that, if you do not switch the
console and don't idle too much, nothing like that should happen. But I
agree, its an annoying feature.
> 2.) In my old setup i could set the resolution used by the driver
> in text- and gfx-mode using something like
> "video=clgen:monitorcap:55;90;31;64,mode:high"
> in the amiboot-start-line
> Clgen in the Kernel from Debian 2.2 seems to ignore all this :-(
> The "official" amiboot-line uses "video=clgen". I tried to change
> this without any visible effects. Changing the textmode with fbset
> works, though.
Selecting a different mode is no longer supported, thats a "feature" of the
2.2 kernel. If you want a different resolution, you have to hardcode it in
the source (one of the Andreas'es, mind to send a patch that I might add to
the potato FAQ?).
> 3.) Using the mouse under X hangs quite often for half a second or
> even longer (maybe this is related to the debug-messages ?!)
How fast, aehm, slow is your system? I found the speed ok on an A3000 where
I tested the installation.
> What am I doing wrong ? Is there nobody with a clgen-gfx-card
> using debian anymore ?
Quite a few clgen users seem to use debian, but none of them has given
anything back to debian-m68k or linux-m68k it seems. You have the card, you
have the source, you have a problem. Write a patch and send it to linux-m68k
(not talking about hardcoding another resolution, but about fixing the
driver so that you have the same functionality as you had with 2.0.36...)
BTW, its not a debian problem, its a linux-m68k problem.
Christian
--
http://www.debian.org/~cts/debian-m68k/potato
Lars Hecking
> 3.) Using the mouse under X hangs quite often for half a second or
> even longer (maybe this is related to the debug-messages ?!)
Are you running gpm by any chance?
Michael Schaffner
> > 3.) Using the mouse under X hangs quite often for half a second or
> > even longer (maybe this is related to the debug-messages ?!)
>
> I had exactly the same problem - until last night :)
>
> Are you running gpm by any chance?
You're right; after stopping gpm, the problem is gone.
Thanks and bye..
Michael
Michael Schaffner
> > 1.) The whole driver seems to run in some kind of "debug-mode",
> > printing messages on the screen each time x is started, the
> > console is changed via Alt-Tab and worst : every time the
> > screen blanks or unblanks :-(
> Right, thats how the "official" m68k kernel source comes. Maybe we should
> build a new kernel-image with this patch applied?
Is there a way to get a kernel with this patch without compiling
it myself ?
> > The system is nearly unusable -> while running the installation,
> > the screen blanks,unblanks,blanks,... After coming home a few
> > hours later you can't even read the messages from the installation
> > you have to answer, only debug-messages from clgen.
> > How can i switch this off ?
> Huh, unusable? Blanking? I did not experience that, if you do not switch the
> console and don't idle too much, nothing like that should happen. But I
> agree, its an annoying feature.
You select 120 MB in dselect -> you go to work, come home 10 hours later :-)
-> the installation asked you a question 5 hours before you come to your
machine -> the screen is full of clgen-debug-messages -> you have no way
to know what the question was -> nearly unusable.
> > 3.) Using the mouse under X hangs quite often for half a second or
> > even longer (maybe this is related to the debug-messages ?!)
> How fast, aehm, slow is your system? I found the speed ok on an A3000 where
> I tested the installation.
68060/50 Mhz. The problem is gpm-related -> see other posting.
Bye..
Lars Hecking
> > Are you running gpm by any chance?
>
> You're right; after stopping gpm, the problem is gone.
check now, I'm logged in from NBSD :) option which causes gpm to copy
all events to some /dev device.
Christian T. Steigies
> Is there a way to get a kernel with this patch without compiling
> it myself ?
> 68060/50 Mhz.
Do you think somebody has a faster machine?
> You select 120 MB in dselect -> you go to work, come home 10 hours later :-)
> -> the installation asked you a question 5 hours before you come to your
> machine -> the screen is full of clgen-debug-messages -> you have no way
> to know what the question was -> nearly unusable.
these days. With slink and before apt was available, you could achieve those
times, but with apt everything is lightning fast!
Anyway, thanks to Lars, I now have the mac 2.2.16 kernel source and the clgen
dedebug patch. I will try to build an amiga kernel image with that.
It would be good if some atari (and mac and vme (Nick?)) users could try to
build that kernel as well and test it.
If it all works out, I would like to use this kernel for the next
boot-flopies version. For this we probably need a kernel-patch package, but
I see no 2.2.16 kernel-source... Nick?
Christian
Ingo Juergensmann
[...]
> dedebug patch. I will try to build an amiga kernel image with that.
> It would be good if some atari (and mac and vme (Nick?)) users could try to
> build that kernel as well and test it.
Uhm... I'm running on 2.2.17 m68k from Mac CVS. Works fine beside of the
clgen debug infos and paper out messages from kernel:
/var/log/kern.log.0:Sep 30 06:45:03 arrakis kernel: lp0: paper-out
/var/log/kern.log.0:Oct 1 06:45:00 arrakis kernel: lp0: paper-out
/var/log/kern.log.0:Oct 1 07:07:20 arrakis kernel: lp0: paper-out
Maybe it's due to MFC-III compiled in driver...
> If it all works out, I would like to use this kernel for the next
> boot-flopies version. For this we probably need a kernel-patch package, but
> I see no 2.2.16 kernel-source... Nick?
Well, sadly I lost my big hard drive with my maling list archive and Mac CVS
2.2.17 kernel and would appreciate to have a recent m68k kernel to test it,
especially to get that paper out messages gone...
Ciao...
Ingo
Christian T. Steigies
> /var/log/kern.log.0:Sep 30 06:45:03 arrakis kernel: lp0: paper-out
> /var/log/kern.log.0:Oct 1 06:45:00 arrakis kernel: lp0: paper-out
> /var/log/kern.log.0:Oct 1 07:07:20 arrakis kernel: lp0: paper-out
>
> Maybe it's due to MFC-III compiled in driver...
nervous... why don't you feed your printer with some paper?
> Well, sadly I lost my big hard drive with my maling list archive and Mac CVS
> 2.2.17 kernel and would appreciate to have a recent m68k kernel to test it,
> especially to get that paper out messages gone...
2.2.17? I checked it out today and only got 2.2.16?
I will try to build 2.2.16 images for amiga with the clgen patch (no debug
messages). Somebody with a clgen board has to test it, you are volunteering?
Good. Some Atari and Mac testers around? Well, maybe you roll your own kernel
and just send the config file here so I can build the kernel-image.
Christian
Ingo Juergensmann
> On Wed, Oct 04, 2000 at 02:50:56PM +0200, Ingo Juergensmann wrote:
> > /var/log/kern.log.0:Sep 30 06:45:03 arrakis kernel: lp0: paper-out
> > /var/log/kern.log.0:Oct 1 06:45:00 arrakis kernel: lp0: paper-out
> > /var/log/kern.log.0:Oct 1 07:07:20 arrakis kernel: lp0: paper-out
> > Maybe it's due to MFC-III compiled in driver...
> paper-out? thats harmless, I once had on fire!, that really made me
> nervous... why don't you feed your printer with some paper?
There is simply no printer attached to it... neither to standard parallel
port nor to MFC-III Port nor to AriadneI or AriadneII port... (does
AriadneII still has par port? Dunno...) I have only one printer and this is
attached to my x86 linux box... but this printer is fed with paper
indeed.... ;))
> > Well, sadly I lost my big hard drive with my maling list archive and Mac CVS
> > 2.2.17 kernel and would appreciate to have a recent m68k kernel to test it,
> > especially to get that paper out messages gone...
> 2.2.17? I checked it out today and only got 2.2.16?
Huh... you're right... sorry... may be I'm getting to old or CVS told me
2.2.17 cos it shall be sometimes a 2.2.17 but is still 2.2.16... dunno...
arrakis:/home/ij/irclogs# uname -a
Linux arrakis 2.2.16 #1 Mon Sep 11 15:16:55 CEST 2000 m68k unknown
> I will try to build 2.2.16 images for amiga with the clgen patch (no debug
> messages). Somebody with a clgen board has to test it, you are volunteering?
Sure.... send me kernel tarball via dcc on IRC or put it to a httpd and give
me URL to download... ;-)
Ciao...
Ingo (aka ij on #debian.de@IRCnet)
Ray Knight
>
> On Wed, Oct 04, 2000 at 02:50:56PM +0200, Ingo Juergensmann wrote:
> > /var/log/kern.log.0:Sep 30 06:45:03 arrakis kernel: lp0: paper-out
> > /var/log/kern.log.0:Oct 1 06:45:00 arrakis kernel: lp0: paper-out
> > /var/log/kern.log.0:Oct 1 07:07:20 arrakis kernel: lp0: paper-out
> >
> > Maybe it's due to MFC-III compiled in driver...
> paper-out? thats harmless, I once had on fire!, that really made me
> nervous... why don't you feed your printer with some paper?
>
> > 2.2.17 kernel and would appreciate to have a recent m68k kernel to test it,
> > especially to get that paper out messages gone...
> 2.2.17? I checked it out today and only got 2.2.16?
>
> messages). Somebody with a clgen board has to test it, you are volunteering?
> and just send the config file here so I can build the kernel-image.
>
> Christian
>
I'm the one responsible for applying the updates to get the Mac CVS to
2.2.16. I have been running the 2.2.16 Mac CVS kernel on a Quadra 950
and a IIfx since early August with no problems. Attached is the config
file I have been using.
--
Ray Knight
aud...@speakeasy.org
Christian T. Steigies
> If it all works out, I would like to use this kernel for the next
> boot-flopies version. For this we probably need a kernel-patch package, but
> I see no 2.2.16 kernel-source... Nick?
Ok everybody, please reply to the list and not in PM. I got a few more
problems right now and I can not handle all the single emails.
Seems there are enough volunteers to test the kernel-images, I will tell you
when its ready and where it will be. Just one thing, I will not fix any
other drivers, you know where the source is, fix it yourself.
2.2.16 built fine last night (with gcc2.9.5!) except for the CyberStorm MK3
driver, a header file is missing. It is running fine, no problems so far,
lets see if it survives until tonight. I do expect problems with the GVP11
driver...
I will build a kernel-image tonight. If Nick is listening, can you test this
version on vme? Can you build a vme kernel-image? Can you create the patch
package? I never did that, I don't quite know against what I should build
the patch, there is no 2.2.16 source in debian.
Id love to hear from mac users, please everybody try to build and test this
version on mac. Its a bit difficult to have two different kernel versions in
the boot-floppies for mac...
Christian
--
http://www.debian.org/~cts/debian-m68k/potato
Nick Holgate
> If it all works out, I would like to use this kernel for the next
> boot-flopies version. For this we probably need a kernel-patch
> package, but I see no 2.2.16 kernel-source... Nick?
I have built an experimental kernel-patch package which can be found at:
http://auric.debian.org/~holgate/kernel-patch-2.2.16-m68k_2.2.16-1_all.deb
It includes a rather large patch to update the kernel source tree from
2.2.13 (the latest kernel source available in potato) to an i386 native
2.2.16 tree.
It also includes:
o a diff of mac68k CVS as of this morning
o Richard Zidlicky's 040 bus error patch
o a couple of VME fixes that are missing from mac68k CVS
o gcc272 Makefile patch
o MVME147 support
Missing, is the clgen debug info patch, if someone would send it to me I'd
be grateful... Christian? :)
As I've already said this package is experimental, and there are problems
with the approach of patching the kernel source from one version to another.
Firstly it make the package very large. Secondly it will break make-kpkg if
it is configured to automatically apply the patches (it will try to find
patches that match the source tree version and fail). Perhaps we should
discuss the strategy for getting the 2.2.16 kernel-source and images into
R1.
Finally, I have not even attempted to compile a kernel using this patch set
so be warned.
Nick
----------------------------------------------------------------
Nick Holgate <hol...@debian.org>
GPG key from public servers : Key ID FD9C18AF
Fingerprint = 9DCA EDEA D5C5 57DA 23F3 1A2B 2273 5645 FD9C 18AF
Christian T. Steigies
>
> I have built an experimental kernel-patch package which can be found at:
>
> http://auric.debian.org/~holgate/kernel-patch-2.2.16-m68k_2.2.16-1_all.deb
> Missing, is the clgen debug info patch, if someone would send it to me I'd
> be grateful... Christian? :)
> patches that match the source tree version and fail). Perhaps we should
> discuss the strategy for getting the 2.2.16 kernel-source and images into
> R1.
Adam>either upload or ask Xu to upload such a package.
> Finally, I have not even attempted to compile a kernel using this patch set
> so be warned.
I am building (from yesterdays CVS) on kullervo for amiga, it takes much
longer than I expected... I will try with your patch package at home. I am
also interested if my amiga survided the day running this kernel.
Christian.
Nick Holgate
> Missing, is the clgen debug info patch, if someone would send it to me I'd
> be grateful... Christian? :)
Thanks Lars and Christian, I've now added the clgen patch.
I've also updated the patch package to patch up a 2.2.15 source tree
instead of 2.2.13, which makes the package somewhat smaller.
I've now also cross compiled a BVME6000 kernel using these patches and
every thing seems to run OK.
The new kernel-patch package can be found at:
http://auric.debian.org/~holgate/kernel-patch-2.2.16-m68k_2.2.16-3_all.deb
Nick
----------------------------------------------------------------
Nick Holgate <hol...@debian.org>
GPG key from public servers : Key ID FD9C18AF
Fingerprint = 9DCA EDEA D5C5 57DA 23F3 1A2B 2273 5645 FD9C 18AF
Christian T. Steigies
>
> The new kernel-patch package can be found at:
>
> http://auric.debian.org/~holgate/kernel-patch-2.2.16-m68k_2.2.16-3_all.deb
with config files and build logs) at
http://non-us.debian.org/~cts/
Yet another webpage, somebody is standing on the other lines...
Atari build did not complete, there was a problem with the ATI Mach64
driver, I removed it from the config (config.atari2), build is not yet
finished. Nick, can you replace the config files in the patch package by
these ones (unless atari+mac users complain)?
All others, please test them on all available hardware, the amiga image is
working very nicely on an A2k, b2060, cv3d, gvpii, ariadne2, catweasel
machine. Please report your findings here, we want to build new
boot-floppies with them asap.
Shall I build *vme images as well?
Christian
Nick Holgate
> kernel-patch-2.2.16-m68k_2.2.16-3_all.deb
> Nick, can you replace the config files in the patch package by
> these ones (unless atari+mac users complain)?
Sure.
> Shall I build *vme images as well?
No, I've built them, they can be found at the usual place:
http://auric.debian.org/~holgate/
Also there is a small boot-floppies patch to add support for the MVME147.
I have checked these changes into CVS this morning. I wass going to leave
this until Woody, but if we are building new boot-floppies and new kernels
I thought I might as well do it now.
Nick
----------------------------------------------------------------
Nick Holgate <hol...@debian.org>
GPG key from public servers : Key ID FD9C18AF
Fingerprint = 9DCA EDEA D5C5 57DA 23F3 1A2B 2273 5645 FD9C 18AF
--
Christian T. Steigies
> http://auric.debian.org/~holgate/
TCP connection to 'auric.debian.org' failed: Operation now in progress.
Ok, Ill copy it via pandora...
> Also there is a small boot-floppies patch to add support for the MVME147.
> I have checked these changes into CVS this morning. I wass going to leave
> this until Woody, but if we are building new boot-floppies and new kernels
> I thought I might as well do it now.
since there is a bug. But before building, I want to hear success reports
from other people. Especially from mac, since I do not intend to use 2.2.10
and 2.2.16, Adam said it would require another subarchitecture. Too much
work for me, but if somebody else jumps in...
Christian