>> It would be good to get all the patches into the 2.6 kernel. I'm not
>> sure 2.4 works with the etch installer any more.
> it does not. I've tried that because the 2.6 does not recognize my ATAPI
> CD-ROM. But the 2.4 didn't work at all with etch.
2.6 does not work here (kernel panic) but in t
Stephen R Marenka píše v Po 26. 03. 2007 v 13:42 -0500:
> It would be good to get all the patches into the 2.6 kernel. I'm not
> sure 2.4 works with the etch installer any more.
it does not. I've tried that because the 2.6 does not recognize my ATAPI
CD-ROM. But the 2.4 didn't work at all with et
On Mon, Mar 26, 2007 at 11:28:07AM +0200, Michael Schmitz wrote:
> ... forgot to mention this ...
>
> > so I had to use Didier Mequignon's ataboot.prg
>
> The same I use, for sure. (plain TOS!)
So is the debian version missing something or does it work too? I was
under the impression that we had
... forgot to mention this ...
> so I had to use Didier Mequignon's ataboot.prg
The same I use, for sure. (plain TOS!)
> 2) kernel 2.2 from the above image crashes after a while with:
> kernel panic: Can't process interrupt vector 196 interrupt handler - not
> syncing
>
> 3) kernel 2.4 from the
Hi there,
[ \me resurfacing from the backlog of a week's worth of unread mails ]
> First I tried compressed then uncompressed. Same results. kernel 2.2
> works but doesn't recognize EtherNEC oder EtherNAT. 2.4 and 2.6 freeze
> after refreshing the screen (switching screen from TOS to Linux).
2.2
> Is the kernel uncompressed?
First I tried compressed then uncompressed. Same results. kernel 2.2
works but doesn't recognize EtherNEC oder EtherNAT. 2.4 and 2.6 freeze
after refreshing the screen (switching screen from TOS to Linux).
Regards,
Frank
--
To UNSUBSCRIBE, email to [EMAIL PROTEC
On Tue, Mar 20, 2007 at 03:49:15PM +0100, Frank Szymanski wrote:
> > Have you tried starting it from plain TOS? It usually works for me there.
>
> Yes. I did. :-) Now.
>
> Although you are losing long filenames with TOS.
>
> Anyway, bootstra.prg starts but doesn't show the correct amount of
> TT
> 1) bootstra.prg crashes at startup with the following message box (MiNT):
> PROCESS "bootstra" KILLED:
> MEMORY VIOLATION. (PID 092)
> Any ideas?
> Or how about the built-in boot loader of the CT60? Just copy your boot
> config whatever it is called into the root of C: and select
On Tue, Mar 20, 2007 at 03:07:25PM +0100, Petr Stehlik wrote:
> Frank Szymanski wrote:
> >>>1) bootstra.prg crashes at startup with the following message box (MiNT):
> >>>PROCESS "bootstra" KILLED:
> >>>MEMORY VIOLATION. (PID 092)
> >>>Any ideas?
> >>change the memory protection level in the bootst
> Have you tried starting it from plain TOS? It usually works for me there.
Yes. I did. :-) Now.
Although you are losing long filenames with TOS.
Anyway, bootstra.prg starts but doesn't show the correct amount of
TT-RAM 510.51050 MB instead of 512 MB.
After loading the kernel (no matter which o
Frank Szymanski wrote:
1) bootstra.prg crashes at startup with the following message box (MiNT):
PROCESS "bootstra" KILLED:
MEMORY VIOLATION. (PID 092)
Any ideas?
change the memory protection level in the bootstra.prg's GEMDOS header
to Super (IIRC).
Unfortunately it doesn't help.
Tried every
>> 1) bootstra.prg crashes at startup with the following message box (MiNT):
>> PROCESS "bootstra" KILLED:
>> MEMORY VIOLATION. (PID 092)
>> Any ideas?
> change the memory protection level in the bootstra.prg's GEMDOS header
> to Super (IIRC).
Unfortunately it doesn't help.
Tried every possible c
Frank Szymanski wrote:
1) bootstra.prg crashes at startup with the following message box (MiNT):
PROCESS "bootstra" KILLED:
MEMORY VIOLATION. (PID 092)
Any ideas?
change the memory protection level in the bootstra.prg's GEMDOS header
to Super (IIRC).
Petr
--
To UNSUBSCRIBE, email to [E
Hi!
Have some days off and tried a net-install on my ct60/EtherNAT Falcon.
Got the images from:
http://www.debian.org/releases/stable/debian-installer/
These are the results:
==
1) bootstra.prg crashes at startup with the following message box (MiNT):
PROCESS "bootstra" KI
> I wonder if we've burned out our 060 chips? My Falcon keeps crashing a
> lot now.
Tracked it down to a flaky disk power supply (I think). We'll see ...
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> Unfortunately the Falcon is continously crashing now, maybe I have to clock
> it down. But it seems I have also lost the software to slow down the
> clock... so I found xcontrol and put xcontrol.acc in C:, now I get a
> segfault during boot. Yeah, how do I get around that? Does zcontrol work any
> Unfortunately the Falcon is continously crashing now, maybe I have to clock
> it down. But it seems I have also lost the software to slow down the
> clock... so I found xcontrol and put xcontrol.acc in C:, now I get a
> segfault during boot. Yeah, how do I get around that? Does zcontrol work any
> > > Yes, SCSI is disabled, but if you say it works, I can try. Thee is not
> > > much
> >
> > Please do - if you have all my patches it should work (i.e. recover from
> > timeout/reset cycles).
>
> I've built one with SCSI drivers, it will appear as:
>
> http://people.debian.org/~cts/debian-m68k
Christian T. Steigies píše v Po 05. 02. 2007 v 21:12 +0100:
> so I found xcontrol and put xcontrol.acc in C:, now I get a
> segfault during boot. Yeah, how do I get around that? Does zcontrol work any
> better?
zControl and XControl are basically the same. Without any CPX modules
they must not cr
On Mon, Feb 05, 2007 at 05:59:10PM +0100, Michael Schmitz wrote:
> > > > Why not build a custom 2.6 kernel with scsi drivers built-in? The
> > >
> > > Because this would be the first real test of Atari SCSI in 2.6, I guess.
> > > Should be fine for reading the CD though (depending on how prone the
> > > Why not build a custom 2.6 kernel with scsi drivers built-in? The
> >
> > Because this would be the first real test of Atari SCSI in 2.6, I guess.
> > Should be fine for reading the CD though (depending on how prone the
> > Falcon is to DMA clock problems; make sure to boot in ST-High
> > res
On Mon, Feb 05, 2007 at 01:30:59PM +0100, Michael Schmitz wrote:
> > > I am trying to install etch on my falcon/ct60, after I lost my woody
> > > installation. There are no atari kernels on the etch CD from january, so I
> > > tried with the latest 2.6 kernel. This kernel has many drivers built in,
Michael Schmitz wrote:
I am trying to install etch on my falcon/ct60, after I lost my woody
installation. There are no atari kernels on the etch CD from january, so I
tried with the latest 2.6 kernel. This kernel has many drivers built in, the
installation starts fine, but it does not have SCSI d
> > I am trying to install etch on my falcon/ct60, after I lost my woody
> > installation. There are no atari kernels on the etch CD from january, so I
> > tried with the latest 2.6 kernel. This kernel has many drivers built in, the
> > installation starts fine, but it does not have SCSI drivers, s
On Sun, Feb 04, 2007 at 08:25:17PM +0100, Christian T. Steigies wrote:
> Hi,
> I am trying to install etch on my falcon/ct60, after I lost my woody
> installation. There are no atari kernels on the etch CD from january, so I
> tried with the latest 2.6 kernel. This kernel has many drivers built in,
Hi,
I am trying to install etch on my falcon/ct60, after I lost my woody
installation. There are no atari kernels on the etch CD from january, so I
tried with the latest 2.6 kernel. This kernel has many drivers built in, the
installation starts fine, but it does not have SCSI drivers, so I can not
26 matches
Mail list logo
