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 - Pete

Pages: 1 ... 8 9 [10] 11 12 ... 73
136
Setup & Installation / Airboot no longer works...
« on: May 11, 2020, 11:27:57 pm »
Hi All

An interesting evening so far. Thought I would create an ArcaOS 5.0.4 USB Flash Drive install which worked OK; booted fine to the Maintenance Console so I would expect to be able to install from it.

However, on rebooting from the Maintenance Console Airboot threw a wobbly and delivered this message:-

Scanning...
- Your system has at least one broken partition table entry or your hard drive contains bad sectors. System halted.(HDD2)


Hmmm... does not look good.

I booted from an ArcaOS5.0.1 dvd to the Maintenance Console and from there discovered that there does not seem to be any Airboot docs installed on my ArcaOS 5.0.1 system.

I did locate airboot2.exe in \sys\bin and ran it thinking to delete the Airboot installation and then reinstall. So I then discovered it is a case of using "lvm:newmbr:1" on the command line to remove Airboot.

Before going any further I chkdsk'd drives with no reported problems, no problems at all running dir on any drive.

I had a look at the disks/drives using LVM - which made no complaint about bad partition table(s).

As I have DFSee installed I fired that up - I would like to say no problems reported but there are some lines that have me puzzled:-

At least 4 non-trivial minor warnings were not shown. Use 'part -w:t -t-' for details.

DFSee OS/2   15.0 : Executing: part -w:t -t-
Command timestamp : Monday 2020-05-11 19:29:39
 Pid02=J: warning : Logical partition is marked as startable! (active)
 Pid03=H: warning : Logical partition is marked as startable! (active)
 Pid04=L: warning : Logical partition is marked as startable! (active)
 Pid06=D: warning : Logical partition is marked as startable! (active)


Not sure how they have become marked as startable, H: and L: are boot drives and on the Airboot menu but J: and D: are not - and I do not think logical drives can be marked startable.

Is this what Airboot was moaning about?

Having checked that my ArcaOS5.0.1 installation was Startable I rebooted and had no problem booting my ArcaOS installation.

I tried reinstalling Airboot which worked fine but on reboot delivered the above "- Your system has at least one broken partition table entry ..." After again booting the dvd to Maintenance Console and removing Airboot I can at least boot ArcaOS.

I can only guess that something is wrong with the Airboot configuration as there does not seem to be anything wrong with partitions or filesystems in use.

The problem is: How to get rid of the existing Airboot configuration?

Any "cures" out there?


Regards

Pete





137
Multimedia / Re: Updated Uniaud32 build
« on: May 11, 2020, 04:34:00 am »
Hi Paul

I have attached debug-linux-3.5.-log.txt

The uniaud16.sys in use is:-

[M:\MMOS2]bldlevel uniaud16.sys
Build Level Display Facility Version 6.12.675 Sep 25 2001
(C) Copyright IBM Corporation 1993-2001
Signature:       @#Netlabs:1.9.7#@##1## 25 Jun 2017 17:11:40     DAZAR1    ::::7
::@@Universal Audio MMPM/2 Driver for OS/2
Vendor:          Netlabs
Revision:        1.09.7
Date/Time:       25 Jun 2017 17:11:40
Build Machine:   DAZAR1
File Version:    1.9.7
Description:     Universal Audio MMPM/2 Driver for OS/2


The above is from the AN update package Uniaud-20181126.exe


Regards

Pete

138
Multimedia / Re: Updated Uniaud32 build
« on: May 10, 2020, 05:26:50 pm »
Hi Paul

Installed the debug 3.5 build, rebooted, sound seems OK with this build - no obvious problems on limited testing.

Setting vlc to use kai:uniaud results in no sound from vlc; resetting to DART works fine.


Regards

Pete

139
Multimedia / Re: Updated Uniaud32 build
« on: May 10, 2020, 03:09:48 pm »
Hi Paul

The only difference between 3.1.txt and 3.2.txt seems to be:-

   3.1 Control iD: 1 has values set to 0
   3.2  Control iD: 1 has values set to 64.

I would have expected 3.1.txt to show that control with values up to 64 but not 0 as 3.1 produces sound at your end.

It might be worth trying 3.2 with Control ID: 1 values set to 0 - it if works for 3.1...


Regards

Pete




140
Hardware / Re: List of OS/2 Tested/Reported Motherboards
« on: May 10, 2020, 02:16:37 am »
Hi Dariusz

AHCI support works fine - the older eCS/AN  V1.32 driver does not have problems initialising ports whereas the later AN V2.0? drivers seem to have initial problems. However the V2.0? driver does work without problems.

This board uses the AMD990FX/SB950 chipsets, everything works barring USB3 - not the fault of the mainboard  :-)
So, probably worth considering; you may even find a reasonable priced "preowned" board on ebay/amazon.


Good hunting  :-)

Pete

141
Hardware / Re: List of OS/2 Tested/Reported Motherboards
« on: May 10, 2020, 02:00:06 am »
Hi Martin

Processor: AMD FX-4300

SATA controller is the AMD/ATI, the Marvell has only 2 external eSATA ports. Yes, both work "Yes I can use the eSATA as a "regular" SATA controller by connecting an eSATA disk prior to booting; the disk is then treated as a SATA disk - not removeable."

Not tried dual monitors , currently no ambitions in that direction  :-)

Yes to the MMRE.OS2 driver question.

No tricks required to get audio working - even with Pauls linux 3.2 port from this discussion https://www.os2world.com/forum/index.php?topic=2436

I do have 1 usb device attached internally, an EVO Labs Internal Multi Card Reader pci 0x048D:0x1336 - the only problem with internal card readers is that it is necessary to manually Refresh Drives in order to get a card recognised after it is inserted.


Regards

Pete




142
Hardware / Re: List of OS/2 Tested/Reported Motherboards
« on: May 09, 2020, 03:42:42 pm »
Hi Martin

Your list seems to be missing Gigabyte 990FXA-UD3 rev 4.0 which, with the exception of USB3 and eSATA support, works well.  Yes I can use the eSATA as a "regular" SATA controller by connecting an eSATA disk prior to booting; the disk is then treated as a SATA disk - not removeable.

Mainboard webpage may be of interest https://www.gigabyte.com/uk/Motherboard/GA-990FXA-UD3-rev-40#ov

Have attached pci output as 990FXA-UD3_pci_list.txt

Not sure what lsusb is but I don't have that... all relevant usb info should be in the pci report.


Regards

Pete



143
Multimedia / Re: Updated Uniaud32 build
« on: May 09, 2020, 03:03:42 pm »
Hi Paul

Tested uniaud32-linux-3.2-debug.zip on a Gigabyte 990FXA-UD3 mainboard with this onboard sound

 Bus 0 (PCI Express), Device Number 20, Device Function 2
 Vendor 1002h Advanced Micro Devices, Inc. [AMD/ATI]
 Device 4383h SBx00 Azalia (Intel HDA)
 Subsystem ID A1321458h Unknown
 Subsystem Vendor 1458h Gigabyte Technology Co., Ltd
 System IRQ 16, INT# -


Changed driver, rebooted, startup sound played OK, other system sounds play OK, CD playback fine.
Sound from both (s)mplayer and vlc when using kai:DART but not when using kai:uniaud


Used the following command to generate the list of Controls and settings

   [M:\MMOS2]unimix -list > new_driver.lst

Of interest is that the file generated is larger than the unimixer.txt file created when using the above unimix -list command with an earlier driver - v2.02.02 according to the info at the top of unimixer.txt

The reason?

A quick read through comparing both files reveals that new_driver.lst has these 2 sections which are missing in the unimixer.txt file:-

Control ID: 11
Interface: virtual mixer device
Device(client): 0, subdevice (substream) 0
Name: [Headphone Playback Volume]
Index: 0
Element type: integer type
Count of values: 2
Value:
 Bounds: min: 0, max: 64, step: 0
  value 0: 59
  value 1: 59

Control ID: 19
Interface: virtual mixer device
Device(client): 0, subdevice (substream) 0
Name: [Auto-Mute Mode]
Index: 0
Element type: enumerated type
Count of values: 1
Value:
 Bounds: items: 2, item: 0, name: [Disabled]
  value 0: 1


So, on this real hardware the uniaud32-linux-3.2-debug.zip seems to be working fine.

People testing this build who reported no audio may want to double check the mixer settings.
Make sure that the following are set:

[Master Playback Volume] - set fairly high (adjust down to suit if it works)

[Master Playback Switch] - must be On ie value of 1


Attached the trunk-linux-3.2-log.txt in case it is of any interest.


Regards

Pete

144
Hardware / Re: eCS 2.1 Mouse buttons = 0
« on: April 30, 2020, 12:29:10 pm »
Hi Axel

Sounds like something may be screwed up in the config.sys file.

The USBcfg utility should help sort out any USB problems, comes as a Warpin self install package (.WPI) or standard ZIP package:-

https://hobbes.nmsu.edu/download/pub/os2/system/USBcfg082.wpi
or
https://hobbes.nmsu.edu/download/pub/os2/system/USBcfg082.zip

Might be worth bookmarking https://hobbes.nmsu.edu/ as a lot of software is uploaded there.

Make sure your mouse is connected via USB before running USBcfg and, hopefully, any USB (including mouse) issues will be resolved.

Other mouse related lines are

LIBPATH=  This line should contain:  H:\ECS\SYSTEM\AMOUSE;

DEVICE=H:\ECS\SYSTEM\AMouse\AMOUSE.SYS SMP


The drive letter H:  is the drive that the above software is installed to here so will, probably, be different on your system..

Long time ago but I do seem to recall something about AMouse and eCS2.1... possibly duplicate lines in config.sys and/or the SMP parameter missing or incorrect.


Hope the above helps

Pete

145
General Discussion / Re: Old OS/2 user, now newbie!
« on: April 30, 2020, 01:35:34 am »
Hi Axel

Welcome back to the weird and wonderful world of OS/2 and minor variations.

A lot of software ported from linux requires various ported libraries, lots of which are available in rpm packages.
As a linux user you probably have used yum/rpm to (un/)install software and will find a frontend to help with that here https://www.arcanoae.com/resources/downloadables/arca-noae-package-manager/

You may also find that eCS2.1 yum/rpm installation needs updating before looking at what other packages are available.

ArcaOS support is included in a purchase of ArcaOS.

General OS/2, eCS, ArcaOS support/discussion is mainly here with the occasional newsgroup post.


Regards

Pete



146
Internet / Re: The new browser / QT5
« on: April 29, 2020, 01:08:02 pm »
Hi All

Indeed Dave - I suspect Silvan would give about the same answer as Andi, possibly not as politely  ;-)

However, we need to be aware that there will probably be a need to fund a qt6 port in the near future - not sure how near - which starts with people organising funding a little in advance of need. Not my area of expertise so possibly a Roderick/OS2VOICE "project" in the near future...


Regards

Pete



147
Hardware / Re: search for a PC for the next 10 years
« on: April 29, 2020, 12:51:59 pm »
Hi Guillaume

As a result of "Googling" for X570-A Pro I see that Asus and MSI both produce that model number, both using the AMD X570 chipset. If Asus had not added shielding to chipset and rear panel outputs it would be difficult to spot the difference between the boards. Gigabyte also has X570 mainboard variants.

CSM: MSI definitely has a CSM option in the BIOS which I think is still need to boot ArcaOS;.
           I suspect the Asus and Gigabyte boards have but best to check.

USB: USB2 ports should be useable - may be even USB3 in the near future

SATA: should not be a problem

Video: Whether using "On Ryzen" GPU or separate video card your choice is SNAP or Panorama drivers in VESA mode I believe

Audio: Hopefully will work with uniaud drivers

LAN: MSI uses Realtek 8111 which should work with the multimac drivers
          Asus uses Intel I211-AT - no idea if this is currently supported, Sorry.
          Gigabyte uses Intel GbE LAN chip (10/100/1000 Mbit) - no idea if this is currently supported, Sorry.


So, for the Asus and Gigabyte boards you need to check that it has BIOS CSM support and whether there is a driver available for the Intel nics used.


Maybe our resident "Ryzen expert", ivan, can add a little more to the above.

You could email AN to ask about Intel LAN driver support if no-one else can answer here.

The MSI board *looks* like it should work with minimum faffing - shame as I usually prefer Asus or Gigabyte boards myself.


Hope the above is of some help
 
Pete





148
Internet / Re: The new browser / QT5
« on: April 28, 2020, 12:18:21 pm »
Hi All

Looking at Pauls post I guess we should be thinking about porting qt6 rather than finishing qt5...

Any volunteers to tell Silvan?  :-)


Regards

Pete

149
Hardware / Re: OS/2 4.52 Freezes Loading Desktop
« on: April 25, 2020, 04:36:17 am »
Hi Carl

If a driver is causing a problem it is usually best uninstalled.

The "How" bit varies a little...

It is about 20 years since I last booted a "pure" OS/2 installation but think it had an Install/Remove folder somewhere in the Desktop folders. That contains the  Install/Uninstall objects for Device Drivers, Networking and Selective Install/Uninstall.

For sound drivers I think you need to run \mmos2\minstall which consults the control.scr supplied with the driver - should be a copy in the same directory, I think - and then set the number of sound devices to 0 to uninstall. However, it is a long time ago...

Most drivers can be over written be installing later/older version of the driver - should always check any included readme just in case though - and the replacement driver becomes active after a reboot.

A lot of drivers can simply be REM'd in or deleted from the config.sys file to make them inactive after a reboot if testing to see if a driver is causing a problem.

Hopefully others will join in if I have missed anything.


Regards

Pete

150
Hardware / Re: OS/2 4.52 Freezes Loading Desktop
« on: April 25, 2020, 12:50:40 am »
Hi Carl

Hmm... I was going to suggest the 2-09 release but maybe not...

A possible alternative would be the uniaud driver see http://trac.netlabs.org/uniaud - supports a wide range of soundchips but does not have DOS or windows sound support.


Regards

Pete


Pages: 1 ... 8 9 [10] 11 12 ... 73