Amiga.org

Amiga computer related discussion => General chat about Amiga topics => Topic started by: ssolie on October 24, 2017, 07:30:05 PM

Title: AmiWest 2017 clarifications
Post by: ssolie on October 24, 2017, 07:30:05 PM
AmiWest 2017 is over and it was one crazy time!

There were the usual announcements and many things were said.

If you want clarifications on anything, please post your questions here and I'll do my best to answer and/or clarify things.

Just don't guess what I meant. Ask instead.
Title: Re: AmiWest 2017 clarifications
Post by: kamelito on October 24, 2017, 07:41:13 PM
Quote from: ssolie;832128
AmiWest 2017 is over and it was one crazy time!

There were the usual announcements and many things were said.

If you want clarifications on anything, please post your questions here and I'll do my best to answer and/or clarify things.

Just don't guess what I meant. Ask instead.

1) Hi Steve, You were on the Amiwest agenda -Next steps for AmigaOS-or something similar, why was it remove and what are the next steps?

2) Any update on the wiki front? like updating it further as there's still AmigaOS 2.x/3.x stuff or new tutorials from AmigaFuture?

Thanks Kamelito
Title: Re: AmiWest 2017 clarifications
Post by: Nagasakee on October 24, 2017, 07:49:04 PM
Steve, could you please update us as to the status of LibreOffice?  My understanding is that this subject was not a part of the Q&A.
Title: Re: AmiWest 2017 clarifications
Post by: ssolie on October 24, 2017, 08:06:44 PM
Quote from: kamelito;832129
1) Hi Steve, You were on the Amiwest agenda -Next steps for AmigaOS-or something similar, why was it remove and what are the next steps?

The original agenda was prepared without my input so there was a miscommunication.

Quote
2) Any update on the wiki front? like updating it further as there's still AmigaOS 2.x/3.x stuff or new tutorials from AmigaFuture?

The wiki is always being updated. October 18 was the last edit. We have 38 editors and each of them contributes however they wish. That is how a wiki works.

We only cover AmigaOS 4.0 and up as stated on the front page. I don't see any need to go backwards. The community can open up their own wiki if need be.

The next batch of AmigaFuture tutorials should be released in December. For some reason, AF wouldn't allow us to publish them until then.
Title: Re: AmiWest 2017 clarifications
Post by: ssolie on October 24, 2017, 08:07:40 PM
Quote from: Nagasakee;832130
Steve, could you please update us as to the status of LibreOffice?  My understanding is that this subject was not a part of the Q&A.

LibreOffice is still a work in progress and there is a beta test team working on it. That is all I know. I'm not on the beta testing team myself.
Title: Re: AmiWest 2017 clarifications
Post by: kamelito on October 24, 2017, 08:26:56 PM
@Steve
1) Since the new Radeon driver (3.3) removed the 256MB limitations is there work ongoing on the Amiga Libraries to take advantage of all that memory and also to take advantage of the power of the GPU?

2) is there improvement done on the  code optimization targetting PPC?
Kamelito
Title: Re: AmiWest 2017 clarifications
Post by: ssolie on October 24, 2017, 09:03:55 PM
Quote from: kamelito;832135
@Steve
1) Since the new Radeon driver (3.3) removed the 256MB limitations is there work ongoing on the Amiga Libraries to take advantage of all that memory and also to take advantage of the power of the GPU?

The plan is to take advantage of the GPU in as many places as possible in graphics.library. Keep in mind that means you have to transfer data into VRAM and let the GPU loose on it so this is not a simple thing to accomplish. Legacy software still uses the CPU to draw into bitmaps in regular RAM and then transfer that to the VRAM for display.

Quote
2) is there improvement done on the  code optimization targetting PPC?

The first step is updating the compiler tool chain. Our focus right now is on getting the A1222 to market and that target requires an updated tool chain as well.
Title: Re: AmiWest 2017 clarifications
Post by: BCP on October 24, 2017, 09:19:23 PM
Steve, I did'nt hear any mention of Timberwolf at AmiWest.  Since its been open-sourced has there been any effort to update it?

- BCP
Title: Re: AmiWest 2017 clarifications
Post by: kamelito on October 24, 2017, 09:25:41 PM
@Steve%&$#?@!
Is it possible to have something like fat binaries produced by the toolchain like what existed on the Next that target FPU and SPE  on one executable?
Kamelito
Title: Re: AmiWest 2017 clarifications
Post by: Rob on October 24, 2017, 09:42:49 PM
Quote from: BCP;832138
Steve, I did'nt hear any mention of Timberwolf at AmiWest.  Since its been open-sourced has there been any effort to update it?

- BCP


There's been no activity on GitHub since the code was uploaded.
Title: Re: AmiWest 2017 clarifications
Post by: Rob on October 24, 2017, 09:47:06 PM
@ssolie

Obviously NIC and Audio are a must for Tabor but will it's release also be dependent on the revised FPU emulation that Thomas is working on.

Are there a new blogs in the pipeline.  It would be nice to read a blog about the FPU emulation when it's done.
Title: Re: AmiWest 2017 clarifications
Post by: ssolie on October 24, 2017, 10:18:16 PM
Quote from: kamelito;832139
Is it possible to have something like fat binaries produced by the toolchain like what existed on the Next that target FPU and SPE on one executable?

Anything is possible. How about we get it working first. :)
Title: Re: AmiWest 2017 clarifications
Post by: ssolie on October 24, 2017, 10:29:06 PM
Quote from: Rob;832141
Obviously NIC and Audio are a must for Tabor but will it's release also be dependent on the revised FPU emulation that Thomas is working on.

As was seen at AmiWest, the A1222 runs pretty darn well already. There is another scheme to improve FPU speed plus the final solution of using SPE. It is a concern for apps like SketchBlock which work 100% in floating point but generally shouldn't be a big issue.

Quote
Are there a new blogs in the pipeline.  It would be nice to read a blog about the FPU emulation when it's done.

Yeah, very good idea. I'll see if I can influence the boys to produce one for us.
Title: Re: AmiWest 2017 clarifications
Post by: klx300r on October 24, 2017, 10:34:58 PM
Quote from: BCP;832138
Steve, I did'nt hear any mention of Timberwolf at AmiWest.  Since its been open-sourced has there been any effort to update it?

- BCP

+1 :hammer:
Title: Re: AmiWest 2017 clarifications
Post by: nbache on October 24, 2017, 11:19:02 PM
Quote from: ssolie;832133
Quote from: kamelito
2) Any update on the wiki front? like updating it further as there's still AmigaOS 2.x/3.x stuff
We only cover AmigaOS 4.0 and up as stated on the front page. I don't see any need to go backwards. The community can open up their own wiki if need be
Steven, I think Kamelito meant that the Wiki still has stuff which was valid back in 2.x/3.x days, but not fully (or at all) today.

And to answer that myself, I know that there have been recent rewrites of some of that stuff, but things take time. Usually it tends to happen when somebody points out a specific example over on Hyperions forums, and one of the active Wiki editors sees it and has time (and knowledge) to fix it.

Best regards,

Niels
Title: Re: AmiWest 2017 clarifications
Post by: ssolie on October 24, 2017, 11:24:56 PM
Quote from: nbache;832146
Steven, I think Kamelito meant that the Wiki still has stuff which was valid back in 2.x/3.x days, but not fully (or at all) today.

Ah, well that does require editors to work on it indeed. More volunteers are most welcome.
Title: Re: AmiWest 2017 clarifications
Post by: kamelito on October 25, 2017, 03:53:55 PM
Quote from: ssolie;832142
Anything is possible. How about we get it working first. :)


I've no Fun tinkering with Windows, Linux and Mac, that is why I plan to buy a A1222 motherboard or full system depending on the final price.
So please hurry up :)
Kamelito
Title: Re: AmiWest 2017 clarifications
Post by: MichaelMerkel on October 25, 2017, 04:20:46 PM
seeing the tabor getting priority now, how is the progress of os4.2?
has the priority been lowered? or has the planned featureset been changed? (multi core + enhanced 3d system, ...)?

thanks and regards...
michael
Title: Re: AmiWest 2017 clarifications
Post by: ssolie on October 25, 2017, 05:25:06 PM
Quote from: MichaelMerkel;832163
seeing the tabor getting priority now, how is the progress of os4.2?
has the priority been lowered? or has the planned featureset been changed? (multi core + enhanced 3d system, ...)?

As far as I know, nothing has changed on the AmigaOS 4.2 front. Hyperion has not provided me with any further clarification.
Title: Re: AmiWest 2017 clarifications
Post by: ssolie on October 25, 2017, 05:27:17 PM
Quote from: kamelito;832162
I've no Fun tinkering with Windows, Linux and Mac, that is why I plan to buy a A1222 motherboard or full system depending on the final price.
So please hurry up :)

I know exactly what you mean. I have Windows, Mac and Linux at home as well. The A1222 is especially exciting due to its lower price and that really cool laptop project Hans de Ruiter is working on. He had a prototype running at the show.
Title: Re: AmiWest 2017 clarifications
Post by: ferrellsl on October 25, 2017, 11:32:08 PM
Quote from: ssolie;832169
I know exactly what you mean. I have Windows, Mac and Linux at home as well. The A1222 is especially exciting due to its lower price and that really cool laptop project Hans de Ruiter is working on. He had a prototype running at the show.


Was it a true laptop or just a luggable?  If it's thicker than 1.5 inches then people shouldn't refer to it as a laptop but as a something else entirely.
Title: Re: AmiWest 2017 clarifications
Post by: Hans_ on October 25, 2017, 11:40:04 PM
Quote from: ferrellsl;832182
Was it a true laptop or just a luggable?  If it's thicker than 1.5 inches then people shouldn't refer to it as a laptop but as a something else entirely.


The plan is to make a kit that takes a full sized Mini-ITX board, so it's going to be fat (the rear connectors aperture alone is >1.5"). You're welcome to call it a luggable if you want.

I haven't designed the case yet, but do have a fully battery powered proof-of-concept (https://keasigmadelta.com/diy-laptop/) (NOTE: I had a slightly more elegant setup at the show than in the video (https://keasigmadelta.com/diy-laptop/)).

My goal right now is to get a full prototype designed.

Hans
Title: Re: AmiWest 2017 clarifications
Post by: Copernicus on October 26, 2017, 12:01:31 AM
Quote from: Hans_;832183
The plan is to make a kit that takes a full sized Mini-ITX board, so it's going to be fat (the rear connectors aperture alone is >1.5"). You're welcome to call it a luggable if you want.

I haven't designed the case yet, but do have a fully battery powered proof-of-concept (https://keasigmadelta.com/diy-laptop/) (NOTE: I had a slightly more elegant setup at the show than in the video (https://keasigmadelta.com/diy-laptop/)).

My goal right now is to get a full prototype designed.

Hans

That's is really cool idea, let it be slightly fatter than 1,5 inch. I hope you will finalize your project and we will eventually get portable AMI. Can't wait for that.
Title: Re: AmiWest 2017 clarifications
Post by: IanP on October 26, 2017, 01:32:07 AM
It could kick the butt of the Atari STacy but the ST Book will probably still have the edge on portability :rofl:
Title: Re: AmiWest 2017 clarifications
Post by: Rob on October 26, 2017, 01:50:50 AM
Quote from: Hans_;832183
The plan is to make a kit that takes a full sized Mini-ITX board, so it's going to be fat (the rear connectors aperture alone is >1.5"). You're welcome to call it a luggable if you want.

My goal right now is to get a full prototype designed.

Hans


The Tabor board could have some minor revisions made to make it suitable for a slimmer case design.  The rear I/O could be reduced by swapping some of the connectors out for header pins to connect to smaller PCB's to relocate the audio ports to the front and the USB and one NIC to the side, as is common with contemporary laptop designs.

Header pins to relocate the CR2032 battery holder to a flat position away from the motherboard would solve another height issue.

My final suggestions would be to use a right angled ATX power connector and there are also right angled PCIe sockets.

I think it would make for a much more appealing end product and I hope that A-EON would asses whether or not there is a business case to to produce a special run revised Tabor boards for the laptop kit.
Title: Re: AmiWest 2017 clarifications
Post by: IanP on October 26, 2017, 02:51:26 AM
A laptop specific motherboard design would be much better. I don't know what if any barriers (other than cost) there would be to designing such a board and modern style laptop but surely it would have a bigger market than a Mini-ITX system.
Title: Re: AmiWest 2017 clarifications
Post by: Bennymee on October 26, 2017, 10:26:22 AM
Quote from: ssolie;832128
AmiWest 2017 is over and it was one crazy time!

There were the usual announcements and many things were said.

If you want clarifications on anything, please post your questions here and I'll do my best to answer and/or clarify things.

Just don't guess what I meant. Ask instead.

Due the lack of movies, people wonder how quick the Tabor with 4.1 will boot to the Workbench.
Is the bootspeed quicker then an AmigaOne 500, mine is slower then my Windows machine - both with SSD ?
Title: Re: AmiWest 2017 clarifications
Post by: ssolie on October 26, 2017, 08:09:09 PM
Quote from: ferrellsl;832182
Was it a true laptop or just a luggable?  If it's thicker than 1.5 inches then people shouldn't refer to it as a laptop but as a something else entirely.

I don't see any point in debating the definition of laptop.
Title: Re: AmiWest 2017 clarifications
Post by: ssolie on October 26, 2017, 08:11:37 PM
Quote from: Bennymee;832204
Is the bootspeed quicker then an AmigaOne 500, mine is slower then my Windows machine - both with SSD ?

The boot speed is similar to any other AmigaOS installation. We have not optimized it in any way thus far. There is ample room for improvement of course but it is not a high priority.
Title: Re: AmiWest 2017 clarifications
Post by: Pgovotsos on October 27, 2017, 04:58:40 AM
Quote from: Copernicus;832186
That's is really cool idea, let it be slightly fatter than 1,5 inch. I hope you will finalize your project and we will eventually get portable AMI. Can't wait for that.


We've had portable Amigas for 20 years. I have Silent Paws 600, 1200, and 4000 and they go on the road nicely.
Title: Re: AmiWest 2017 clarifications
Post by: kamelito on October 27, 2017, 06:39:13 AM
@Steve
We know that AmigaOS is C with some assembly.
Is it C89 or C99 with some GCC extensions? Does it contain C++?
Regards
Kamelito
Title: Re: AmiWest 2017 clarifications
Post by: ssolie on October 27, 2017, 09:48:51 PM
Quote from: kamelito;832244
We know that AmigaOS is C with some assembly.
Is it C89 or C99 with some GCC extensions? Does it contain C++?

Depends on the component. We used whatever language/tool was most appropriate at the time the component was created.
Title: Re: AmiWest 2017 clarifications
Post by: Spectre660 on October 27, 2017, 11:46:34 PM
@Steve

Any plans to look into the X5000 CMI8738 Sound Card issues ?
The CMI cards seem to be the the models in greatest supply .

The  PCIex1 version issue is probably related to the Asmedia 1083 bridge  chips (Revision 1) but may be able to be  be overcome in the driver.  Case in point I have an Envyht24 pciex1 card with an Asmedia 1083  revision 1 bridge chip that works on my X5000 with AmigaOS 4.1FE with   no problems.

The PCI CMI8738 cards (which do not have a bridge chip) also have an issue as some models work and others do not.
I am using a PCI CMI8738 in my X5000 with no problems with AmigaOS 4.1FE
Or could the  the problem actually be with some X5000's ? and not with others ?


See the following thread if you have not seen it already .
http://forum.hyperion-entertainment.biz/viewtopic.php?f=57&t=3625
Title: Re: AmiWest 2017 clarifications
Post by: ferrellsl on October 28, 2017, 02:39:24 AM
Quote from: ssolie;832212
I don't see any point in debating the definition of laptop.


I didn't call for a debate.  Are you looking for one?  My point is that standards have changed over the past 30  years as to what defines a laptop and these days there's the expectation that a laptop has a certain dimensional and weight threshold, a battery life measured in hours and WiFi.  A Tabor shoe-horned into a box with some batteries and an LCD panel doesn't fit that definition at all.  I'd be laughed out of the room if I showed up with such a system in front of my peers and referred to it as a laptop....

So call it a laptop if you want to continue living in 1998, but time marches on and so do standards.
Title: Re: AmiWest 2017 clarifications
Post by: LoadWB on October 28, 2017, 02:53:56 AM
Hence why so many "laptops" are called "desktop replacements" or "portable computers."
Title: Re: AmiWest 2017 clarifications
Post by: ferrellsl on October 28, 2017, 03:08:01 AM
@LoadWB

Exactly.....this portable Tabor -in-a-box more closely fits the definition of a portable or desktop replacement....not a laptop.  I definitely wouldn't throw it in a briefcase or backpack for my travels or use it on the train or plane.
Title: Re: AmiWest 2017 clarifications
Post by: Oldsmobile_Mike on October 28, 2017, 04:04:41 AM
Quote from: ferrellsl;832273
A Tabor shoe-horned into a box with some batteries and an LCD panel doesn't fit that definition at all.  I'd be laughed out of the room if I showed up with such a system in front of my peers and referred to it as a laptop....

This thing sounds g-d ridiculous.  Where can one see a picture of it? :lol:
Title: Re: AmiWest 2017 clarifications
Post by: ferrellsl on October 28, 2017, 04:17:22 AM
Quote from: Oldsmobile_Mike;832277
This thing sounds g-d ridiculous.  Where can one see a picture of it? :lol:

Hans is working on it and has a video of his progress here:  https://keasigmadelta.com/diy-laptop/

Not sure why he chose to leave the Tabor board mounted in the PC case for this video unless it was to provide support for the video card. It'll be tough to stuff all that hardware into a case without a 90-degree adapter for the video card slot and then there's the driver board for the LCD panel, 6 batteries that look to be the size of standard C cells and a switching power supply.
Title: Re: AmiWest 2017 clarifications
Post by: kamelito on October 28, 2017, 09:34:10 AM
As I understand it Hans wants an easy way to travel with an Amiga computer. I guess that way he can code while he travel. I see it as a very good news. I still have an 80's mindset and at my age I don't care at all what other people think of me.
Kamelito
Title: Re: AmiWest 2017 clarifications
Post by: wawrzon on October 28, 2017, 03:15:34 PM
Quote from: kamelito;832281
As I understand it Hans wants an easy way to travel with an Amiga computer. I guess that way he can code while he travel. I see it as a very good news. I still have an 80's mindset and at my age I don't care at all what other people think of me.
Kamelito

an easy way to travel with an amiga computer is to throw your a600 or a1200 in a suitcase. i used to do it a lot in the nineties, when carrying the computer around my school, video studio, to my girlfriends place or parents home. in this respect it was truly "portable."
Title: Re: AmiWest 2017 clarifications
Post by: kamelito on October 28, 2017, 05:48:43 PM
Quote from: wawrzon;832290
an easy way to travel with an amiga computer is to throw your a600 or a1200 in a suitcase. i used to do it a lot in the nineties, when carrying the computer around my school, video studio, to my girlfriends place or parents home. in this respect it was truly "portable" and certainly qualifies more as such than any however modded os4 system today.

 Did you read that it has battery? That he is using battery that are permitted onboard? That way he could use it's Amiga while flying for example...  Kamelito
Title: Re: AmiWest 2017 clarifications
Post by: eliyahu on October 29, 2017, 12:24:00 AM
Quote from: ferrellsl;832182
Was it a true laptop or just a luggable?  If it's thicker than 1.5 inches then people shouldn't refer to it as a laptop but as a something else entirely.
fair point. however at the moment the project is in very early days. hans mentioned he wanted to 3D print a case for everything so it would be close to a true laptop, but we just don't know yet. he's just prototyping things right now, so we can't really judge what the final offering will be. they didn't even know if they would offer it as a kit, a finished product, or whatever. he had literally just picked up the batteries that week.

anyway -- i think it's cool that folks are tinkering like this. :)

-- eliyahu
Title: Re: AmiWest 2017 clarifications
Post by: ssolie on October 29, 2017, 08:17:41 PM
Quote from: Spectre660;832269
Any plans to look into the X5000 CMI8738 Sound Card issues ?

I don't know of anybody looking into this problem at the moment.
Title: Re: AmiWest 2017 clarifications
Post by: ssolie on October 29, 2017, 08:27:01 PM
Quote from: ferrellsl;832273
I didn't call for a debate.  Are you looking for one?  My point is that standards have changed over the past 30  years...

I guess I just didn't notice my MacBook Pro booted in 6 seconds from cold and I have Chrome up and running in under 10 seconds. :)

Listen, all of us here know time has moved on. My point is that somebody is trying their best to create a portable Amiga running the latest AmigaOS. If some people want to point and laugh that is their business but that kind of stuff doesn't belong in this thread.

I am looking forward to my new A1222 laptop and I don't care if my peers laugh or not.
Title: Re: AmiWest 2017 clarifications
Post by: ferrellsl on October 30, 2017, 03:24:20 AM
Quote from: ssolie;832369
I guess I just didn't notice my MacBook Pro booted in 6 seconds from cold and I have Chrome up and running in under 10 seconds. :)

Listen, all of us here know time has moved on. My point is that somebody is trying their best to create a portable Amiga running the latest AmigaOS. If some people want to point and laugh that is their business but that kind of stuff doesn't belong in this thread.

I am looking forward to my new A1222 laptop and I don't care if my peers laugh or not.

I look forward to it as well, but let's call it what it is....as the saying goes, you can put lipstick on a pig and you still have a pig.

Shoe-horning a Tabor into a small box doesn't make it a laptop....it's a Tabor in a small box.

People outside the NG Amiga community who might be interested in an Amiga laptop are only going to be annoyed when they search for an Amiga "laptop" only to find a Tabor crammed in a small box with no WiFi and battery life measured in minutes instead of hours and it's as thick as a pizza box.
Title: Re: AmiWest 2017 clarifications
Post by: Hans_ on October 30, 2017, 06:38:58 AM
I'll say more later, but just a few quick comments...

Firstly, yes, I have a 90 degree PCIe riser. It's not featured in the video because I don't have a computer case where the riser can be used. Plus, it was an electronics test, so physical layout wasn't important.

Quote from: ferrellsl;832399

...

People outside the NG Amiga community who might be interested in an Amiga laptop are only going to be annoyed when they search for an Amiga "laptop" only to find a Tabor crammed in a small box with no WiFi and battery life measured in minutes instead of hours and it's as thick as a pizza box.


It's always interesting to see what people decide is the "definition" of something. Perhaps I should run a survey to see just how big a box I can get away with. ;-)

I'm calling it a laptop because I'm following the typical laptop design: motherboard, batteries & keyboard in the base, and a flip-up screen. That differs quite substantially from what you get when you search for luggable on Google.

Regarding battery life, I have a 93 WH battery pack, and measured 28W power usage with the CPU & GPU maxed out as much as possible. So it's good for a few hours at least, and that's without any dynamic power management. I could increase the battery capacity, but then it would exceed the max allowed on a plane.

For wifi I'm currently going to use a tiny wifi router that works in client mode. There are nicer options out there, but the wifi-router eliminates the need to write drivers, which makes getting the first prototype done easier.

Obviously, this "laptop" kit won't be for everyone. If you're someone who likes this kind of stuff, then I encourage you to sign up to the mailing list (https://keasigmadelta.com/diy-laptop/) (here (https://keasigmadelta.com/diy-laptop/)). If not, then perhaps A.L.I.C.E. would be more to your taste (it looked pretty neat at AmiWest).

Hans
Title: Re: AmiWest 2017 clarifications
Post by: Spectre660 on October 30, 2017, 05:45:56 PM
That is quite unfortunate .

Quote from: ssolie;832367
I don't know of anybody looking into this problem at the moment.
Title: Re: AmiWest 2017 clarifications
Post by: Hans_ on October 31, 2017, 12:27:43 AM
Quote from: Spectre660;832429
That is quite unfortunate .


From what I heard, some CMI8738 sound cards have a serious bug on their PCI-to-PCIe bridge chip. It generally isn't a problem on true PCI systems, but causes trouble when there's a PCIe to PCI bridge in-between (e.g., like on the X5000).

There are CMI8738 cards with a fixed bridge chip, but it's impossible to know ahead of time which one you'll get. So, basically a lottery.

I don't think that trying to work around this issue is worth it. It would be far better to find a genuine PCIe sound card and write drivers for that.

Hans
Title: Re: AmiWest 2017 clarifications
Post by: Pgovotsos on October 31, 2017, 01:44:18 AM
Quote from: Hans_;832445
I don't think that trying to work around this issue is worth it. It would be far better to find a genuine PCIe sound card and write drivers for that.

Hans


This is one of those times when I really wish this forum had a Thanks, thumbs up, or +1 button.

Hans, the above is for you. Below is not. It's venting frustration at A-eon, Hyperion, AmigaKit that your comment brought back to the surface.

Danger Will Robinson, Danger! Major rantage ahead!

Come on, the motherboards have been in hand for years. There are drivers for all components for the "alternate" operating systems. How about some love for the PRIMARY operating system?

I can't write driver code worth a hoot, but is it REALLY that hard? Took years for everything on board the X1000 to be supported. I was hoping that moving stuff off the motherboard to cards would make it easier since we already have drivers that work. Guess not.

Hasn't A-eon, Hyperion and / or AmigaKit learned any lessons from the X1000 experience? Guess not. I've got a lot of money and time tied up in 2 X1000s and 2 X5000s. That's a lot of money sitting around, spent based on a lot of promises that have not been delivered on - after years.

Lets quit mucking around with experimental file systems that still have bugs, incomplete SATA drivers that still barely provide the minimum to mount 2 drives, pushing useless Xena that still can't do anything but blink some lights on a project board that doesn't even physically fit in all the systems. The list of "lets quit"s goes on and on.

Would I love to see a new ImageFX or a functioning Libre Office? Darn tootin' but I want to see 100% functional hardware before diluting what few development resources there are in Amiga land on "extras". There's other software that can get the work done for now.

Cut the garbage and get core components 100% supported before doing anything else! I don't care who is responsible for what hasn't happened. I don't care where the fingers get pointed. The fingers have got to come out of someone's bum and start working.

How long are we supposed to keep forking over money on the promises of "it's coming, it's coming"? There's been an awful lot of patience being expended, and HAS been expended. WHEN is there going to be some delivery? When is a system going to be completed before rushing on to another one. When is ANYTHING going to get delivered within 5 years of promised? Heck, 5 years would be a major improvement over the "never" time frame currently in place on so many issues.

When will the party stop going on and just flipping get here? I swear, some days it's enough to make me want to just throw it all away.

You may now return to your regularly scheduled peaceful programming :)
Title: Re: AmiWest 2017 clarifications
Post by: Spectre660 on October 31, 2017, 01:45:48 AM
If you saw my first post on the subject  in this thread you will see that there are quite a few results with different models of cards that are not consistent.
the buggy bridge chip works perfectly with a different PCIEx1 sound card (Envyht24) and its driver and also some PCI CMI878 cards (no bridge chip) work perfectly while other PCI versions of the the CMI8738 (no bridge chip) do not .
The CMI8738 versions exist currently in good quantity so it may be worth having thorough look at the driver .
This is one area that may be diminishing the X5000 experience among new users as some are receiving their systems with problem versions of the CMI8738 cards.
 

Quote from: Hans_;832445
From what I heard, some CMI8738 sound cards have a serious bug on their PCI-to-PCIe bridge chip. It generally isn't a problem on true PCI systems, but causes trouble when there's a PCIe to PCI bridge in-between (e.g., like on the X5000).

There are CMI8738 cards with a fixed bridge chip, but it's impossible to know ahead of time which one you'll get. So, basically a lottery.

I don't think that trying to work around this issue is worth it. It would be far better to find a genuine PCIe sound card and write drivers for that.

Hans
Title: Re: AmiWest 2017 clarifications
Post by: Hans_ on October 31, 2017, 06:12:42 AM
Quote from: Spectre660;832449
If you saw my first post on the subject  in this thread you will see that there are quite a few results with different models of cards that are not consistent.
the buggy bridge chip works perfectly with a different PCIEx1 sound card (Envyht24) and its driver and also some PCI CMI878 cards (no bridge chip) work perfectly while other PCI versions of the the CMI8738 (no bridge chip) do not .
The CMI8738 versions exist currently in good quantity so it may be worth having thorough look at the driver .

Well, I'm just repeating what I've heard. That PCIe bridge chip's IRQ bug is described as "fatal" with "no useful OS workarounds possible." Perhaps your Envyht24 is using a newer revision of that bridge chip, or maybe you're just very lucky.

I can't comment on any other issues.

Quote from: Spectre660;832449
This is one area that may be diminishing the X5000 experience among new users as some are receiving their systems with problem versions of the CMI8738 cards.


Now that everyone is aware of the issue, vendors can choose a different card that's known to work.

Hans
Title: Re: AmiWest 2017 clarifications
Post by: Spectre660 on October 31, 2017, 09:05:19 AM
It actually does uses the version 1. See the Ranger Screen grabs from the post below.
http://forum.hyperion-entertainment.biz/viewtopic.php?f=57&t=3625&start=40#p41538


Quote from: Hans_;832455
Well, I'm just repeating what I've heard. That PCIe bridge chip's IRQ bug is described as "fatal" with "no useful OS workarounds possible." Perhaps your Envyht24 is using a newer revision of that bridge chip, or maybe you're just very lucky.

I can't comment on any other issues.



Now that everyone is aware of the issue, vendors can choose a different card that's known to work.

Hans
Title: Re: AmiWest 2017 clarifications
Post by: Iggy on October 31, 2017, 07:50:50 PM
Quote from: Spectre660;832449
If you saw my first post on the subject  in this thread you will see that there are quite a few results with different models of cards that are not consistent.
the buggy bridge chip works perfectly with a different PCIEx1 sound card (Envyht24) and its driver and also some PCI CMI878 cards (no bridge chip) work perfectly while other PCI versions of the the CMI8738 (no bridge chip) do not .
The CMI8738 versions exist currently in good quantity so it may be worth having thorough look at the driver .
This is one area that may be diminishing the X5000 experience among new users as some are receiving their systems with problem versions of the CMI8738 cards.


Actually, it gets weirder than that, since ALL PCI cards are working through a bridge chip (the PCI-PCI-E bridge chip on board the X5000).

You would think the PCI-E cards would work better, BUT the CMI8738 is a PCI component, so using it you're again...using a bridge chip, but this time on the sound card.
It might be less problematic if Aeon had chosen a sound card that featured a native PCI-E component.

In any case, I've got a VIA Envy24 card sitting around waiting for use (its the better of the two solutions anyway).
Title: Re: AmiWest 2017 clarifications
Post by: Spectre660 on October 31, 2017, 08:12:04 PM
As seen with Acill's soundblaster with the Amiwest MorphOS demo things can get be dodgy on the MorphOS side too .
Interestingly with my X5000 my PCI CMI8738 works with no problems under AmigaOS 4.1FE  but causes a freeze under Linux if used with full screen video.
The issue is to get a working solution for which the availability of the sound cards does not dry up .

It may take a third party approach like the RadeonHD driver to keep up though unless there is a move to Radeon HD audio or USB sound cards .
Title: Re: AmiWest 2017 clarifications
Post by: Iggy on October 31, 2017, 09:03:10 PM
Quote from: Spectre660;832484
As seen with Acill's soundblaster with the Amiwest MorphOS demo things can get be dodgy on the MorphOS side too .
Interestingly with my X5000 my PCI CMI8738 works with no problems under AmigaOS 4.1FE  but causes a freeze under Linux if used with full screen video.
The issue is to get a working solution for which the availability of the sound cards does not dry up .

It may take a third party approach like the RadeonHD driver to keep up though unless there is a move to Radeon HD audio or USB sound cards .


Yeah, but again, there we're dealing with a PCI card being driven via a bridge component.
Although you would have thought legacy drivers like the SB Live would have been tested, then again the MorphOS ISO Paul was provided was a beta.

Odd, your freeze up under Linux, but I think I'm just going to avoid CMI, at least for the time being.

In any case, as you've pointed out on other forums, having multiple OS' on the X5000 will make things interesting.

That's why its going to become my PPC system of choice, after all, I have no use for OSX, but the other three possibilities...this intrigues me.
Title: Re: AmiWest 2017 clarifications
Post by: Hans_ on November 01, 2017, 12:00:54 AM
Quote from: Spectre660;832461
It actually does uses the version 1. See the Ranger Screen grabs from the post below.
http://forum.hyperion-entertainment.biz/viewtopic.php?f=57&t=3625&start=40#p41538

Assuming that they correctly updated the revision register between chip revisions... (stuff like this is so easy to forget).

Hans
Title: Re: AmiWest 2017 clarifications
Post by: Spectre660 on November 01, 2017, 12:17:54 AM
The chips seem to have have markings that indicate the versions.
My version 1's end with 1B1
My version 3 ends with 1B2


Quote from: Hans_;832489
Assuming that they correctly updated the revision register between chip revisions... (stuff like this is so easy to forget).

Hans
Title: Re: AmiWest 2017 clarifications
Post by: Spectre660 on November 08, 2017, 04:03:22 PM
http://forum.hyperion-entertainment.biz/viewtopic.php?f=57&t=3846&start=40#p42936
Title: Re: AmiWest 2017 clarifications
Post by: Spectre660 on November 08, 2017, 04:11:55 PM
http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=39511&forum=14#744313

Quote from: Hans_;832445
From what I heard, some CMI8738 sound cards have a serious bug on their PCI-to-PCIe bridge chip. It generally isn't a problem on true PCI systems, but causes trouble when there's a PCIe to PCI bridge in-between (e.g., like on the X5000).

There are CMI8738 cards with a fixed bridge chip, but it's impossible to know ahead of time which one you'll get. So, basically a lottery.

I don't think that trying to work around this issue is worth it. It would be far better to find a genuine PCIe sound card and write drivers for that.

Hans