On 1/22/2011 12:38 PM, Rick Sewill wrote:
> I looked at URL, http://fedoraproject.org/wiki/KernelCommonProblems,
> for hints. It has a suggestion, under "Crashes/Hangs",
> "# initcall_debug will allow to see the last thing the kernel tried to
> initialise before it hung."
> I have the impression,
On 1/22/2011 1:03 PM, JB wrote:
> I do not see any audio (sound) device controller in your lspci ...
> Is that possible ?
That would be correct, it's a server board, it has no onboard audio.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
htt
Ashley M. Kirchner pcraft.com> writes:
> ...
I do not see any audio (sound) device controller in your lspci ...
Is that possible ?
JB
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
G
On 1/22/2011 12:35 PM, JB wrote:
> Ashley M. Kirchner pcraft.com> writes:
>
> there is something perhaps with your two Ethernet setups (you have 2 NIC
> controllers shown in lspci).
>
> always keep --> ignore_loglevel enforcing=0
> add -->ether=0,0,eth1
>
> this will force probing both Ethe
On Saturday, January 22, 2011 01:14:40 pm Ashley M. Kirchner wrote:
> On 1/22/2011 12:03 PM, JB wrote:
> > Kernel command line:
> > always keep --> ignore_loglevel
> > add --> enforcing=0
>
> The only major difference this time is that it's also detecting the
> additional drives that are o
Ashley M. Kirchner pcraft.com> writes:
there is something perhaps with your two Ethernet setups (you have 2 NIC
controllers shown in lspci).
always keep --> ignore_loglevel enforcing=0
add --> ether=0,0,eth1
this will force probing both Ethernets.
Another kernel option you can try as well i
On 1/22/2011 12:03 PM, JB wrote:
> Kernel command line:
> always keep --> ignore_loglevel
> add --> enforcing=0
The only major difference this time is that it's also detecting the
additional drives that are on the add-on card. Previously it wasn't,
but now I can see them after it says '
Ashley M. Kirchner pcraft.com> writes:
> ...
Kernel command line:
always keep --> ignore_loglevel
add --> enforcing=0
JB
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: htt
On 1/22/2011 11:31 AM, JB wrote:
> Remove "quiet" and
> add "ignore_loglevel"
> (without "" characters) to the boot options to see where it hangs.
There was no 'quiet' option on the boot line to begin with.
After the 'waiting for hardware to initialize...' line, there are
several lines
Ashley M. Kirchner pcraft.com> writes:
> ...
Remove "quiet" and
add "ignore_loglevel"
(without "" characters) to the boot options to see where it hangs.
Report back.
JB
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedorapro
On 1/22/2011 11:11 AM, JB wrote:
> I have to guess somewhat, which is a polite way to admit ...
> Pass these on kernel line:
> xdriver=vesa nomodeset agp=off
>
> JB
No dice. Same spot.
At this point I may just have to continue running CentOS, it's not
like it's the end of the world an
Ashley M. Kirchner pcraft.com> writes:
> ...
I have to guess somewhat, which is a polite way to admit ...
Pass these on kernel line:
xdriver=vesa nomodeset agp=off
JB
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproje
I'm guessing no one has an answer as to why FC14 install hangs at
the 'waiting for hardware to initialize' while I can install CentOS with
no problems what so ever? Or what to do to try and get FC14 installed
(tried the standard ide=nodma noapic acpi=off options already). Below
are the
13 matches
Mail list logo
