I’m having QRTP running in it’s own partition.
Today I donloaded the Upgrade to 6.1 found in the QNX repository on the net.
After download, the package manager ran some scripts and finaly
told me all ok.
But after that no click on any button on desktop had any reaction.
Only the launch button opened a menu, but pressing shutdown showed no
reaction
other than closing the menu.
I finaly tried to reboot by pressing HW-reset.
No luck!
After loading the kernel it told me:
Unable to start devc-con
and nothing more.
After that I booted QNX-4.
Looking into the partition QNZ(79) I found no /bin directory anymore.
The other directories were still there.
I’m having QRTP running in it’s own partition.
Today I donloaded the Upgrade to 6.1 found in the QNX repository on the
net.
After download, the package manager ran some scripts and finaly
told me all ok.
But after that no click on any button on desktop had any reaction.
Only the launch button opened a menu, but pressing shutdown showed no
reaction
other than closing the menu.
I finaly tried to reboot by pressing HW-reset.
No luck!
After loading the kernel it told me:
Unable to start devc-con
and nothing more.
After that I booted QNX-4.
Looking into the partition QNZ(79) I found no /bin directory anymore.
The other directories were still there.
I’m experiencing the same problem…
upon loading… received the msg something about devc-con
and then nothing…
I’m using the qnx rtp patch c.
Pls help.
Thank you.
Dzulbokhari
I’m experiencing the same problem…
upon loading… received the msg something about devc-con
and then nothing…
I’m using the qnx rtp patch c upgrading to qnx6.1
Pls help.
Thank you.
Dzulbokhari
“Werner Schweizer” <> W.Schweizer@BigFoot.com> > wrote in message
news:9hk9le$eaj$> 1@inn.qnx.com> …
I’m having QRTP running in it’s own partition.
Today I donloaded the Upgrade to 6.1 found in the QNX repository on the
net.
After download, the package manager ran some scripts and finaly
told me all ok.
But after that no click on any button on desktop had any reaction.
Only the launch button opened a menu, but pressing shutdown showed no
reaction
other than closing the menu.
I finaly tried to reboot by pressing HW-reset.
No luck!
After loading the kernel it told me:
Unable to start devc-con
and nothing more.
After that I booted QNX-4.
Looking into the partition QNZ(79) I found no /bin directory anymore.
The other directories were still there.
I’m having QRTP running in it’s own partition.
Today I donloaded the Upgrade to 6.1 found in the QNX repository on the net.
After download, the package manager ran some scripts and finaly
told me all ok.
But after that no click on any button on desktop had any reaction.
Only the launch button opened a menu, but pressing shutdown showed no
reaction
other than closing the menu.
I finaly tried to reboot by pressing HW-reset.
No luck!
After loading the kernel it told me:
Unable to start devc-con
and nothing more.
You’re not alone. I had RTP patch C loaded on a partition and did the
upgrade to 6.1. I got the same reaction from RTP after the install was
completed. I got the same behavior after hard rebooting, “Unable to
start devc-con”.
I’m having QRTP running in it’s own partition.
Today I donloaded the Upgrade to 6.1 found in the QNX repository on the net.
After download, the package manager ran some scripts and finaly
told me all ok.
But after that no click on any button on desktop had any reaction.
Only the launch button opened a menu, but pressing shutdown showed no
reaction
other than closing the menu.
I finaly tried to reboot by pressing HW-reset.
No luck!
After loading the kernel it told me:
Unable to start devc-con
and nothing more.
You’re not alone. I had RTP patch C loaded on a partition and did the
upgrade to 6.1. I got the same reaction from RTP after the install was
completed. I got the same behavior after hard rebooting, “Unable to
start devc-con”.
So, QNX, any ideas how to fix this?
We have discovered what the problem is and will fix it immediately. We
will
also post a boot floppy image that will fix the package file on your
system
so that you and everyone else who has encountered this problem can get
QNX
up and running again. Sorry for the inconvenience.
I’m having QRTP running in it’s own partition.
Today I donloaded the Upgrade to 6.1 found in the QNX repository on the
net.
After download, the package manager ran some scripts and finaly
told me all ok.
But after that no click on any button on desktop had any reaction.
Only the launch button opened a menu, but pressing shutdown showed no
reaction
other than closing the menu.
I finaly tried to reboot by pressing HW-reset.
No luck!
After loading the kernel it told me:
Unable to start devc-con
and nothing more.
After that I booted QNX-4.
Looking into the partition QNZ(79) I found no /bin directory anymore.
The other directories were still there.
Does this happen with just the update? Or does it also happen with a clean
install?
Thanks
“Werner Schweizer” <> W.Schweizer@BigFoot.com> > wrote in message
news:9hk9le$eaj$> 1@inn.qnx.com> …
I’m having QRTP running in it’s own partition.
Today I donloaded the Upgrade to 6.1 found in the QNX repository on the
net.
After download, the package manager ran some scripts and finaly
told me all ok.
But after that no click on any button on desktop had any reaction.
Only the launch button opened a menu, but pressing shutdown showed no
reaction
other than closing the menu.
I finaly tried to reboot by pressing HW-reset.
No luck!
After loading the kernel it told me:
Unable to start devc-con
and nothing more.
After that I booted QNX-4.
Looking into the partition QNZ(79) I found no /bin directory anymore.
The other directories were still there.
From hanging on the QNX Chat on the QNXStart IRC server, apparently this is
a problem when you use the web-based updated from 6.0, but doesn’t happen
when you update with the package manager from the ISO. But everyone seems
to want you to do a totally clean install; bleh
I had Patch B installed and after the upgrade the bootloader did hang. I
could boot anyway with the installation floppy.
“Me” <> paul.ryan2@nospam.virgin.net> > schrieb im Newsbeitrag
news:9hutso$q8q$> 1@inn.qnx.com> …
Everyone seems to have had Patch “C” installed previous to 6.1 upgrade
falling over. Is the same true of a Patch “B” installation upgrading to
6.1?
Yes I know Chalz. I tried all three installation procedures, Windows
install, CD-ROM install and upgrade. I can finally boot into 6.1 but there
are still problems. So I can’t use my PS/2 mouse anymore (never had any
problems with it in any other either commercial or alternative OS) and
PPPoE still doesn’t work. But now I got a nifty pointer cam to not getting
bored until 6.1.1 Seems like QSSL have foreseen that and introduced a
third digit in the version number.
From hanging on the QNX Chat on the QNXStart IRC server, apparently this
is
a problem when you use the web-based updated from 6.0, but doesn’t happen
when you update with the package manager from the ISO. But everyone seems
to want you to do a totally clean install; bleh >
“Peter Kleinstück” <> pk@netfight.de> > wrote in message
news:9hvfm7$7da$> 1@inn.qnx.com> …
I had Patch B installed and after the upgrade the bootloader did hang. I
could boot anyway with the installation floppy.
“Me” <> paul.ryan2@nospam.virgin.net> > schrieb im Newsbeitrag
news:9hutso$q8q$> 1@inn.qnx.com> …
Everyone seems to have had Patch “C” installed previous to 6.1 upgrade
falling over. Is the same true of a Patch “B” installation upgrading
to
6.1?
Yes I know Chalz. I tried all three installation procedures, Windows
install, CD-ROM install and upgrade. I can finally boot into 6.1 but there
are still problems. So I can’t use my PS/2 mouse anymore (never had any
problems with it in any other either commercial or alternative OS) and
PPPoE still doesn’t work. But now I got a nifty pointer cam to not getting
bored until 6.1.1 > > Seems like QSSL have foreseen that and introduced a
third digit in the version number.
“Sir Charles” <> nospam@chalz-of-internetusa.net> > schrieb im Newsbeitrag
news:9hvui8$g3m$> 2@inn.qnx.com> …
From hanging on the QNX Chat on the QNXStart IRC server, apparently this
is
a problem when you use the web-based updated from 6.0, but doesn’t
happen
when you update with the package manager from the ISO. But everyone
seems
to want you to do a totally clean install; bleh >
“Peter Kleinstück” <> pk@netfight.de> > wrote in message
news:9hvfm7$7da$> 1@inn.qnx.com> …
I had Patch B installed and after the upgrade the bootloader did hang.
I
could boot anyway with the installation floppy.
“Me” <> paul.ryan2@nospam.virgin.net> > schrieb im Newsbeitrag
news:9hutso$q8q$> 1@inn.qnx.com> …
Everyone seems to have had Patch “C” installed previous to 6.1
upgrade
falling over. Is the same true of a Patch “B” installation upgrading
to
6.1?
Yes I know Chalz. I tried all three installation procedures, Windows
install, CD-ROM install and upgrade. I can finally boot into 6.1 but there
are still problems. So I can’t use my PS/2 mouse anymore (never had any
problems with it in any other either commercial or alternative OS) and
PPPoE still doesn’t work. But now I got a nifty pointer cam to not getting
Can you describe your PPPoE problem, so maybe we can look into it?
-xtang
bored until 6.1.1 > > Seems like QSSL have foreseen that and introduced a
third digit in the version number.
OK, here again: I installed QNX (fresh base install from CD-ROM), after
reboot I started the network configuration, added a new PPPoE DialUp
connection. Then when I wanted to connect to ISP the terminal window shows
me pppoed is started, the npm-pppoe.so is properly mounted and it gets
indeed a session with the ISP but as soon as pppd is started (“ppp0 <->
ppp_en”) I get a “Fatal Signal 11”. I have then to restart the network stack
(“io-net -d tulip -p ttcpip -p pppmgr -p pppoe”) before I can do the next
try. I use the tulip driver with a SMC 21041-based network card but another
guy with a Realtek 8139 has exactly the same problem. Both cards are PCI and
detected at bootup and the proper driver is started. My card was enabled
(phlip checkbox) and had IP adress 10.0.0.1, subnetmask 255.0.0.0, gateway
left blank.
“Peter Kleinstück” <> pk@netfight.de> > wrote:
Yes I know Chalz. I tried all three installation procedures, Windows
install, CD-ROM install and upgrade. I can finally boot into 6.1 but
there
are still problems. So I can’t use my PS/2 mouse anymore (never had any
problems with it in any other either commercial or alternative OS) and
PPPoE still doesn’t work. But now I got a nifty pointer cam to not
getting
Can you describe your PPPoE problem, so maybe we can look into it?
-xtang
bored until 6.1.1 > > Seems like QSSL have foreseen that and introduced a
third digit in the version number.
OK, here again: I installed QNX (fresh base install from CD-ROM), after
reboot I started the network configuration, added a new PPPoE DialUp
connection. Then when I wanted to connect to ISP the terminal window shows
me pppoed is started, the npm-pppoe.so is properly mounted and it gets
indeed a session with the ISP but as soon as pppd is started (“ppp0 ←
ppp_en”) I get a “Fatal Signal 11”. I have then to restart the network stack
Hm, do you by any chance using chap (/etc/ppp/chap-secret) ?
I wonder you just hit a but we’ve descovered recently. I will
see if I could get you a new pppd for try.
-xtang
(“io-net -d tulip -p ttcpip -p pppmgr -p pppoe”) before I can do the next
try. I use the tulip driver with a SMC 21041-based network card but another
guy with a Realtek 8139 has exactly the same problem. Both cards are PCI and
detected at bootup and the proper driver is started. My card was enabled
(phlip checkbox) and had IP adress 10.0.0.1, subnetmask 255.0.0.0, gateway
left blank.
Peter
“Xiaodan Tang” <> xtang@qnx.com> > schrieb im Newsbeitrag
news:9i06u4$ltr$> 1@nntp.qnx.com> …
“Peter Kleinstück” <> pk@netfight.de> > wrote:
Yes I know Chalz. I tried all three installation procedures, Windows
install, CD-ROM install and upgrade. I can finally boot into 6.1 but
there
are still problems. So I can’t use my PS/2 mouse anymore (never had any
problems with it in any other either commercial or alternative OS) and
PPPoE still doesn’t work. But now I got a nifty pointer cam to not
getting
Can you describe your PPPoE problem, so maybe we can look into it?
-xtang
bored until 6.1.1 > > Seems like QSSL have foreseen that and introduced a
third digit in the version number.
“Peter Kleinstück” <> pk@netfight.de> > wrote:
OK, here again: I installed QNX (fresh base install from CD-ROM), after
reboot I started the network configuration, added a new PPPoE DialUp
connection. Then when I wanted to connect to ISP the terminal window
shows
me pppoed is started, the npm-pppoe.so is properly mounted and it gets
indeed a session with the ISP but as soon as pppd is started (“ppp0 ←
ppp_en”) I get a “Fatal Signal 11”. I have then to restart the network
stack
Hm, do you by any chance using chap (/etc/ppp/chap-secret) ?
I wonder you just hit a but we’ve descovered recently. I will
see if I could get you a new pppd for try.
-xtang
(“io-net -d tulip -p ttcpip -p pppmgr -p pppoe”) before I can do the
next
try. I use the tulip driver with a SMC 21041-based network card but
another
guy with a Realtek 8139 has exactly the same problem. Both cards are PCI
and
detected at bootup and the proper driver is started. My card was enabled
(phlip checkbox) and had IP adress 10.0.0.1, subnetmask 255.0.0.0,
gateway
left blank.
Peter
“Xiaodan Tang” <> xtang@qnx.com> > schrieb im Newsbeitrag
news:9i06u4$ltr$> 1@nntp.qnx.com> …
“Peter Kleinstück” <> pk@netfight.de> > wrote:
Yes I know Chalz. I tried all three installation procedures, Windows
install, CD-ROM install and upgrade. I can finally boot into 6.1 but
there
are still problems. So I can’t use my PS/2 mouse anymore (never had
any
problems with it in any other either commercial or alternative OS)
and
PPPoE still doesn’t work. But now I got a nifty pointer cam to not
getting
Can you describe your PPPoE problem, so maybe we can look into it?
-xtang
bored until 6.1.1 > > Seems like QSSL have foreseen that and
introduced a
third digit in the version number.
\
Just wondering what I can do to boot back into my disk. I upgraded from
Patch B using the ISO image and I ended up with the “Unable to start
devc-con” message as well. What’s the suggested fix for this? I’d
rather not re-install over the image that’s already there…
Thanks
Robert Craig
Hardware Support Account wrote:
Hi Dale,
This just happens with the update. A clean install doesn’t have any
known problems.
Erick.
Dale Frameli <> dframeli@texas.net> > wrote:
Does this happen with just the update? Or does it also happen with a clean
install?
Thanks
“Werner Schweizer” <> W.Schweizer@BigFoot.com> > wrote in message
news:9hk9le$eaj$> 1@inn.qnx.com> …
I’m having QRTP running in it’s own partition.
Today I donloaded the Upgrade to 6.1 found in the QNX repository on the
net.
After download, the package manager ran some scripts and finaly
told me all ok.
But after that no click on any button on desktop had any reaction.
Only the launch button opened a menu, but pressing shutdown showed no
reaction
other than closing the menu.
I finaly tried to reboot by pressing HW-reset.
No luck!
After loading the kernel it told me:
Unable to start devc-con
and nothing more.
After that I booted QNX-4.
Looking into the partition QNZ(79) I found no /bin directory anymore.
The other directories were still there.
Look for a fix to this problem which should be posted at QDN http://qdn.qnx.com on Friday.
Robert Craig wrote:
Just wondering what I can do to boot back into my disk. I upgraded from
Patch B using the ISO image and I ended up with the “Unable to start
devc-con” message as well. What’s the suggested fix for this? I’d
rather not re-install over the image that’s already there…
Thanks
Robert Craig
Hardware Support Account wrote:
Hi Dale,
This just happens with the update. A clean install doesn’t have any
known problems.
Erick.
Dale Frameli <> dframeli@texas.net> > wrote:
Does this happen with just the update? Or does it also happen with a clean
install?
Thanks
“Werner Schweizer” <> W.Schweizer@BigFoot.com> > wrote in message
news:9hk9le$eaj$> 1@inn.qnx.com> …
I’m having QRTP running in it’s own partition.
Today I donloaded the Upgrade to 6.1 found in the QNX repository on the
net.
After download, the package manager ran some scripts and finaly
told me all ok.
But after that no click on any button on desktop had any reaction.
Only the launch button opened a menu, but pressing shutdown showed no
reaction
other than closing the menu.
I finaly tried to reboot by pressing HW-reset.
No luck!
After loading the kernel it told me:
Unable to start devc-con
and nothing more.
After that I booted QNX-4.
Looking into the partition QNZ(79) I found no /bin directory anymore.
The other directories were still there.
Look for a fix to this problem which should be posted at QDN http://qdn.qnx.com > on Friday.
Robert Craig wrote:
Just wondering what I can do to boot back into my disk. I upgraded from
Patch B using the ISO image and I ended up with the “Unable to start
devc-con” message as well. What’s the suggested fix for this? I’d
rather not re-install over the image that’s already there…
Thanks
Robert Craig
Hardware Support Account wrote:
Hi Dale,
This just happens with the update. A clean install doesn’t have any
known problems.
Erick.
Dale Frameli <> dframeli@texas.net> > wrote:
Does this happen with just the update? Or does it also happen with a clean
install?
Thanks
“Werner Schweizer” <> W.Schweizer@BigFoot.com> > wrote in message
news:9hk9le$eaj$> 1@inn.qnx.com> …
I’m having QRTP running in it’s own partition.
Today I donloaded the Upgrade to 6.1 found in the QNX repository on the
net.
After download, the package manager ran some scripts and finaly
told me all ok.
But after that no click on any button on desktop had any reaction.
Only the launch button opened a menu, but pressing shutdown showed no
reaction
other than closing the menu.
I finaly tried to reboot by pressing HW-reset.
No luck!
After loading the kernel it told me:
Unable to start devc-con
and nothing more.
After that I booted QNX-4.
Looking into the partition QNZ(79) I found no /bin directory anymore.
The other directories were still there.
It happend with an update on version 6.0C with the package manager.
Now I’m trying to burn the whole image onto a CD to be able to do a complete
install.
No success yet. My WinOnCD 3.8 doesn’t know the downloaded image qnxrtp.iso.
If I rename it to qnxrtp.c2d (the default extension for CD-images in
WinOnCD)
it reports a bad format.
Does this happen with just the update? Or does it also happen with a
clean
install?
Thanks
“Werner Schweizer” <> W.Schweizer@BigFoot.com> > wrote in message
news:9hk9le$eaj$> 1@inn.qnx.com> …
I’m having QRTP running in it’s own partition.
Today I donloaded the Upgrade to 6.1 found in the QNX repository on the
net.
After download, the package manager ran some scripts and finaly
told me all ok.
But after that no click on any button on desktop had any reaction.
Only the launch button opened a menu, but pressing shutdown showed no
reaction
other than closing the menu.
I finaly tried to reboot by pressing HW-reset.
No luck!
After loading the kernel it told me:
Unable to start devc-con
and nothing more.
After that I booted QNX-4.
Looking into the partition QNZ(79) I found no /bin directory anymore.
The other directories were still there.
