QNX RTOS v4 [EOL]/Discussion/General/I want to test new Fsys.ahci driver/List of Posts
 
Forum Topic - I want to test new Fsys.ahci driver: (10 Items)
   
Update
kbob kbob(deleted)
11/14/2011 5:51 AM
post90068
I want to test new Fsys.ahci driver   
When I try to test new Fsys.ahci driver, I found that I need to add Fsys.ahci driver into qnxboot.144.2011 floppy image 
file. After boot standart QNX4 CD I have only Fsys.aha2scsi, Fsys.aha4scsi, Fsys.aha7scsi, Fsys.amdscsi, Fsys.atapy, 
Fsys.floppy, Fsys.mitsumi, Fsys.ncr8scsi, Fsys.umass drivers.

Mounting qnxboot.144.2011 as loop device gave me absolutely messed and meaningless filenames in mount point directory. 
Very strange.
How can I rebuild qnxboot.144.2011 file?
Pavel Kozlov(deleted)
11/14/2011 7:44 AM
post90073
Re: I want to test new Fsys.ahci driver   
Hi,

The qnxboot.144.2011 image doesn't have a file system, it contains raw
encrypted image so you can't mount it.  The qnxboot.144.2011 is a part
of Product Suite environment and there is no simple way to rebuild it.
I suppose that Fsys.ahci will be included to Product Suite 2012 and
qnxboot.144.2012 will contain it.
If you want to test new Fsys.ahci driver the easiest way is to prepare
your own bootable usb-flash or floppy with the Fsys.ahci.


Regards,
Pavel

> When I try to test new Fsys.ahci driver, I found that I need to add Fsys.ahci driver into qnxboot.144.2011 floppy 
image file. After boot standart QNX4 CD I have only Fsys.aha2scsi, Fsys.aha4scsi, Fsys.aha7scsi, Fsys.amdscsi, Fsys.
atapy, Fsys.floppy, Fsys.mitsumi, Fsys.ncr8scsi, Fsys.umass drivers.
>
> Mounting qnxboot.144.2011 as loop device gave me absolutely messed and meaningless filenames in mount point directory.
 Very strange.
> How can I rebuild qnxboot.144.2011 file?
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post90068
>
>
kbob kbob(deleted)
11/15/2011 2:48 AM
post90090
Re: I want to test new Fsys.ahci driver   
Install QNX4 on other motherboard. Rebuild boot image with Fsys.ahci

/boot/sys/boot
$ /boot/sys/boot -v

/boot/sys/Proc32
$ /boot/sys/Proc32 -l 1

/boot/sys/Slib32
$ /boot/sys/Slib32

/boot/sys/Slib16
$ /boot/sys/Slib16

/bin/Fsys
$ /bin/Fsys -Hdisk160

/bin/Fsys.ahci
$ /bin/Fsys.ahci fsys -Ndsk0 -n0=hd0. -n5=cd0.

/bin/mount
$ /bin/mount -p /dev/hd0.1 /dev/hd0.1t77 /

/bin/sinit
$ /bin/sinit TERM=qnxm

Connect hard disk to P8H67-V motherboard (as second drive).

When booting
/bin/Fsys.ahci terminated (SIGSEGV) at 00D1:0000040B
Pavel Kozlov(deleted)
11/15/2011 3:36 AM
post90091
Re: I want to test new Fsys.ahci driver   
Hi,

It seems that your PCI BIOS is not compatible with Intel 386 protected
mode. If so then any QNX4 program that call PCI BIOS functions
(Fsys.atapi, Fsys.ahci, io-usb, network drivers, etc.) will be
terminated with SIGSEGV approximately at the same place (00D1:0000040B).
To cheek this assumption include into your boot image, for example
Fsys.atapi, instead of Fsys.ahci.
If my assumption is correct then the only way to fix this is to
upgrade/downgrade BIOS.


> Install QNX4 on other motherboard. Rebuild boot image with Fsys.ahci
>
> /boot/sys/boot
> $ /boot/sys/boot -v
>
> /boot/sys/Proc32
> $ /boot/sys/Proc32 -l 1
>
> /boot/sys/Slib32
> $ /boot/sys/Slib32
>
> /boot/sys/Slib16
> $ /boot/sys/Slib16
>
> /bin/Fsys
> $ /bin/Fsys -Hdisk160
>
> /bin/Fsys.ahci
> $ /bin/Fsys.ahci fsys -Ndsk0 -n0=hd0. -n5=cd0.
>
> /bin/mount
> $ /bin/mount -p /dev/hd0.1 /dev/hd0.1t77 /
>
> /bin/sinit
> $ /bin/sinit TERM=qnxm
>
> Connect hard disk to P8H67-V motherboard (as second drive).
>
> When booting
> /bin/Fsys.ahci terminated (SIGSEGV) at 00D1:0000040B
>
>
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post90090
>
>
kbob kbob(deleted)
11/15/2011 4:04 AM
post90092
Re: I want to test new Fsys.ahci driver   
Yes, Fsys.atapi included in .altboot terminated with SIGSEGV at same address too.
io-usb also terminated with SIGSEGV

When I try to start
Fsys.ahci &
unknown driver '&' before SIGSEGV
kbob kbob(deleted)
11/17/2011 9:20 PM
post90181
Re: I want to test new Fsys.ahci driver   
EFI BIOS is not compatible with QNX4
kbob kbob(deleted)
02/28/2012 4:49 AM
post91829
Re: I want to test new Fsys.ahci driver   
With new proc32 -E0 option
Fsys.ahci driver works fine.

Thank you very much.
Dmitriy Domaratsky
02/19/2014 5:38 AM
post108885
Re: I want to test new Fsys.ahci driver   
> With new proc32 -E0 option
> Fsys.ahci driver works fine.
> 
> Thank you very much.


I use .boot with -P option (with old proc32 without -E0) and works fine.
kbob kbob(deleted)
02/28/2012 5:30 AM
post91830
Re: I want to test new Fsys.ahci driver   
SATA DVD-ROM works too.
Egor Tkachenko(deleted)
04/30/2013 5:44 AM
post100992
Re: I want to test new Fsys.ahci driver   
the MB P8H67-V you are using is LGA1155. Im interesting which kind of proccesor are you using? Intelhd graphics supports
 only Device ID 0x0042h and 0x0046x and its i3-5x0 proccessors with socket 1156. 
Im trying to boot qnx on new hardware and if you could make intelhd graphics work with new proccessors then Id like to 
know how and wich proccessor.

Thank you

Return