Annunci online

All that comes in the mind of an italian guy moved to california
4 aprile 2010
Technology: AROS: Kitty on a Stick ;)
Even if the last post is not finished yet, i start this because a very important thing happened on AROS: Starting from March 9 nighty, AROS can be finally installed and boot from USB Sticks!

I wrote a basic tutorial on Arosworld.org on how to install using a simple 2GB stick. Despite an initial problem due to the fact that the stick was partitioned in two and one of the partitions was hidden, after I wiped it with a windows program called Hard Disk Wipe Tool, that can be downloaded at this link , i finally as able to install AROS on the stick. Of course I tried the stick in all the computers available at home: my usual old laptop, my new Dell Vostro and, this time, also my wife's netbook, a MSI Wind u100.

The MSI Wind u100 proudly shows AROS OWB :)

The old buggy USB controller of my old ASUS does not allow to boot from USB stick, and is just the next USB fault in a long list (it ever was unable to see any of the sticks and USB devices I tried on AROS since the early Michal Schulz's usb.device tests); my Dell Vostro behaves a bit better, though it will boot forkm the stick if the "USB Legacy Driver" option in the BIOS is on - but that means no external keyboard and mouse: weird huh?

The best of the bunch was the netbook: called affectionately "blacky" from my wife, the wedding gift  MSI Wind u100 started from the stick with no glitches once I selected the stick from the startup menu; most of the hardware is supported: the wired RTL8168 network card and the HDAudio chip works nicely; of course the only missing components from this heavenly are the wireless chip and the external screen output (about the latter one got no clue whether can be selected as main from BIOS, need to check) but was nicely surprised from the performance.

Further tutorials and details can be found in this screen collection made by DizzyOfCRN, that also made a movie of its Samsung netbook booting from stick here, and more in general in this thread on AROS-exec.

Furthermore, paolone started a poll about how should he structure and what software should he put in a stick-friendly version of Icaros; the poll can be accessed from its blog.

I was a bit concerned about the lack of update from the AROS show lately, plus was waiting  for the promised interview to Matthias "Mazze" Rustler and i decided to check the pulse on Paul Beel aka Novaburstfor when the new updates might come out; pity that the answe was not encouraging.

In short, Novaburst said that slowly with the time he lost "the spark" on talking about AROS and that lately he is pursuing different interests; he also added that, at least for now, he will not update The AROS show, this means that (hopefully momentarily) one of most interesting insight voices from what happens behind the community doots got silent; i have a debt with the work of Paul; its periodical writings gave me motivation in checking first then support AROS and start my advocacy and, following, this blog. Hope to read you again soon, Paul.

Talking one moment about Mazze, he recently ported Jabberwocky, a well known Jabber Instant messenger App; in this moment the source was made sync with mainstream so that further versions willbe out even for AROS.

Last month I started some new little works for the AROS community giving my personal contribution in form of works: I created some wallpapers in several formats and uploaded it on the AROS Archives here, and I made a screencast where I show how to install the HDAudio drivers,how to test whether they are working correctly and how to file a bug report; the tutorial was made by me using AROS on Qemu, camstudio, Audacity and put together with premiere; it has been uploaded in Vimeo and can be seen here.

By the way, working at the tutorial was interesting and proposed me several technical problems; the first, obviously, was that since was working in an emulated environment could not propose the situation exactly as it should have shown; the second is that i realized that i need to write a script before to do a tutorial, else i end up having a lot of footage to discard (like 30 minutes for a 10 minute one) andis hard to make the voices match copying and pasting content; the last one was that I missed having a video capture software native on AROS (ok, we also miss audio and video editing software but lets take the problems one at the time) and, upon advice of Fabien Coeurjoly, i wrote to Ilkka "Itix" Lethoranta aobut making the source of its Screen Recording Program for MorphOS available; he gave its availability to provide the code and to help if somebody wants to port it; will let you know more details in the future.

The fact that now AROS is bootable from stick was for me the next critical mass signal, after the release of OWB and the completion of the Poseidon stack, that we can now aim at a largel userspace level; even though its "semi-perpetual pre-alpha stage" (sometimes the lack of smaller features to reach the alpha level frustrates me, i admit it, even though things look to progress fast), there is indeed an area where AROS can increase its user area thanks to its implicit advantages that can be already satisfied IMHO from the actual status (low memory footprint, fast start/shutdown and multitasking): that is the hobbyist area: think at HAM radio people, RC, Robotics, small hardware projects,etc. ; they already used Amigas in the past and have the feeling that the only reason they stopped using it was the death of commodore and the decaying of support; bringing them an Amiga-like OS in a x86 machine might be an ideal target.
Since is my intention to promote AROS for such uses, i started two threads, one in aros-exec and one in arosworld.org, where was trying to do some brainstorming; the thread on aros-exec has been deserted so far, while in the arosworld one got some responses from one of the users; gave me some insight of what might be (for me that am kinda out of the field) useful:

Amiga tinkerers should like Aros since its somewhat 3.1 compatible, with a cpu on steroids compared to 68k.
There were some articles that NASA (the ultimate tinkerers) were using Amigas at one time.
I wonder if they even know about Aros.
AFAIR most robotics people are using specific languages that may not be ported to Aros yet. At this time I think the main advantage of Aros for tinkerers is its quick boot and shut down.

Since another of my ideas was that there are some languages (rexx lua and, paying, hollywood) to provide a rapid application development, i asked whether there was way to interact with them using serial port (yup am still at that level), and that is its answer (longer but condensed):

I don't know much about Amilua or Rexx, but high level languages are not designed to explore the hardware. Instead they are an abstraction layer to shield you from the hardware. I'd be suprised if you find a way. Besides, are there any modern devices that really use the serial port anymore? It's really slow.

I forgot to mention bluetooth technology. With support for bluetooth an operating system can interact with many devices that are fun to tinker with.

Also do not overlook Midi. Many people have used Midi to sequence automated event timing, such as in light shows and animatronics.

As you can see, things are starting to look interesting (for me at least): it shows what might be needed for pepole to control devices through AROS: some good things might be bluetooth(not uspported) or MIDI (supported? got no idea, and Hitchhikr port of Bars and Pipes has been left unfinished for now); even HAM radio requires some kind of hardware, as said from a friend of mine  whose father is a HAM radio user and in the past used c64 and Amiga for its hobby; but he said that writing a serial driver should be trivial if somebody knows how to do it (neither me or him knows) -then, still talking aobut HAM radio, there is the lack of software problem; most amiga software found on Aminet is not open source or looks outdated, most linux software that can be ported resorts in GTK or QT (and the port is not trivial), not to mention licensing issues that might arise. Find new userbase and developers might help solve this part too: the most of the software around is ported mainly by three people: Mazze, Fishy_fis and Yannickescu; we also have occasional contributors that then disappears from the scene, like Masta1 that ported the main part of MAME engine but left the job unfinished (screen cannot be resized, missing GUI,etc). Others lack the time to contribute more, likg Craig "cjkiesau" Kiesau, that lately put in Aros Archives both the binary archive and the source code of ArosPDF so that the project can go on; as said in the past it is a port of xpdf on AROS and is GPL licensed.

Oliver "01i" Brunner is going on slow and steady in the Janus-UAE development, now pretty near the conclusion, though this did not satisfied the appetite of some hardcore Amiga Fans, as seen in this thread and also in this thread on Amigaworld.net: in short is the same old story; lots of people complaining about that AROS is not amiga os for brand/hardware/whatsoever else excuse, miss SMP, miss this miss that, does not integrate,etc.
Anyway, looks like another project, less ambitious and so far much less advanced, is trying to solve the problem of using legacy Amiga OS applications on AROS: will not be the final solution (since the idea is to have a local JIT 68k emulation that run the software and use AROS tools (graphics.library, gadtools.library, zune) to display the tool output - therefore is not going to work with those applications that use low-level Blitter and copper graphical output - but will indeed provide a glood level of backward compatibility for those workbench tools and applications.
The project is called Emumiga and has its own blog page, interesting styled in old amiga os3 with amigaguide-style links:) ; no downloads are possible yet but is possible to track down the progressing of the project; i sinteresting to know that the project use its own 68k emulation engine since the licensing of existing engines prevented the use in AROS.
So far it is possible to run some amiga shell commands and work is being done concerning the applications that use window gadgets; a proof of concept is the old Amiga clock; emumiga is now able to show it graphically on a window and use menus, even though at the moment the responsivity is still a bit slow due to the wrapping of AROS and old Amiga os graphical functions; expect things to improve in the future (the code is not even optimised yet).

Emumiga in action - the clock is the original Amiga OS one
(from Emumiga website)!

[the new commodore USA wedge - another AROS platform?]
Two weeks ago reading Slashdot I was greeted form this announcement of a supposed heir to the C64: turned out that a company called Commodore USA (that is actually a Florida based company that negotiated the brand name from Commodore Gaming and is actually the rights to the old logo of the twice dead Commodore) is about to sell a wedge shaped all-in-one PC (quite well known to the amiga crowd) as spiritual heir of the old "breadbox"; the machine in itself might be not that interesting - was origially called [name] and runs an Atom Processor together with Intel graphics card and Realtek HDAudio -  in theory all devices already supported by AROS, beside, obviously, wireless and SD card reader (a different beast from USB SD card). An interesting discussion arisen on the Developers mailing list; among the ideas it came out that, if Commodore USA would like to bundle AROS with their computers, it might be a good sign if they decide to support the development of AROS, either participating to the bounties, or contributing in development of missing drivers; plus is unresolved the legal implication of selling AROS in bundle with a system in the states, due to the different copyright laws; even though the most of old copyrights on the technologies are now are expired, is still a good idea being careful.

The article started with Neil Cafferkey work and end with another Neil Cafferkey work: the update and bug fixing of dopus is almost done, with also some help from Mazze and Sonic, especially in poointing some freezing bugs left; it is possible to follow the ongoing work in this aros-exec thread.
20 settembre 2009
Diary: Technologies: AROS: Fall colors over the MESA...
Want to begin this article with a sad note: at the end of August my actual company decided to downsize and to change its location, and am among the laid-offs, so right now most of my effort in front of this keyboard goes in finding a new job in order to pay the bills and keep the apartment; hope to be able to dedicate time to my advocacy back soon (that of course means i will be employed): please cross your fingers...

[update in november: still no job, will let you know of anything].

The month of October looks like has been a bit unfortunate for this blog: several times, trying to look at the content, i was greeten from a white page: by the way the black-out (or white-out i might say) affects almost all the ilcannocchiale blogs: it is the second time that I sent notification to the webmasters about this and lately am starting to consider to move this blog in a more affordable platform, maybe even self-hosted.

But let's go back and talk about AROS. Right now the most important news in AROS front are the following ones:

As said last august, Krysztof "Deadwood" Smiechowicz ported version 7.5 of MESA to AROS, for now in software rendering mode only. Latter in the month he also ported GLU,GLUT and added a revised version of SDL that can use MESA. The addition of MESA as library allowed  people, especially Matthias "Mazze" Ruster to port some new games on AROS; among the contributions we have now Block Out II, a 3d Tetris clone, Abuse, a well-known platform game, a first attempt to port Open Red Alert (that later has been removed due to a bad bug in the upstream that prevent enemy AI to operate), 3d Pool Billiard (running kinda slow due to the software renderer, kinda playable if you keep the window at stamp size).

September news is that Deadwood decided to accept the Gallium 3d Bounty. Krysztof already started to meddle with Gallium 3d at the time of the MESA port; he started getting decent results, as seen in this movie here on youtube. Following those embrionic attempts, Deadwood compiled a version of GLExcess that includes the nVidia Gallium driver and, compared to the old software-only compilation, the difference is really remarkable.

The latest additions to the already rich porting gallery of Deadwood are the OpenAL/alut/ogg/vorbis libraries. Those libraries, as said from deadwood itself in AROS-exec, are used in several open source games to provide the sound experience; their porting will open the door, together with the perfecitoning of MESA and Gallium, to porting some open source 3d games, such as Warzone 2100, AssaultCube and Cube2; and is known the plan to use the hardware acceleration together with Cairo in order to improve Wanderer responsivity and performance, but as far as i know is all still related to Deadwood progresses.

Talking about 3d and Mesa, last month the e-zine The Vague came out for AROS using the last MESA port of Deadwood; e-zines are well known to amiga users thanks to the demoscene; though i was hardly been a follower, remember an Italian one made called Infamia - at the time even Tadsince1995 used to cooperate with it as coder - and reminding the experience I started The Vague. The AROS version is in the same .lha archive with the Amiga PPC and Morphos version; once double clicked the icon a requester ask to start either in full-screen (for 640x480 resolution) or windowed (as i started it being in qemu at 800x600x24 resolution) ,whether to use sound effects and the music replay rate. Nikos posted a youtube video of The Vague running on AROS here.

The Vague volume 1 on AROS

Its been exciting to see some good demoscene art and nice music on AROS: i liked The Vague and am waiting for further numbers, and possibly even more e-zines and (why not?) some AROS demos too :)

Last August the code of the Poseidon stack finally got released under APL and built together with the nightly builds, making so complete the Poseidon Bounty, the so far most contributed bounty in AROS history. I tried the stack on my old laptop, where a known incompatibility with the USB SIS controller so far occured, with November 12 nightly the USB devices are still not recognized, by the way. Once i find a way to download OWB from the nightly (writing the URL and then use wget to download it seems a good one), will post the dump of PCItool from my old laptop in order to help the debug.

Icaros 1.1.6 is already on the works but, since this blog post is kinda late, let me talk about the version 1.1.5, that I tried both as iso image on qemu and as live CD on the old laptop. So grub worked fine, but when I tried to select my sis900 network card with DHCP form the network control panel and press the "use" button in order to test OWB performance, the system froze hard. Everytime.
In defense of the network control panel, by the way, doing the same with the latest nightly worked pretty fine, apart the missing OWB in the nightly - beside an OWB folder and a OWB icon in extras/networking - for don't know what reason; i understand that OWB cannot be added to the nightly both for weight and license issues but my personal suggestionis to replace the actual useless directory with a script that might download the latest version on RAM, for new installs.

And, talking about OWB, our Stanislaw Szymczyk , after a while where he took a pause from AROS development, released another new version of OWB. The Version 0.9.9 is downloadable, as usual, from the sand-labs web site and this time introduces, beside the usual flattening of several bugs, a loader, called StartOWB, that uses the artwork made by michaels and helps to track the long first loading (caused by the fontConfig cache building); beside that, now the main application menus are finally available with the right mouse button as for every other AROS application, giving it a standard interface. As far as i know,  the AREXX port in OWB is still missing, but hope Stanislaw will fix this soon.

The new OWB splash screen,designed by michaels

And then let's talk once more about the hidden hero of AROS, Matthias "mazze" Rustler: most of the software used on AROS has been ported by mazze, starting form several games (, then the unfinished port of Ignition Spreadsheet (that i still hope one day will be finished), LUA and its extensions, zulu and siAmiga - that are providing the base ground for several utilities, panels and give easy way for beginner programmers (like me) to produce something in AROS: the last fatigue of Mazze is the porting of Scout, the famous low-level tool for manage tasks under Amiga OS; undoubtely this might help to get rid of some annoying freeze of some shell windows or commodities, though for the well known lack of protected memory on Amiga OSes is still better to reboot the system as fast as possible.

Going further, any AROS user had to deal with the well known problems with our version of Dopus: despite being invaluable for file management, it has strong issues with advanced operations, such as extracting files, viewing pictures, even personalising buttons; this is due to the fact that this dopus port is pretty old (from 2000, if i remember clearly): now a new bounty  has been introduced in Power2people.org, for the port of the latest version of Dopus actually for Amiga OS-4 only; the bounty has been accepted by Neil Cafferkey and hope will improve this invaluable tool.

Last September once again Pianeta Amiga was held in Empoli, despite the fact that this year was held only at Saturday and the flow of people is really at its own minimum. This Year AROS was highly represented from, as usual Paolo Besser and, straight from the United Kingdom, Steven jones that brought its iMica platform. But here is the outcome according to Paolo Besser:

Thanks to Enrico Vitali and other well-known people of the italian Amiga community, the event has been amusing and interesting, but... well, I can't hide the mixture of bitter sweet feelings that left me only half happy. The good news, at least for Icaros Desktop, is that every visitor of the fair had the chance to see it in action, and most of them stopped at my table, asking for more informations or to see some demostration. I've also got many congratulations and many thanks for the effort, asking me for keeping up "the good job", but the bad news about all this, is that Pianeta Amiga this year lacked of visitors. Numbers had been fairly low (I've personally counted about 100 visitors) and the exhibitors themeselves were a tiny group that could comfortably stay in less space than the half area of the Palaesposizioni reserved to the event. "In the good old days you could see a crowd of people making long tails in front of the ticket booth - said Enrico while we were taking something to eat at noon - but today...", unluckily today's Pianeta Amiga loosely reflects the situation of the whole Amiga market. A tiny, fragile community which is hardly trying to keep its platform alive, even if the interest decreases a little more every year, and even if the whole IT market has completely forgotten the Amiga. So we have to thanks ACube, VirtualWorks, AmigaKit.com and everyone else that still persists, and spends money every year to organize a event which has just become a symbol, a tradition for the community, but which is practically perceived like a hobby, a nice meeting day with other people who share the same passion, even by people who professionally operate in the Amiga business.

It is sad for me to hear that despite the good news in the Amiga market (the SAM availability last year, the MorphOS on Mac Mini, icaros, iMica, Ares one, the settlement of the Amiga-Hyperion cause,etc., one of the last Amiga events is gone so unnoticed; despite my hopes, i think it is realistic that next year Pianeta Amiga might not be hold, if this is the trend; of course i expect thngs to change, but who knows....

Frustrations and disillusionment might hit even die-hard supporters. Many of the Aros-exec usual lurkers know Nikos: beside being a strong fan of the platform he is also one of the testers and one of the main bounty contributors ever, but in this thread he say that decided to take a leave from AROS, disappointed from the apparent lack of progresses, especially in the hardware acceleration section. By the way this happened just before Deadwood released its new MESA port and announced the start of the Gallium3d Bounty. The community reaction has been something you will rarely see in other open osurce community: almost everybody sent its own comment to nikos (including myself) expressing support; that convinced him to stay and luckilly for him, the new results on AROS seems to keep him busy...

Another AROS-friendly machine recently surfaced: provided by Pascal "Phoenixkonsole" Papara, the ARES one is an AMD Athlon x2 powered machine provided in a small tower case, bigger in size than Steven's Atom powered iMica; the graphic card is a performing nvidia GeForce 7200 with 256 megabytes DDR2  video RAM; phoenixconsole expects support from Gallium3d in order to enhance 3d capabilities; the machine hosts 1 gigabyte 800mhz DDR2 RAM (can be expanded up to 8 gigs) and can host up to four 5,25" devices; has a DVD/RW drive and a 3,5" floppy drive (foreseeing a catweasel support); it has a SoundBlaster Live as sound card and the network card is a Realtek RTL8139d that has a RTL8139 family chip and, quite interestingly, just today Hitchhikr released an rtl8169.device driver that in theory should support it. Paolone had occasion to test it with its Aspire One netbook and said it works nicely, adding another device to the netbook puzzle (right now still wireless and sound are unsupported on Aspire One).

Phoenixkonsole also plans to put in bundle with Ares One Icaros Desktop and a suite of programs for AROS including: the registered version of FryingPan and the incoming AROS Port of Cinnamon Writer: the latter one fills another software gap under AROS, presenting the first Word Processor available for the platform.

Cinnamon Writer is about to spice AROS

Now, if only Ignition port were finished we surely might had a decent AROS base office suite, together with MuiBase; the actual problem in finishing Ignition is non trivial. According to mazze itself in this thread on AROS-exec, it is depending from the actual order of "struct node":

Problem is that AROS has the elements of "struct Node" wrong on X86. This is supposed to be fixed with ABI V1. Unfortunately, Ignition makes *heavy* use of linked lists.
I could:
-continue porting when V1 ABI is released

-fixing list handling in Ignition which would be a lot of work which wouldn't be any longer necessary when V1 is out

-compiling me a version of AROS with the right order of Node. I could continue porting but I couldn't release the result until V1 is out.

All sucks somehow.

Further in the thread, phoenixconsole ask for how long might still take to Staf Verhaegen to finish the ABI 1.1; Staf's answer does not look too encouraging:

If I don't get help months to years from now. Problem seems to be that for being able to work on ABI V1 you need very good knowledge of AROS internals, Amiga OS internals and low level programming. It seems it is difficult to find people that have these capabilities and want to do it as their hobby activity. Additionally no glory or money can currently be gained by it.!!!

Staf is quite right: actually very few people have the required knowledge to help him in fix the ABI, and the actual AROS documentation, that should help provide that kind of knowledge is still kinda incomplete: lately even the quite famous "Linux lady" Carla Schroeder wrote two articles about the importance of documentation in Linux magazine: they can be found here and here, hoping to give guidelines for the actual coders, and maybe some non-coder to help therm in write it.

Simone "samo" Bevilacqua finally ported BOH to AROS, and it behave nicely even under qemu! BOH is one of the new generation commercial software available on the Amiga platforms (a little but, considered the platform diffusion, important avantguarde of a hopefully bigger production that include even Cinnamon Writer itself) and has been prepared for all the Amiga platforms so far: os 4, morphos and now even AROS. Despite some gitches with the sound due to the SDL libraries (and i expect things to imnprove thanks to the recent Deadwood work), the game runs fine even on qemu.


This coming year, God and Cash willing, is my intention to attend once more the Southern California Linux Expo in Los Angeles; will introduce the new features of AROS, the Icaros distribution, the new software and, if possible, even a native AROS box. Will write more about it soon; just mind that if somebody want to help me next february can get in touch with me at the email on the right side of the blog - the Get in Touch with Simone Bernacchia link, that I will repeat here, just remember to replace the sentences between square brackets.
28 maggio 2009
Diary:Technologies:AROS: the long and painful road to 1.0

I needed to take a leave a bit from the blog scene because my main laptop has been infected badly by a virus so that had to reformat and reinstall my OS: plus as bonus the backup DVDs i made looks like have errors and so i might be unable to recover my old AROS virtual disk: thank god i used to work my lua scripts on Windows and have copies on my SD card.

Anyway, despite Przemyslaw "Qus" Szczygielsky fixed its TCPPrefs control panel for AROS,this does not mean that I should abandon my lua Network config project: the problems withmy computer stopped me for a while but am ready to go on: at least i hope the related aros-exec thread should be a good didactic reference point for whoever want to start an Amilua project. Anyway, is my intention to post a tutorial when will have some free time.

I already set up the user interface: both mazze answers in the thread and some lua regular expression tutorials helped me in parsing the configuration files and do backup copies of it (in a bit rudimental way, parsing them and writing in a new renamed file via script), so what else is missing?
First of all I need to set the graphical frontend gadgets according to the preferences set in the files, including pre-set the cycle gadget on the actual network card; second i need to write the new configuration with the user set parameters. And last, if i would indulge in a little ego trip, a menu with a voice to show the about window ;) .

My Network Config Amilua app and part of the debug output window

Once done with this control panel, I would like to write sometihng to manage the Amistart calendar: one of the few widgets for Amistart, that also should be taken as example for those that want to write some more - is not happening yet, dont know why ;  another idea tingling my mind is to write a simple bookmark manager for OWB but so far there is no way to make OWB open a new address using the DOS getURL command and it is only possible to use the command OWB [url to launch] in order to open the program: it is not possible to use it with an open session: the old one needs to be closed first; i tested it personally.

At the begin of may I helped on write the AROS website status update: in this one I asserted that the latest months progresses brought AROS on the verge to be available for a daily usage; but in order to reach this goal still several obstacles need to be overcome, both on software availability, and on the system stability and affordability.

Neil Cafferkey still continues in its work on the ata.device; being this a critical piece of AROS, every time he or somebody else put its hand on it there is the risk something that used to work might break and, once it was fixed, might make it wonder how the hell was able to work before, but first let's get the facts: An updated ata.device patch has been provided with the Icaros desktop 1.1.1 upgrade; the upgrade has been temporarily removed by Paolo Besser itself due to the fact that on computers with southbridge board AMD SB600 or with similar architectures severe data corruption occured writing data in the disc partition; beside this, several users were greeted with a black screen and the red pointer with no further boot progress. For those the solution, was less drastic, citing from the Icaros website:

If you can't boot Icaros and the process stops after the red pointerappeared on the screen, please do as follow to fix the issue:

- turn on PC
- choose a resolution from Grub's menu but DON'T press Enter
- press 'E' instead
- move cursor after "ATA=32bit" and change it either to "ATA=nodma" or "ATA=nopci" (depending on what it works for you)
- press Ctrl+X to continue booting

Ifbooting has success open /boot/grub/grub2.cfg with the AROS editor,search for the "ATA=32bit" string and replace it with "ATA=nodma" or"ATA=nopci". You can do this easily, using the 'replace' option in the'search' menu of the editor.

At the same time, in answer to the problem exposed by Paolo Besser, Neil Cafferkey unveils what happened in the developer's mailing list:

I think I've found the cause of these problems: we don't set the
controller's timing registers.

My guess is that when DMA *did* work with older driver versions, it was
just a coincidence: ata.device re-set the drive mode that the BIOS had
already set, so there was no need to change the timing registers.

If we want to use a drive in a mode that the BIOS hasn't set, we need to
set the controller's timing registers to match that mode. Unfortunately,
there is no single standard for these timing registers. This is why Linux
for example has numerous PATA drivers: one for Intel, one for ATI, one for
Silicon Image etc.

This problem probably became more apparent because the new driver version
checks the cable report register bits to determine if the 80-wire cables
necessary for high-speed UDMA are present. My mistake was to assume that
all PCI controllers followed the T13 spec for these registers, but I
should have realised that that was unlikely given that the spec was only
published as recently as 2003. The T13 spec is implemented by Intel (and I
only have machines and emulators with Intel chipsets to test on), but I
suspect that T13 were actually following Intel's established design. Other
manufacturers have incompatible controller registers.

So on non-Intel controllers, the driver will incorrectly determine that
only 40-wire cables are installed, and downgrade the DMA mode from say
UDMA5 to UDMA2. Since the timing will then be wrong, data corruption is
likely to occur.

As a solution, I propose that, at least in the short term, ata.device does
not attempt to set a mode for any drive, but simply detects and uses the
mode already set by the BIOS. I hope that this will not lead to a
degradation in performace in most cases: in my small sample, BIOSes in
modern machines seem to set the best available mode for each drive by
default. I have this fix working locally. We already rely on the BIOS to
set addresses for PCI devices and enable bus-mastering, so this is just
one more thing.

In the longer term we could look at setting timings ourselves, but this
looks like a complicated procedure, and probably wouldn't give any
performance gain in most cases.

To help confirm my theory, I set a disk in one of my PCs to MDMA mode in
the BIOS instead of UDMA, and ata.device failed to access it after it put
the drive into UDMA2 mode. It had worked perfectly when the BIOS had set
it to UDMA (UDMA1 as it happens, but probably close enough not to cause

once the ata.device was fixed, the icaros update has been restored and is now available again for download.
In the Icaros Website Paolo expressed the fact that, despite he is doing the best to offer maximum stability and performance with the most recent system libraries and programs, sometimes it might happen that some components were not fully tested, also because is hard to test all hardware configurations, and especially for a small volunteered project as AROS; Paolo also assures how, despite the actual problem, the actual situation is even improved, considered that  now AROS boots even in machines where was unable to boot before, and that, thanks to the fact that the actual users and testers are aware of the beta nature of the syatem, damage was pretty limited; those kind of accidents might happen in open source projects- without mention Linux and its well known breakages - i might not say it happens often, but it happens.

Recently Neil also worked on fix other ata.device problems, including the fact that the device thought there were two DVD drive in case a SATA DVD drive was used. The change of the device enumeration system is also planned.

Neil is actually checking DHCP system, due to the fact that, once the shell command arostcp stop is given (or  a CTRL-C break command, as is called in unix environments), the DHCP stack become unresponsive and bring the CPU usage to 100%.

At the same time Michal Schulz worked on improve graphic performance on ATI Radeon - same graphic card that he as on Efika; bot Michal and Nik  "Kalamatee" Andrews  seen how the themes design (bad) implementation is among of the culprit in slowing down Wanderer performance - this in a fairly slow system such as Efika is much more perceived ; therefore Michal worked hard in accelerate several display redraw functions and the performance on ATI radeon both on x86 and PPC are improved quite dramatically.
Kalamatee, beside its actual task in improving and modernizing Wanderer, is considering whether to take the Graphic Subsystem Bounty, but so far nothing more is known about this topic.

And, at last, a rare happening in the actual Amiga oses landscape: with a joint effort, users from both Amiga OS, MorphOS and AROS partecipated to reach the $4000 goal set for the Poseidon USB Bounty: Thanks also to the initiative of a community member, that offered to double further received offers, the actual bounty quota is at $4170. Chris Hodges, the author of the Poseidon stack, started to work at the port - which source code will be open - and the stack will be released on the APL license; this will also allow other Amiga-like oses to port and to update extend and improve the stack code.

Outside the Amiga communities (with maybe the exception of the Haiku os) the bounty system concept might sound unknown - considered that in example a bigger open source player system such as Linux usually projects are founded from those government and commercial entities interested in their further development and maintenance; for smaller projects and communities, instead - such amiga-like oses -  the bounty system is the major (almost unique for AROS) source of funding. Therefore projects like this really are funded from the community and literally belong to the community, in a sort of similar fashion to the gothic cathedrals in the middle age.

And now a last word on the Aros-exec portal: last May 22nd the portal, after another virus exploit, was once again closed: now, after a week, the portal is finally back online using an updated and exploit -free xoops version and also a nice blue-metal new skin. I by the way remember that aros-exec is mainly a development-oriented portal; is my advice to point final users to the more user-oriented portal Arosworld.org. test



Feed RSS di questo 

blog Reader
Feed ATOM di questo 

blog Atom
Resta aggiornato con i feed.

blog letto 1 volte

Older Posts

Who links to me?
Get in touch with Simone Bernacchia