Amiga.org
Amiga computer related discussion => General chat about Amiga topics => Topic started by: MarkTime on November 29, 2003, 03:39:18 AM
-
OK, I burned the AROS ISO image on a CD, and it ran so slow, that I decided to try the linux hosted version.
So....I am running Red Hat's Fedora Core, release one on my Athlon 2000+.
I downloaded the binaries and they blow up....then I downloaded the sources, and after compiling....that blows up.
List chip memory: Attr=00000703 from 0xbed37030 to 0xbf537008 Free=8343368
Chunk bed420c0 Size 8343368
List rom memory: Attr=00000400 from 0x0804a7c0 to 0x080cac8c Free=0
GURU Meditation b501 0000
Deadend/*unknown*/*unknown*
Task: 0xbed377c8 (Boot Task)
Aborted
-
*KABOOM*
-
I can see that the antiterror squads are gonna be hunting AROS down now...
-
MarkTime wrote:
it ran so slow
I never used the Linux-hosted version, so I'm afraid I'm of little help there... However, it runs slow on an Athlon 2000+? It's pretty snappy here on my P3-550 and flies on my Athlon 1800+... Strange.
:-?
-
What date was the ISO?
Dammy
-
by that_punk_guy on 2003/11/28 23:21:33
I never used the Linux-hosted version, so I'm afraid I'm of little help there... However, it runs slow on an Athlon 2000+? It's pretty snappy here on my P3-550 and flies on my Athlon 1800+... Strange.
Unless it's an old ISO, it maybe hardware issues. I've got my Dell Latitude 233MHz MX fired up and it's running hosted AROS (from the other night's CVS) on Fedora and it's running as smooth and pretty responsive (considering the limited RAM available after Fedora, that's impressive).
Dammy
-
OK, I burned the AROS ISO image on a CD, and it ran so slow, that I decided to try the linux hosted version.
Slow as in loading slow? If so, it must be because of our pretty buggish and limited ide.device, if not, then i'm surprised, as native runs faster than hosted for me, even in VMWare :-o.
So....I am running Red Hat's Fedora Core, release one on my Athlon 2000+.
What's the version of the libc that distribution got?
I downloaded the binaries and they blow up....then I downloaded the sources, and after compiling....that blows up.
List chip memory: Attr=00000703 from 0xbed37030 to 0xbf537008 Free=8343368
Chunk bed420c0 Size 8343368
List rom memory: Attr=00000400 from 0x0804a7c0 to 0x080cac8c Free=0
GURU Meditation b501 0000
Deadend/*unknown*/*unknown*
Task: 0xbed377c8 (Boot Task)
Aborted
Looks like something couldn't be properly allocated... the guru doesn't explain much, though, which is puzzling. I'll try to find out more.
-
Karlos wrote:
I can see that the antiterror squads are gonna be hunting AROS down now...
Don't say that or AROS might have to be reclassified under the Dagerous weapons act 1997 :-D
-
This GURU seems to come from input.device or
unixio.hidd (I think, having scanned the exe for
this alert numbers). First try running AROS with
some more memory:
./aros -m 64
Gives it 64 MByte of RAM.
If this doesn't help recompile the source with debugging
enabled:
make clean
./configure --enable-debug
make
Then run AROS through the GNU debugger "gdb":
cd bin/linux-i386/AROS
gdb aros
Inside gdb enter:
run -m 64
Then when it crashes do a backtrace by typing
bt
What output does the backtrace give?
-
Ah, and if after the "run" in gdb it gets interrupted through a (mysterious. no idea where coming from)
SIGTRAP type "cont" to make it continue from where
it was interrupted.
BTW: At what depth is your X11 Server running?
-
Don't say that or AROS might have to be reclassified under the Dagerous weapons act 1997
That would please tony blair it would be the first ones he had found. :-D
-
amigamad wrote:
Don't say that or AROS might have to be reclassified under the Dagerous weapons act 1997
That would please tony blair it would be the first ones he had found. :-D
:lol:
-
Matt, imagine it! Nationwide publicity for AROS!
:-D
-
that_punk_guy wrote:
Matt, imagine it! Nationwide publicity for AROS!
:-D
Well, you know what they say... No publicity is Bad publicity... (http://www.hotornot.com/r/?eid=GLRZEMB&key=NPJ)
-
First, I should explain my remarks, though I didn't mean them in a provocative way.
I first tried running AROS on a P4 1.6 running the native version, but inside Virtual PC 5.2 (last connectix version)
That was slow in terms of gui responsiveness...windows were slow to redraw.
As for comparing it to the hosted version, I cannot.
Now I'm on a different machine, and its an Athlon 2000+ 384MB running the fedora core.
It has a ps/2 keyboard and a usb mouse.
I will try the suggestions and see if I can track down the problem further.
thanks for the help.
-
oh I just thought of something, this machine has no floppy drive.
I remember on the other machine it was constantly polling the floppy and going buzz buzz buzz.
two questions...can someone stop that buzzing, and would you consider making it the default? it has something to do with amigaos compatibility? make sure its equally annoying?
:-)
anyway, this machine has no floppy...is a floppy drive a requirement?
thanks,
Robert
-
I grabbed a floppy drive from an old machine, and to my amazement, it has some kind of proprietary connector...it seems to have 2 less pins than the floppy drive connector on my Athlon 2000+
amazing...well thats about as much effort as I'm putting into it. Thanks for the help, but I'm done.
I think the aros team has done wonderful work, and of course I found it interesting, but I don't spend hour after hour not being productive trying to track down problems with alpha software....its just not my thing.
Keep up the good work, can't wait to hear about a tcp/ip stack and other advancements I am sure are coming.
--Robert
-
MarkTime wrote:
I grabbed a floppy drive from an old machine, and to my amazement, it has some kind of proprietary connector...it seems to have 2 less pins than the floppy drive connector on my Athlon 2000+
amazing...well thats about as much effort as I'm putting into it. Thanks for the help, but I'm done.
I think the aros team has done wonderful work, and of course I found it interesting, but I don't spend hour after hour not being productive trying to track down problems with alpha software....its just not my thing.
Keep up the good work, can't wait to hear about a tcp/ip stack and other advancements I am sure are coming.
--Robert
You don't actually need a really Floppy drive, just make sure the Floppy drive is switched on in the BIOS :-)
The trackdisk.device looks for the presence of the Floppy Drive controler rather than an actual drive.