I have updated two different machines and ran into the following problems as of yesterday and today:
1) ASUS P5GC-MX/1333
(a) If booting latest kernel: 2.6.26.3-29.f9.i686:
- No Gui startup after udev - mkrootdev: could not determine nfs root target - mount: missing mount point - setuproot: moving /dev failed (No such file or directory) : error mounting /proc (No such file or directory) : error mounting /sys (No such file or directory) : error mounting /selinux (No such file or directory) - switchroot: Mount failed - system hangs
(b) If booting previous kernel 2.6.25.14-108.f9.i686:
+ Worked with updates prior to that of last week or so, startup/login gui worked fine, however:
- Due to current updates (last few days): - Startup gui fails to come up just after udev, but login gui works. - (yesterday) Startup reported 3 kmod warnings (files were missing and startup was unable to force kmod builds) but continued to login gui. - (today): yum updated with several new kmods, then rebooted: + Startup forced kmod rebuild but kmod-ndiswrapper failed + Startup continued and and gui login came up, but after login: - firefox has installed *many* language plug-ins (that I did not choose) and *everytime* you log in, the extensions dialog pops up - so I disabled all the language plugins I did not need but could not un-install them, and the annoyance stopped.
2) Intel DQ35J0
(a) New kernel in 1a worked and did not have any problems, and it did not hang. (b) Same as 1b above, but using the same kernel as 1a above.
FWIW, Dan
On Mon, 2008-09-29 at 08:11 -0700, Dan Thurman wrote:
- ASUS P5GC-MX/1333
(a) If booting latest kernel: 2.6.26.3-29.f9.i686:
- No Gui startup after udev
- mkrootdev: could not determine nfs root target
- mount: missing mount point
- setuproot: moving /dev failed (No such file or directory) : error mounting /proc (No such file or directory) : error mounting /sys (No such file or directory) : error mounting /selinux (No such file or directory)
- switchroot: Mount failed
- system hangs
I had this same problem... changed to mandriva for the moment.
2008/9/29 Renich Bon Ciric renich@woralelandia.com:
On Mon, 2008-09-29 at 08:11 -0700, Dan Thurman wrote:
- ASUS P5GC-MX/1333
(a) If booting latest kernel: 2.6.26.3-29.f9.i686:
- No Gui startup after udev
- mkrootdev: could not determine nfs root target
- mount: missing mount point
- setuproot: moving /dev failed (No such file or directory) : error mounting /proc (No such file or directory) : error mounting /sys (No such file or directory) : error mounting /selinux (No such file or directory)
- switchroot: Mount failed
- system hangs
I had this same problem... changed to mandriva for the moment.
Renich Bon Ciric http://www.woralelandia.com/
# Facebook http://www.facebook.com/profile.php?id=674792460
# introbella (band) http://www.introbella.com/
# Smolt uuid (pub_3e18efc2-dee4-459f-8d40-ddf489be817d) http://www.smolts.org/client/show/?uuid=pub_3e18efc2-dee4-459f-8d40-ddf489be...
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
did you file a bug???
Antonio M wrote:
2008/9/29 Renich Bon Ciric renich@woralelandia.com:
On Mon, 2008-09-29 at 08:11 -0700, Dan Thurman wrote:
- ASUS P5GC-MX/1333
(a) If booting latest kernel: 2.6.26.3-29.f9.i686:
- No Gui startup after udev
- mkrootdev: could not determine nfs root target
- mount: missing mount point
- setuproot: moving /dev failed (No such file or directory) : error mounting /proc (No such file or directory) : error mounting /sys (No such file or directory) : error mounting /selinux (No such file or directory)
- switchroot: Mount failed
- system hangs
I had this same problem... changed to mandriva for the moment.
did you file a bug???
No. I would even know how to report this and what I need to provide exactly that would aide in getting this issue resolved.
I have removed and reinstalled the latest kernel (2.6.26.3-29.f9.i686) and it still hangs. I cannot use it and I am forced to use the previous kernel (2.6.25.14-108.f9.i686)
I have removed akmod and kmod, disabled livna, rebooted and interestingly the kmod warnings no longer appear during bootup and so it appears to have nothing to do with corrupting the startup gui, so it appears to be a seperate issue. Also, interestingly, I cannot reinstall akmod/kmod (with livna disabled) because akmod/kmod are not available with the fedora-only repos.
So, I re-enabled the livna repos, attempted to reinstall akmod/kmod and I get for every kmod module, errors similar to the following:
Error: Missing Dependency: kernel-uname-r = 2.6.25.3-18.fc9.i686 is needed by package kmod-ndiswrapper-2.6.25.3-18.fc9.i686-1.52-31.lvn9.i686 (livna)
Finally, the startup gui is still a very big annoyance for both kernels esp. with my less-experienced fedora users.
When will someone acknowledge if this is bug or not? Only one person acknowledged he had a problem as well as I.
I have already listed the specific motherboards in this posting and it has been a little more than a week with no resolution at this time.
Thanks! Dan
On Wed, 2008-10-01 at 09:24 -0700, Dan Thurman wrote:
Antonio M wrote:
2008/9/29 Renich Bon Ciric renich@woralelandia.com:
On Mon, 2008-09-29 at 08:11 -0700, Dan Thurman wrote:
- ASUS P5GC-MX/1333
(a) If booting latest kernel: 2.6.26.3-29.f9.i686:
- No Gui startup after udev
- mkrootdev: could not determine nfs root target
- mount: missing mount point
- setuproot: moving /dev failed (No such file or directory) : error mounting /proc (No such file or directory) : error mounting /sys (No such file or directory) : error mounting /selinux (No such file or directory)
- switchroot: Mount failed
- system hangs
I had this same problem... changed to mandriva for the moment.
did you file a bug???
No. I would even know how to report this and what I need to provide exactly that would aide in getting this issue resolved.
I have removed and reinstalled the latest kernel (2.6.26.3-29.f9.i686) and it still hangs. I cannot use it and I am forced to use the previous kernel (2.6.25.14-108.f9.i686)
I have removed akmod and kmod, disabled livna, rebooted and interestingly the kmod warnings no longer appear during bootup and so it appears to have nothing to do with corrupting the startup gui, so it appears to be a seperate issue. Also, interestingly, I cannot reinstall akmod/kmod (with livna disabled) because akmod/kmod are not available with the fedora-only repos.
So, I re-enabled the livna repos, attempted to reinstall akmod/kmod and I get for every kmod module, errors similar to the following:
Error: Missing Dependency: kernel-uname-r = 2.6.25.3-18.fc9.i686 is needed by package kmod-ndiswrapper-2.6.25.3-18.fc9.i686-1.52-31.lvn9.i686 (livna)
Finally, the startup gui is still a very big annoyance for both kernels esp. with my less-experienced fedora users.
When will someone acknowledge if this is bug or not? Only one person acknowledged he had a problem as well as I.
I have already listed the specific motherboards in this posting and it has been a little more than a week with no resolution at this time.
---- The list provides community assistance when / where possible. It's a great place for what often proves to be less than fully qualified help.
Bugzilla provides interaction with the Fedora developers/packagers. It's the perfect place for qualified help.
Livna has their own support (Bugzilla) http://rpm.livna.org/rlowiki/Bugzilla
It seems that if a number of other people on this list aren't experiencing the same problems as you, the problems are somewhat unique to you and the list may not be capable of providing the assistance that you need.
Craig
Craig White wrote:
On Wed, 2008-10-01 at 09:24 -0700, Dan Thurman wrote:
Antonio M wrote:
2008/9/29 Renich Bon Ciric renich@woralelandia.com:
On Mon, 2008-09-29 at 08:11 -0700, Dan Thurman wrote:
- ASUS P5GC-MX/1333
(a) If booting latest kernel: 2.6.26.3-29.f9.i686:
- No Gui startup after udev
- mkrootdev: could not determine nfs root target
- mount: missing mount point
- setuproot: moving /dev failed (No such file or directory) : error mounting /proc (No such file or directory) : error mounting /sys (No such file or directory) : error mounting /selinux (No such file or
directory)
- switchroot: Mount failed - system hangsI had this same problem... changed to mandriva for the moment.
did you file a bug???
No. I would even know how to report this and what I need to provide exactly that would aide in getting this issue resolved.
I have removed and reinstalled the latest kernel (2.6.26.3-29.f9.i686) and it still hangs. I cannot use it and I am forced to use the
previous
kernel (2.6.25.14-108.f9.i686)
I have removed akmod and kmod, disabled livna, rebooted and
interestingly
the kmod warnings no longer appear during bootup and so it appears
to have
nothing to do with corrupting the startup gui, so it appears to be a seperate issue. Also, interestingly, I cannot reinstall akmod/kmod (with livna
disabled)
because akmod/kmod are not available with the fedora-only repos.
So, I re-enabled the livna repos, attempted to reinstall akmod/kmod and I get for every kmod module, errors similar to the following:
Error: Missing Dependency: kernel-uname-r = 2.6.25.3-18.fc9.i686 is
needed
by package kmod-ndiswrapper-2.6.25.3-18.fc9.i686-1.52-31.lvn9.i686
(livna)
Finally, the startup gui is still a very big annoyance for both kernels esp. with my less-experienced fedora users.
When will someone acknowledge if this is bug or not? Only one person acknowledged he had a problem as well as I.
I have already listed the specific motherboards in this posting and it has been a little more than a week with no resolution at this time.
The list provides community assistance when / where possible. It's a great place for what often proves to be less than fully qualified help.
Bugzilla provides interaction with the Fedora developers/packagers. It's the perfect place for qualified help.
Livna has their own support (Bugzilla) http://rpm.livna.org/rlowiki/Bugzilla
It seems that if a number of other people on this list aren't experiencing the same problems as you, the problems are somewhat unique to you and the list may not be capable of providing the assistance that you need.
Craig
What has changed? I mean, if there is a new list (I noticed that this list no longer says: For Fedora Users", where has this list moved to so that I can get a more technical level of support?
Thanks! Dan
On Wed, 2008-10-01 at 09:40 -0700, Dan Thurman wrote:
What has changed? I mean, if there is a new list (I noticed that this list no longer says: For Fedora Users", where has this list moved to so that I can get a more technical level of support?
The only thing that has changed is the name (also I think the list owners, but that's administrivia).
poc
Patrick O'Callaghan wrote:
On Wed, 2008-10-01 at 09:40 -0700, Dan Thurman wrote:
What has changed? I mean, if there is a new list (I noticed that this list no longer says: For Fedora Users", where has this list moved to so that I can get a more technical level of support?
The only thing that has changed is the name (also I think the list owners, but that's administrivia).
poc
Thank you for being helpful! So, this list has not really changed and I can assume that this is the right list for me in terms of reporting potential problem/issue as if for confirmation, before going off and filing off false problem reports into Bugzilla.
Dan
--- On Wed, 10/1/08, Craig White craigwhite@azapple.com wrote:
From: Craig White craigwhite@azapple.com Subject: Re: Updates caused problems... To: dant@cdkkt.com, "Community assistance, encouragement, and advice for using Fedora." fedora-list@redhat.com Date: Wednesday, October 1, 2008, 4:35 PM On Wed, 2008-10-01 at 09:24 -0700, Dan Thurman wrote:
Antonio M wrote:
2008/9/29 Renich Bon Ciric
On Mon, 2008-09-29 at 08:11 -0700, Dan
Thurman wrote:
- ASUS P5GC-MX/1333
(a) If booting latest kernel:
2.6.26.3-29.f9.i686:
- No Gui startup after udev
- mkrootdev: could not determine nfs
root target
- mount: missing mount point
- setuproot: moving /dev failed (No
such file or directory)
: error mounting /proc (Nosuch file or directory)
: error mounting /sys (Nosuch file or directory)
: error mounting /selinux(No such file or directory)
- switchroot: Mount failed - system hangsI had this same problem... changed to
mandriva for the moment.
did you file a bug???
No. I would even know how to report this and what I
need
to provide exactly that would aide in getting this
issue resolved.
I have removed and reinstalled the latest kernel
(2.6.26.3-29.f9.i686)
and it still hangs. I cannot use it and I am forced
to use the previous
kernel (2.6.25.14-108.f9.i686)
I have removed akmod and kmod, disabled livna,
rebooted and interestingly
the kmod warnings no longer appear during bootup and
so it appears to have
nothing to do with corrupting the startup gui, so it
appears to be a
seperate issue. Also, interestingly, I cannot reinstall akmod/kmod
(with livna disabled)
because akmod/kmod are not available with the
fedora-only repos.
So, I re-enabled the livna repos, attempted to
reinstall akmod/kmod and
I get for every kmod module, errors similar to the
following:
Error: Missing Dependency: kernel-uname-r =
2.6.25.3-18.fc9.i686 is needed
by package
kmod-ndiswrapper-2.6.25.3-18.fc9.i686-1.52-31.lvn9.i686 (livna)
Finally, the startup gui is still a very big annoyance
for both
kernels esp. with my less-experienced fedora users.
When will someone acknowledge if this is bug or not?
Only one
person acknowledged he had a problem as well as I.
I have already listed the specific motherboards in
this posting and
it has been a little more than a week with no
resolution at this time.
The list provides community assistance when / where possible. It's a great place for what often proves to be less than fully qualified help.
Bugzilla provides interaction with the Fedora developers/packagers. It's the perfect place for qualified help.
Livna has their own support (Bugzilla) http://rpm.livna.org/rlowiki/Bugzilla
It seems that if a number of other people on this list aren't experiencing the same problems as you, the problems are somewhat unique to you and the list may not be capable of providing the assistance that you need.
Craig
--
I am not a heavy Linux sys admin but I have never had any luck with Linux updates like Fn to (Fn+1)
sooner or later something happens requiring a heavy research project!
Now I save all files I need and load Fedora (n+1) from DVD.
Sure I should have done a
rpmyumsxx -1234 /rtter /dodad/honky tonk blah blah -crunch
and then figure out why that didn't work!
Linux should NOT be a mountain of complexity for those who admire/worship complexity.
I have far more than enough complexity in programming subjects.
Remember, we are defeating Vista and XP Prof and need to make things simple for newbies.
THEN maybe we'll have another 14,000 Munich computer switch to Linux!
fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
On Wed, 2008-10-01 at 09:48 -0700, Fred Silsbee wrote:
--- On Wed, 10/1/08, Craig White craigwhite@azapple.com wrote:
The list provides community assistance when / where possible. It's a great place for what often proves to be less than fully qualified help.
Bugzilla provides interaction with the Fedora developers/packagers. It's the perfect place for qualified help.
Livna has their own support (Bugzilla) http://rpm.livna.org/rlowiki/Bugzilla
It seems that if a number of other people on this list aren't experiencing the same problems as you, the problems are somewhat unique to you and the list may not be capable of providing the assistance that you need.
Craig
--
I am not a heavy Linux sys admin but I have never had any luck with Linux updates like Fn to (Fn+1)
sooner or later something happens requiring a heavy research project!
Now I save all files I need and load Fedora (n+1) from DVD.
Sure I should have done a
rpmyumsxx -1234 /rtter /dodad/honky tonk blah blah -crunch
and then figure out why that didn't work!
Linux should NOT be a mountain of complexity for those who admire/worship complexity.
I have far more than enough complexity in programming subjects.
Remember, we are defeating Vista and XP Prof and need to make things simple for newbies.
THEN maybe we'll have another 14,000 Munich computer switch to Linux!
---- 1 - you are bringing in an issue separate from the OP
2 - many of us have had no problems updating from release to release but yes, a clean install is clearly easier for the less than technically inclined. I think Ubuntu is intended to be the release for the non-inclined/less technical users.
3 - Fedora is not intended to replace Windows on anything and I have yet to see that to be a stated goal for Fedora. While Fedora tries to make things simpler, it's not a primary objective.
I think you need to review the 'overview' page for Fedora...
http://fedoraproject.org/wiki/Overview
The primary objective...the first sentence. "Fedora is all about freedom and rapid innovation."
Rapid innovation, not making a platform to easily create Windows converts.
Craig
Craig White wrote:
On Wed, 2008-10-01 at 09:24 -0700, Dan Thurman wrote:
Antonio M wrote:
2008/9/29 Renich Bon Ciric renich@woralelandia.com:
On Mon, 2008-09-29 at 08:11 -0700, Dan Thurman wrote:
- ASUS P5GC-MX/1333
(a) If booting latest kernel: 2.6.26.3-29.f9.i686:
- No Gui startup after udev
- mkrootdev: could not determine nfs root target
- mount: missing mount point
- setuproot: moving /dev failed (No such file or directory) : error mounting /proc (No such file or directory) : error mounting /sys (No such file or directory) : error mounting /selinux (No such file or
directory)
- switchroot: Mount failed - system hangsI had this same problem... changed to mandriva for the moment.
did you file a bug???
No. I would even know how to report this and what I need to provide exactly that would aide in getting this issue resolved.
I have removed and reinstalled the latest kernel (2.6.26.3-29.f9.i686) and it still hangs. I cannot use it and I am forced to use the
previous
kernel (2.6.25.14-108.f9.i686)
I have removed akmod and kmod, disabled livna, rebooted and
interestingly
the kmod warnings no longer appear during bootup and so it appears
to have
nothing to do with corrupting the startup gui, so it appears to be a seperate issue. Also, interestingly, I cannot reinstall akmod/kmod (with livna
disabled)
because akmod/kmod are not available with the fedora-only repos.
So, I re-enabled the livna repos, attempted to reinstall akmod/kmod and I get for every kmod module, errors similar to the following:
Error: Missing Dependency: kernel-uname-r = 2.6.25.3-18.fc9.i686 is
needed
by package kmod-ndiswrapper-2.6.25.3-18.fc9.i686-1.52-31.lvn9.i686
(livna)
Finally, the startup gui is still a very big annoyance for both kernels esp. with my less-experienced fedora users.
When will someone acknowledge if this is bug or not? Only one person acknowledged he had a problem as well as I.
I have already listed the specific motherboards in this posting and it has been a little more than a week with no resolution at this time.
The list provides community assistance when / where possible. It's a great place for what often proves to be less than fully qualified help.
Bugzilla provides interaction with the Fedora developers/packagers. It's the perfect place for qualified help.
Livna has their own support (Bugzilla) http://rpm.livna.org/rlowiki/Bugzilla
It seems that if a number of other people on this list aren't experiencing the same problems as you, the problems are somewhat unique to you and the list may not be capable of providing the assistance that you need.
Craig
Clearly:
1) Kernel 2.6.26.3-29.f9.i686: Does not work for two different motherboards/systems, nor for: Renich Bon Ciric renich@woralelandia.com so, I do not think this problem is `unique' to me. This kernel is a show-stopper - so I have to revert to the previous kernel version for now and hope a later update will resolve this issue.
2) The startup Gui stopped working due to latest updates (as of last week) and if this is `unique' to me, then I will just ignore this and *maybe* later updates will automagically repair it - as it sits now, it is not a show-stopper because ignoring the startup gui, in the end, the login gui still appears.
3) The livna issue is a seperate issue - and is not a show-stopper as I have removed them (kmod/akmod) and I know I can at least let the livna group know about it. It is obvious to me that kmod-ndiswarpper expects an older kernel (2.6.25.3-18.fc9.i686) which is no longer available in the repos. Many of the other kmods reported many other dependencies as well - so it appears that livna is `out of sync', perhaps but I will resolve this later - and focus on my main issues (1) and (2)
Ignoring the Livna issue, (1) and (2) remains and is unique to Fedora since these kernels comes from the Fedora repos and has nothing to do with Livna (so I think).
Are you are telling me (and others) to use Bugzilla and not to report individual problem issues here in this list because these are `unique' problems? How does one know if they are unique problems before they post it? And even if they are `unique' - what are they supposed to do? What is the point of this mailing list with the following statement:
"Community assistance, encouragement,and advice for using Fedora"
You come across as if to to say: "go to livna" and ignore the the other two problems reported altogether?
This sort of reply does nothing to encourage people like myself to remain a faithful user to Fedora and I am almost beginning to see why, but I am not deterred - just a little bit disappointed.
I would have at least expected a little direction as how to handle each of the problems reported, explain if there is a problem or not, perhaps a link, perhaps what to report, with what expected information, etc, so that at least I am not left perplexed as to what I really need to do next.
Kind regards, Dan
On Wed, 2008-10-01 at 10:38 -0700, Dan Thurman wrote:
Clearly:
Kernel 2.6.26.3-29.f9.i686: Does not work for two different motherboards/systems, nor for: Renich Bon Ciric renich@woralelandia.com so, I do not think this problem is `unique' to me. This kernel is a show-stopper - so I have to revert to the previous kernel version for now and hope a later update will resolve this issue.
The startup Gui stopped working due to latest updates (as of last week) and if this is `unique' to me, then I will just ignore this and *maybe* later updates will automagically repair it - as it sits now, it is
not a show-stopper because ignoring the startup gui, in the end, the login gui still appears.
- The livna issue is a seperate issue - and is not a show-stopper as I have removed them (kmod/akmod) and I know I can at least let the livna group know about it. It is obvious to me that kmod-ndiswarpper expects an older kernel (2.6.25.3-18.fc9.i686) which is no longer available in the repos. Many of the other kmods reported many other dependencies as well - so it appears that livna is `out of sync', perhaps but I will resolve this later - and focus on my main issues (1) and (2)
Ignoring the Livna issue, (1) and (2) remains and is unique to Fedora since these kernels comes from the Fedora repos and has nothing to do with Livna (so I think).
Are you are telling me (and others) to use Bugzilla and not to report individual problem issues here in this list because these are `unique' problems? How does one know if they are unique problems before they post it? And even if they are `unique' - what are they supposed to do? What is the point of this mailing list with the following statement:
"Community assistance, encouragement,and advice for using Fedora"
You come across as if to to say: "go to livna" and ignore the the other two problems reported altogether?
This sort of reply does nothing to encourage people like myself to remain a faithful user to Fedora and I am almost beginning to see why, but I am not deterred - just a little bit disappointed.
I would have at least expected a little direction as how to handle each of the problems reported, explain if there is a problem or not, perhaps a link, perhaps what to report, with what expected information, etc, so that at least I am not left perplexed as to what I really need to do next.
---- OK - I too will ignore the livna items
I think you can lean on the list all you wish. In fact, you seem to lean on the list excessively but as long as people can and will help you out, that's great.
I am not trying to discourage you from using Fedora. This list however does nothing to 'report' problems - that's what bugzilla is for.
Craig
Craig White wrote:
On Wed, 2008-10-01 at 10:38 -0700, Dan Thurman wrote:
Clearly:
Kernel 2.6.26.3-29.f9.i686: Does not work for two different motherboards/systems, nor for: Renich Bon Ciric renich@woralelandia.com so, I do not think this problem is `unique' to me. This kernel is a show-stopper - so I have to revert to the previous kernel version for now and hope a later update will resolve this issue.
The startup Gui stopped working due to latest updates (as of last
week)
and if this is `unique' to me, then I will just ignore this and*maybe*
later updates will automagically repair it - as it sits now, it isnot a show-stopper because ignoring the startup gui, in the end, the
login
gui still appears.
- The livna issue is a seperate issue - and is not a show-stopper
as I have
removed them (kmod/akmod) and I know I can at least let the livna group know about it. It is obvious to me that kmod-ndiswarpper expects an older kernel (2.6.25.3-18.fc9.i686) which is no longer available in the repos. Many of the other kmods reported many other dependencies as well - so it appears that livna is `out ofsync',
perhaps but I will resolve this later - and focus on my main issues (1) and (2)Ignoring the Livna issue, (1) and (2) remains and is unique to Fedora since these kernels comes from the Fedora repos and has nothing to do with Livna (so I think).
Are you are telling me (and others) to use Bugzilla and not to report individual problem issues here in this list because these are `unique' problems? How does one know if they are unique problems before they post it? And even if they are `unique' - what are they supposed to do? What is the point of this mailing list with the following statement:
"Community assistance, encouragement,and advice for using Fedora"
You come across as if to to say: "go to livna" and ignore the the other two problems reported altogether?
This sort of reply does nothing to encourage people like myself to remain a faithful user to Fedora and I am almost beginning to see why, but I am not deterred - just a little bit disappointed.
I would have at least expected a little direction as how to handle each of the problems reported, explain if there is a problem or not, perhaps a link, perhaps what to report, with what expected information, etc, so that at least I am not left perplexed as to what I really
need to do
next.
OK - I too will ignore the livna items
I think you can lean on the list all you wish. In fact, you seem to lean on the list excessively but as long as people can and will help you out, that's great.
I am not trying to discourage you from using Fedora. This list however does nothing to 'report' problems - that's what bugzilla is for.
Craig
Thank you for letting me know how you feel. Perhaps I do lean on this list for the reasons stated (1) to discover if the problem reported has already been reported and/or there is a fix and/or someone is working on it and (2) to let anyone know about it so they can benefit from the posting if it concerns them. I know that many have responded asking for details especially if the problem has been resolved by me or if others have resolved it - a networked community helping each other out which is the benefit of using this list in the first place. IMO, there are a few people esp. newbies, go to a Bugzilla site to search for answers to their specific problems - simply because - it is not that simple to find so this mailing list provides them that "forum" where they can ask about it and hopefully someone might know, and help out.
I have been resistant to using Bugzilla because it is a pain for me since I use it so rarely and trying to fill in the fields for which I have not a clue such as to what product/component the product/issue involves, what relevant data to provide which requires an intimate technical detail level that a professional Fedora expert might know which can be beyond a (semi) newbie's depth. But, I will try with each passing day to `get used to it' and maybe it will become easier over time.
Kind regards, Dan
On Wed, 2008-10-01 at 10:55 -0700, Craig White wrote:
I am not trying to discourage you from using Fedora. This list however does nothing to 'report' problems - that's what bugzilla is for.
Yes and no. The list is useful for saying "this doesn't work for me, has anyone had this problem?". BZ is for reporting genuine bugs, preferably once you've determined that they really are bugs.
It can be a fine line of course.
poc
Daniel B. Thurman wrote:
If booting latest kernel: 2.6.26.3-29.f9.i686 (or newer):
- No Gui startup after udev
- mkrootdev: could not determine nfs root target
- mount: missing mount point
- setuproot: moving /dev failed (No such file or directory) : error mounting /proc (No such file or directory) : error mounting /sys (No such file or directory) : error mounting /selinux (No such file or directory)
- switchroot: Mount failed
- system hangs
Thanks to the RH team for fixing the above non-bootable kernel!
Note: The problem of the boot time GUI is not resolved and it appears to be related to the latest xorg updates and no fixes are known at this time, AFAIK.
For those of you who have encountered the unbootable kernel with the "nfs root target" message, here is what you need to do:
Using your latest working bootable kernel: =============================== 1) rpm -e ltsp-client (or yum remove ltsp-client) 2) mkinitrd -f /boot/initrd-<VERSION>.img <VERSION>
I have tested the above with kernel versions: 2.6.26.3-29.f9.i686 2.6.26.5-45.fc9.i686
.... and the problems disappears!
Note: I did not consciously install ltsp-client and this must have been included in the updates AFTER kernel-2.6.25.14-108.f9.i686. Strangely, the problem appeared only with kernels above: 2.6.25.14-108.f9.i686 which was installed/updated AFTER 2.6.25.14-108.f9.i686. My guess is that initrd was (re)built when ltsp-client was installed just before the new kernels were added.
Cheers! Dan
-
Antonio M -
Craig White -
Dan Thurman -
Fred Silsbee -
Patrick O'Callaghan -
Renich Bon Ciric