Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Roderick Klein

Pages: [1] 2 3 ... 13
1
Programming / Re: OS/2 kernel requiring speculative execution patch!!!!
« on: January 03, 2018, 06:21:52 am »
So I'm sure many are aware of the news regarding the flaw in Intel's speculative execution in the majority of the CPUs:
https://www.theregister.co.uk/2018/01/02/intel_cpu_design_flaw/

The problem doesn't end there, it affects anything i686 and newer (as this was when speculative execution was introduced):
https://en.wikipedia.org/wiki/P6_(microarchitecture)

Which means, anything Pentium II and newer is affected.

Will ArcaNoae be working on patching the OS/2 kernel with KPTI? Otherwise I won't be able to consider OS/2 a viable OS for going on the internet anymore for anything personal.

If you want to know if  Arca Noae wants to patch the kernel then you should also open a ticket on
https://mantis.arcanoae.com. They have stated repeatedly no ticket=no support.

Roderick

2
Programming / Re: Compiling an OS/2 Driver
« on: December 31, 2017, 06:27:32 pm »
Also forgot about the Microsoft C compiler. Its better to use the Open Watcom compiler. It may not be suitable to compile Mozilla with as that requires GCC. The Open Watcom compiler seems to be much stricter in grabbing any errors in your code then Visual Age or the Microsoft 6 C compiler that is included in the DDK. Also the Open Watcom code I understands generates better optimized code.

If you do want to write an article recommending how to write drivers.

* Include some decent comment in the code.

* Any kind of source control system is your friend. Having worked at Mensys the fact  drivers where *frequently* checked in made it *easier* to find why a certain version of a driver would suddenly blow up. Its then easier to locate the code that was modified.

As I have said so often, finding the cause of a kernel dump can be extremely time consuming.  That is why the above conditions may cost some time when you work on you project. But you will be gladd you did it when you run into a problem.

Roderick

3
Multimedia / Re: How to change the audio card driver
« on: December 31, 2017, 03:41:35 pm »
CHeck the documentation in readme.txt in the directory
\CID\SERVER\MMOS2\DRIVERS\UNIAUD and see if /A: switch is usefull so you can select the audio chip which the driver uses to control

Roderick

4
Multimedia / Re: How to change the audio card driver
« on: December 31, 2017, 12:13:20 am »


 I just receive a laptop  ASUS X551c   , i install arcad 5.01 , and the installation  pass with no issu ,

 the video  is intel Hd graphics   run on panorama

the network card in is  Realtek pci e  Fe family  work
 
  the 2 usb port  work
 my mouse logitek and keypad mouse work


 by my sound card  is a realtek  alc 270  , but ir install the  intel hda driver
 the sound distortion a lot and loop 1 a 2 sec work a couple a sec and reloop

 My question how to reinstall  to try a another driver    to force to use anoher  to try



Happy New year

Robert

 

Robert,

This most likely not required to uninstall the driver.  The driver that is installed in your config.sys is UNIAUD32.sys and UNIAUD16.sys.  There is no need to uninstall as the driver scans your system loads the proper audio driver from the UNIAUD32.SYS driver (the driver supports many chipsets).
On OS/2 issue's with an audio driver are also not resolved by uninstalling and the reinstalling the driver.  At least that is how I read your message that you think such an action would help resolve your issue.

Its possible your system had 2 HDA audio chipsets (one on the video card). Thats the only reason I can think off.
I am no certain we can help you in this forum. It might help to open a ticket in the AN bugtracker https://mantis.arcanoae.com. You can login in with your credentials you use to login on the www.arcanoae.com website.

Roderick Klein


5
Article Discussions / Re: ArcaOS Wishlist - 6 months !!
« on: December 30, 2017, 09:01:27 pm »
While I really happy with the work you Martin are doing and have been doing to collect API documentation and source code for drivers and applications.  I think its possibly time for a new strategy. What can be done with all of this source code ? As a community we can try to collect more source code. But the vast majority of work is not being done by the community. I can understand why that its happening as writing device drivers is a time consuming job.
While I can understand that you are not happy with the DRV32 library...

Practically speaking who is working on drivers for example ? And I do not think we need even more examples as Netlabs and hobbes has tons of driver sources stored already. Also checkin into SVN at Netlabs with revision history so people can see what and why was modified. When do we have enough source code ?

Roderick

We will never have enough source code !!  Collecting source code and documenting the OS/2 API is already advanced but it is not finished yet.  Knowledge it just a base to create things. I still do not think that the knowledge to create device drivers is completely consolidated and public. We need more documentation and articles about this subject.

But you are right by asking what comes next.

In the device drivers area I still think that there should be alternatives to the IBM DDK Source code samples, the IBM DDK binary tools can be used (since some version of the IBM DDK were available with free registration on the web) but I think that some open source samples are still needed.  It will be interesting to try to create an open source friendly IBM DDK Samples alternative. (maybe BSD license)

For drivers based on the IBM DDK samples it will be satisfactory to me to create close source projects, but that are collaborative and governed by an organization like Netlabs, just like Lars is doing with his USB drivers. It is not the best thing for open source to use IBM DDK based drivers, but giving the source code changes rights to a third party will make me happy on this area to reduce the risk that the developer loose interest and we may lost the source code.

On the other hand we need device driver developers which is the hardest part. But I think it is also worst to have the rare case of having someone that has the will to create driver, but can not find examples or documentation on how to do it on OS/2. If someone wants to sponsor a device driver or try to raise money to create one, I will jump into that ship as long as it is an open source driver or at least that the source is giving to a  third party non-profit organization that will share the rights and may continue the development in the future. Maybe with the exception that for the moment it will not be desirable a device driver of the ones that are on the
Arca's roadmap, just to don't step other firemen hose.

(please remember this are my personal opinions).

Regards

Well let me ask you this question then. What should the source code contain ? I will explain to you why we are pretty complete. Look which drivers OS/2 can load. IFS, storage drivers, NIC and audio for example.
We have plenty of examples of these drivers at Netlabs and on hobbes. If you even start looking in more detail you will see the DANIS506.ADD and OS2AHCI will have a small portion of code that talks to OS/2.
The OS/2 kernel/OS2DASD driver make calls to storage driver and its most likely these API's you are interested in to have documented. The other code in the DANIS506.ADD and OS2AHCI is not that interesting if you for example want to create a new open source version of OS/2. Lets say you would want that kernel to be able to load OS/2 drivers.

With audio, NIC and IFS drivers its the same thing. Most of the code is mostly not OS/2 related. If you want to write a driver for OS/2 you can go two ways. The first one really sucks. This I think could be example where you end up with up: https://www.intel.com/content/dam/www/public/us/en/documents/datasheets/ethernet-controller-i350-datasheet.pdf Happy reading and then writing code based on all the registers.

Or you do how the Multimac project started out:
http://trac.netlabs.org/multimac/browser/trunk/e1000e/e1000hw.c
If you skim the code you will get somewhat of a feel what is happening and what the code does. It talks to chip.
Most of that code is not even OS/2 code specific. Its just C code that talks to the hardware and thanks to C code being a standard open watcom can compile the code. 

Both these scenario's take up a lot of time and requiring patience and working accurately. Such as checking into SVN so you can track what changes you made. If a driver does crash you system you need to use a kernel debugger via a serial cable or grab a memory dump. Then it can still be very time consuming and a detective job to find why a driver you wrote blows up.

Anyway I kind of what to explain to you that for anybody who wants to write device drivers for OS/2 it should be possible with the current code we have. But you need to have patience, time and understand what you are doing. Drivers work at ring 0 of a computer and an error can make the OS crash or hang. 

As I see it the DANIS506.ADD driver is mature but the code will most likely never be updated. But when Mensys had the first OS2AHCI driver developed the developers that worked on that code looked at the DANIS506.ADD driver to spot what they needed to pay attention to on how to interface with OS/2 its API calls.

Both JFS.IFS and FAT32 are basically the same API calls into the OS2KRNL the rest is file system specific code.
Maybe now you understand if you want developers to write code why I said we always have had enough code.

As when it comes to the DDK as I understand a portion of the DDK code is in Open Watcom and the guys rewrote portions of the DDK code. How much of the DDK code is in the Open Watcom I can not tell you.
While I share you hope the DDK can be rewritten I think with our current human resources we have its not practical to expect this to happen anytime soon.

This is why invited you to work with the people in the forum and with OS/2 VOICE is you want to start working on projects such as one I suggested. We are collecting funding. Any further OS/2 development will need more people on the platform that also means users.

I have been looking for people to help repackage software in RPM software rpm.os2voice.org could get large library I simply lack the time for it with a day job. But getting more applications is what I need people to help me with.

I hope the stuff about the driver stuff was useful if you have questions let me know.

Everybody have a good 2018 and thanks for helping to keep OS/2 on the move.

Roderick

6
Article Discussions / Re: ArcaOS Wishlist - 6 months !!
« on: December 30, 2017, 06:22:16 pm »
Again I invite everybody to look at David Azarewicz his presentation he gave at Warpstock in Torinto this year. He is working on Wifi and USB 3.0 and a new audio driver.  All of these projects are moving along and from how I understand his presentation they are in a far reaching stage. But its all a lot of work.

If you look at the postings they have been doing they are also working on updating the base OS:

Such as adding MSI interrupt support to OS/2 and to the drivers that need to use them.
I have had two systems myself where a NIC and disc controller would not work without MSI IRQ support.
They also for example expanded the IRQ support of the kernel from 48 to 64 IRQ's because some of the more modern mainboards so peripherals work.

So a lot of stuff continues to be worked on. I would imagen why they would do USB 3.0 first as I do find any USB 2.0 host controller support in computers being sold in stores.

Roderick





7
Article Discussions / Re: ArcaOS Wishlist - 6 months !!
« on: December 30, 2017, 04:17:57 pm »
We have Lars Erdmann and Wim Brul working on the UBSMSD and USB audio driver.
Other then that not much driver development is being done by the community (Or did I miss anybody). As I typed before I can understand why, writing drivers is not an easy task and its timing consuming. Especially when it comes to debugging drivers then run into trouble.

What I think would be great is if we can see if we can some more development going again.  From what I can tell developers such as BWW already get very little feedback and Lars I think also does not get that much amount of feedback. Hence my other reason why I think at certain moment you have enough source code as community and see what we can do with that source code. As in put it to good use.

One thing I think that would be great community project is to use the Arca Noae ACPI toolkit and see if we can create a tool that can

* Warn when your battery runs low on your laptop. I miss that Thinkpad feature and I do no get an audio beep.

* A tool that dim the backlight of your LCD screen when you are running on battery power. Doing this is laptop depended but might be possible in some cases via ACPI or in some cases via the VESA BIOS. It could dramticly extend the battery live of your laptop.

Just one idea. on how to keep OS/2 really useable so people stick with the platform. Then it also makes more sense to talk about a full blown OS/2 open source replacement. You need a go in between if such a project even has a fighting chance. The above is just one example of what we could do to try and improve the useability of OS/2.

Roderick

8
Article Discussions / Re: ArcaOS Wishlist - 6 months !!
« on: December 30, 2017, 01:41:12 pm »
Hi

Like I said before, even that DRV32 is freeware, it's source code it still govern by the IBM DDK license. It has been used to add (I don't know which) functionality to the AHCI driver. What I would consider something better, is that DRV32 source code became a netlabs close source project just like Lars has done with the USB drivers, so Netlabs can also share the ownership of it to have a chance that if 5 or 10 years David no longer wants to work on DRV32, it can be switched to other developer. With that DRV32 will still respect the IBM DDK license and there will be change to don't get "lock".
 
Regards

While I really happy with the work you Martin are doing and have been doing to collect API documentation and source code for drivers and applications.  I think its possibly time for a new strategy. What can be done with all of this source code ? As a community we can try to collect more source code. But the vast majority of work is not being done by the community. I can understand why that its happening as writing device drivers is a time consuming job.
While I can understand that you are not happy with the DRV32 library...

Practically speaking who is working on drivers for example ? And I do not think we need even more examples as Netlabs and hobbes has tons of driver sources stored already. Also checkin into SVN at Netlabs with revision history so people can see what and why was modified. When do we have enough source code ?

Roderick

9
Article Discussions / Re: ArcaOS Wishlist - 6 months !!
« on: December 30, 2017, 01:28:12 pm »
Quote
Yes, USB is necessary since most usb devices are now 3.0.

No, USB  3 is not necessary. USB 3 devices will work with USB 2 cables, hubs, and controllers, at USB 2 speeds. However, a USB 3 driver is becoming much more important now that many new computers don't have USB 2 controllers. This is likely more important than WiFi.

Quote
I am wondering about the encryption that these devices demand that you do.  Don't do the encryption and the drive is useless.

The only device that I have seen with "so called" built in encryption was easily fixed. First, you probably want to use DFSEE to image the drive, so you can put it back to the way that you got it. Then, use DFSEE to wipe the front end of the disk. Now, it is just an empty USB device,waiting for you to put proper partitions on it, and format it. There may be something new, that I don't know about.

Quote
I was also wondering about WIFI.  This is something I have been waiting for a long time.

Yeah, WiFi is about 10 years over due. I do know that most of the project has been done, but other things are taking the developers time.

Having worked on this project with David at Mensys at the time the Wifi driver project got a mayor blow by the LInux guys making changes of some kind. It made updating of the E1000E driver that is hosted at Netlabs just about impossible. Basically from what I can tell from the presentation from David at Warpstock is that Arca Noae has library that is used to compile FreeBSD sources.  That is how they created the new NIC drivers.
That is what put the WiFi drivers on hold.

For the same reason UNIAUD based on Alsa seems to be RIP.  They made to made changes to the Alsa code. David mentioned they are working on a FreeBSD audio driver.

Roderick

10
Article Discussions / Re: ArcaOS Wishlist - 6 months !!
« on: December 29, 2017, 11:59:54 pm »

Quote
But: as it turns out ArcaOS is getting more and more closed source, so - even if these Drivers will be available those may be only licensed for ArcaOS I fear - may be not.

Actually, that isn't entirely true. Arca Noae is adding value (sometimes by removing unproven, unstable , or legally questionable, features from some things) to most of their drivers etc. and they are building them, with some support available. Those drivers are available, for all "current" versions of OS/2 (warp 4, and up, AFAIK). through subscriptions. The base code is shared with the open source repositories, when it is possible to do it, but somebody else needs to build, and support, that code. I think the Arca Noae build system is kept private, and probably has patches etc. that public sources won't have. When you purchase a subscription, you support Arca Noae in making better drivers (and other things).

Hi Doug

I found an exception here. The OS2AHCI driver used to be completely open source (GNU GPL V2) and now the latest versions includes David's Drv32, which the binaries may be freeware but the source code is contaminated by the IBM DDK license (can not be made public).

They may have their reasons that with David's Drv32 they can do interesting things (but I haven't noticed that on OS2AHCI), but it is step back in a driver that used to be 100% open source software.

---

Everybody, keep posting our wishlist about ArcaOS. It seems to me that  the "Sound Driver" is starting to get a higher priority on the community wishlist.

Regards

I think I invited people to checkout David his presentation from Warpstock Toronto 2017.
They are working on USB 3.0 and an audio drivers is in the works to replace UNIAUD.
Look up the video on youtube in which he explains it in more detail.

Roderick

12
Applications / Re: Software Reports
« on: December 12, 2017, 08:49:37 pm »
Using ArcaOS 5.01

Installing eSchemes makes the whole system unstable.

Installing Animated mouse pointer 1.01 locks the system up. 

Both resulted in me installing ArcaOS 5.01 again.

If eSchemes failed while I was testing and it would hang the desktop.
Reboot the system to the command line. Rename the eSchemes directory.
Reboot, DLL's can no longer be found by the WPS.
Run Checkini.exe and presto. Or does that not fix the crashes then ?

Not certain if you can do the same with animated mouse pointers.

Roderick

13
Internet / Re: Experimental build of SeaMonkey
« on: November 28, 2017, 11:15:58 pm »
I've uploaded an experimental build of SeaMonkey 2.42.9ESR, https://bitbucket.org/dryeo/dry-comm-esr31/downloads/seamonkey-2.42.9esr.en-US.os2_exp1.zip
Optimized for size instead of performance, should fit into memory a bit better and almost as fast. Also optimized for a Pentium M so needs a CPU with SSE2 support.
You could also install it as if it was an RPM, putting everything in @UNIXROOT/usr/lib/seamonkey-2.42.9esr and a copy of seamonkey.exe in @UNIXROOT/usr/bin so it is on the PATH.
Same codebase as the latest release of Firefox. Once dmik releases another version of Firefox, I'll release the usual i686 build and if I ever get some guidance on building an RPM, I'll try to release them as well.
Needs the latest libcx and libc that are now available on netlabs-release RPM repository (I hope).

Note there also seems to be a regression with highmem support, marking xul.dll to load code and data makes SM unstable here on ArcaOS.

In my experience only load the code segments high, not the data segments!

I am running Firefox, Thunderbird and Open Office next to each other without an issue. Without loading the DLL's in high memory it toasts my system within a few minutes.

Roderick

14
General Discussion / Re: Good Bye Net Neutrality
« on: November 26, 2017, 05:28:29 pm »
This whole discussion about free market is somewhat of a weird thing in the sense that internet has simply become such a extremely key item in our world these days. Many things as business owner or private individual in the Netherlands you can simply no longer do without having internet access.  If you get unemployed for example 99% of the stuff needed to ask for unemployment can only be done online.  The internet is everywhere and its just as vital as other types of infrastructure (railways, roads and airports).

While the internet is operated by many different parties it is clear it has become a vital part of daily. It has also become a vital tool for our democracy to operate. That said it also threatens it, but that is live.

https://en.wikipedia.org/wiki/Net_neutrality_in_the_Netherlands
We have a large degree of network neutrality in the Netherlands but I wonder with the current right wing government how long its going to take before its lobbied away...

15
Article Discussions / Re: Sponsorship needed for new OS/2 web browser
« on: November 22, 2017, 10:57:41 pm »
Hi

Trying to move on there is a new post at OS2VOICE.
http://articles.os2voice.org/

It seems to be a good step on answering some of the "well funded" questions about the idea/project. I think think that Qt5 is something we need to support and that Bitwise works has shown the skill to deliver OS/2 projects on the past.

Qt's QtWebEngine seems the way to go to have a Chromium port or any other browser that uses Qt's QtWebEngine. Other ways may be too much time consuming or expensive. But if someone have alternatives it will be great to have the developers to back it up.


Regards

Thanks Martin for your posting.  I just want to emphasize that the complete posting on articles.os2voice.org has been reviewed by Dmitriy Kuminov  from Bitwise works.

Roderick Klein
President OS/2 VOICE

Pages: [1] 2 3 ... 13