On Tuesday, January 25, 2011 06:43:27 pm JB wrote:
> Thirdly, stick around the thread for many days (even weeks) - there is
> a good chance somebody will have time (like Lamar next week) and come up
> with a good idea.
Given what I've seen of Ashley's symptoms, it may be more BIOS related than
ch
Maurizio Marini datalogica.com> writes:
> ...
> I would delay the stream of lines before
> waiting for hardware to initialize
>
> or better it would be to avoiud the clear screen, can fedora ppl avoid this
> clear screen?
>
I do not know if this kernel parameter may help you in your extende
On Wed, 26 Jan 2011 09:50:42 + (UTC)
JB wrote:
> Ashley M. Kirchner pcraft.com> writes:
>
> > ...
>
> You are much happier and reasonable this time - throwing books at Fedora,
> however deserved and fun, will not change anything :-)
I agree with that :)
I have added ignore_loglevel enfor
Ashley M. Kirchner pcraft.com> writes:
> ...
You are much happier and reasonable this time - throwing books at Fedora,
however deserved and fun, will not change anything :-)
Please file a new bug report with Bugzilla as an F14 kernel problem.
If you need help, tell us.
https://bugzilla.redhat.c
On Tue, Jan 25, 2011 at 14:26:00 -0700,
"Ashley M. Kirchner" wrote:
>
> Well, that was a major pain in the you-know-what. Sheesh. Intel
> only provides floppy BIOS updates for this board (considering how old it
> is, I don't blame them.) So I had to find a a floppy drive, find a
> fl
> -Original Message-
> From: users-boun...@lists.fedoraproject.org [mailto:users-
> boun...@lists.fedoraproject.org] On Behalf Of JB
> Sent: Tuesday, January 25, 2011 4:43 PM
> To: users@lists.fedoraproject.org
> Subject: Re: [Fedora] Re: FC14 Installation Hangs
>
>
Ashley M. Kirchner pcraft.com> writes:
>
>
> Well, with the confetti guns at the ready, I tried FC13, no dice.
> Boot options were:
>
> ide=nodma noapic acpi=off ignore_loglevel initcall_debug
> ...
Do not worry, be happy.
You are a brave girl - the way you read all that extended
Well, with the confetti guns at the ready, I tried FC13, no dice.
Boot options were:
ide=nodma noapic acpi=off ignore_loglevel initcall_debug
It quit at the same point it has been lately, which is giving me
garbage on screen like my image posted yesterday, and ata3 times out,
On 1/25/2011 5:41 AM, JB wrote:
> Check the board's BIOS date.
> In Bugzilla 665109 they claim that this board can have old or incomplete BIOS.
> Does it seem to be outdated ? Is there any update on manufacturer's or
> reseller's web site ?
>
> I would look at the BIOS settings too (sometimes their
Ashley M. Kirchner pcraft.com> writes:
>
> On 1/24/2011 4:33 PM, JB wrote:
> > Read Lamar Owen's post.
> > You may search Google and Bugzilla for problems related to your Broadcom
> > CNB20LE board.
> >
> > There is a chance that Alan drops by and he is expert on hard disks.
> >
> > Tomorrow wil
On 1/24/2011 4:33 PM, JB wrote:
> Read Lamar Owen's post.
> You may search Google and Bugzilla for problems related to your Broadcom
> CNB20LE board.
>
> There is a chance that Alan drops by and he is expert on hard disks.
>
> Tomorrow will try some more.
>
> JB
Yep, I'm going to try and boot
Ashley M. Kirchner pcraft.com> writes:
> ...
Read Lamar Owen's post.
You may search Google and Bugzilla for problems related to your Broadcom
CNB20LE board.
There is a chance that Alan drops by and he is expert on hard disks.
Tomorrow will try some more.
JB
--
users mailing list
users@lis
On 1/24/2011 4:04 PM, JB wrote:
> Try:
> keep only -> ignore_loglevel enforcing=0 initcall_debug
>
> Keep these runs separate.
>
> 1st run:
> add -> pci=use_crs
>
> 2nd run (remove 1st run added parameters):
> add -> noapic nolapic nolapic_timer
>
> 3rd run (remove 2nd run added parameters):
> n
Ashley M. Kirchner pcraft.com> writes:
> ...
One more time for today :-)
I incorporated a probable fix (1st run) from similar problems in Bugzilla.
Try:
keep only -> ignore_loglevel enforcing=0 initcall_debug
Keep these runs separate.
1st run:
add -> pci=use_crs
2nd run (remove 1st run adde
On 1/24/2011 2:32 PM, JB wrote:
> Let's take a shot at hard disk problems:
> keep only -> ignore_loglevel enforcing=0 initcall_debug
>
> Keep these 2 runs separately.
>
> 1st run:
> add -> pci=nomsi pci=nommconf pci=nocrs
>
> 2nd run (remove 1st run added parameters):
> rdblacklist=ahci
>
> JB
[Note that there is quite a list of things below to look at, but do look at the
bugzilla entry at the very bottom and try that, possibly even first.]
On Monday, January 24, 2011 02:09:52 pm Ashley M. Kirchner wrote:
> What I don't get is how this dies with FC14 but not with CentOS 5
> ... d
Ashley M. Kirchner pcraft.com> writes:
> ...
Let's take a shot at hard disk problems:
keep only -> ignore_loglevel enforcing=0 initcall_debug
Keep these 2 runs separately.
1st run:
add -> pci=nomsi pci=nommconf pci=nocrs
2nd run (remove 1st run added parameters):
rdblacklist=ahci
JB
On 1/24/2011 2:06 PM, JB wrote:
> I am looking at kernel parameters and Fedora kernel problems - there is so
> much of it that could go wrong that the head is spinning.
>
> Let's hope that Alan finds time to come back to the thread - he is the real
> expert here.
>
> I will continue looking into it
Ashley M. Kirchner pcraft.com> writes:
>
> On 1/24/2011 1:43 PM, JB wrote:
> > I am looking at that dmesg posted by you - CentOS had some errors too.
> > We have to reset the kernel line and run it again with max verbose
> > debugging.
> >
> > Please reset kernel parameters to only the ones nee
On 1/24/2011 1:43 PM, JB wrote:
> I am looking at that dmesg posted by you - CentOS had some errors too.
> We have to reset the kernel line and run it again with max verbose debugging.
>
> Please reset kernel parameters to only the ones needed for debugging (and keep
> them always), remove anything
Ashley M. Kirchner pcraft.com> writes:
> ...
I am looking at that dmesg posted by you - CentOS had some errors too.
We have to reset the kernel line and run it again with max verbose debugging.
Please reset kernel parameters to only the ones needed for debugging (and keep
them always), remove
On 1/24/2011 12:14 PM, Terry Polzin wrote:
> Install with basic video? Or what ever the correct verbage is.
Tried that already. Also tried running in text mode, vnc mode,
nothing. It doesn't even get there, it dies way before that.
--
users mailing list
users@lists.fedoraproject.org
To uns
On Mon, 2011-01-24 at 12:09 -0700, Ashley M. Kirchner wrote:
> On 1/22/2011 2:53 PM, Alan Cox wrote:
> > Ok try this
> > Remove the 'quiet' add
> >
> > irqpoll initcall_debug
> >
> > The first one tries to catch and deal with hangs due to IRQ routing bugs
> > in the BIOS etc, the second will print
On 1/22/2011 2:53 PM, Alan Cox wrote:
> Ok try this
> Remove the 'quiet' add
>
> irqpoll initcall_debug
>
> The first one tries to catch and deal with hangs due to IRQ routing bugs
> in the BIOS etc, the second will print a trace of each function called
> during initialisation. It's not exciting to
> meantime, is there a way to capture this so I don't have to try and type it
> all out? While the machine has serial ports, they're all disabled in BIOS
> and I don't know how else I can capture all the stuff that gets spewed out,
> other than to take a physical picture of the screen when it hang
>
> Ok try this
>
> Remove the 'quiet' add
>
> irqpoll initcall_debug
>
> The first one tries to catch and deal with hangs due to IRQ routing bugs
in the
> BIOS etc, the second will print a trace of each function called during
> initialisation. It's not exciting to most people but as part of a
On Sat, 22 Jan 2011 19:35:16 + (UTC)
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 for
> ata3.01 - which accounts for the four hard drives, and then it lists the
> CD-ROM. But it still dies at the same exact spot after detecting the
> CD-ROM ...
Ok try this
Remove the 'quiet' add
irqpoll initcall_debug
The first one tries to catch and deal with hangs due to IRQ routing bugs
in
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
Below
are the output of dmesg and lspci as JB previously requested.
Original Message
Subject: Re: [Fedora] Re: FC14 Installation Hangs
Date: Fri, 21 Jan 2011 14:40:08 -0700
From: Ashley M. Kirchner
Reply-To: Community support for Fedora users
To: Commun
On 1/21/2011 1:22 PM, JB wrote:
> Just install CentOS (as if you were installing F14 - layout mainly),
> select
> desktop set (X, GNOME), nothing more. It will take 15 min or so.
> Then pass to the list the following displays:
> $ dmesg
> $ lspci
>
> JB
That I can do. In the interest of not
42 matches
Mail list logo
