On Fri, Dec 21, 2007 at 06:22:41PM -0800, H. Peter Anvin wrote:
> >Ok, that's a different argument than before. Ok. Although it's
> >only a few bytes.
> >
> >I would lobby for any message at least contain the suggestion to try
> >edd=off. That could save users a lot of time.
>
> The important thi
Andi Kleen wrote:
Those don't live in an area of memory which is hard-limited to 32K.
Why not 64k?
Because the bootloader needs some memory in the same segment that it
controls. Furthermore, since there were some residual uses of the
0x9000 segment (now removed, but not all bootloaders co
> Those don't live in an area of memory which is hard-limited to 32K.
Why not 64k?
Ok, that's a different argument than before. Ok. Although it's
only a few bytes.
I would lobby for any message at least contain the suggestion to try
edd=off. That could save users a lot of time.
-Andi
--
To uns
Andi Kleen wrote:
"H. Peter Anvin" <[EMAIL PROTECTED]> writes:
[EMAIL PROTECTED] wrote:
/* Query EDD information */
#if defined(CONFIG_EDD) || defined(CONFIG_EDD_MODULE)
- query_edd();
+printf("Probing EDD (query Bios for boot-device information)\n");
+printf("If
"H. Peter Anvin" <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] wrote:
>> /* Query EDD information */
>> #if defined(CONFIG_EDD) || defined(CONFIG_EDD_MODULE)
>> - query_edd();
>> +printf("Probing EDD (query Bios for boot-device information)\n");
>> +printf("If boot
Alan Cox wrote:
Does printk support escape sequences? The last time I tried
printk("\e[1;35m omg ponies \e[0m"); that did not went too successful.
It should handle \r correctly. If not that is easy to fix.
Escape codes are bad and should not be used - you may have a serial
console and not be o
> Does printk support escape sequences? The last time I tried
> printk("\e[1;35m omg ponies \e[0m"); that did not went too successful.
It should handle \r correctly. If not that is easy to fix.
Escape codes are bad and should not be used - you may have a serial
console and not be on a Linux conso
Jan Engelhardt wrote:
On Dec 16 2007 20:18, Alan Cox wrote:
Why tax other people with a warning/hang etc. in printk when the
problem is very unlikely on their systems?
I think there is sense in it if you do it subtly differently.
printk(".. if this hangs do ... \r");
edd_stuff(
On Dec 16 2007 20:18, Alan Cox wrote:
>
>> Why tax other people with a warning/hang etc. in printk when the
>> problem is very unlikely on their systems?
>
>I think there is sense in it if you do it subtly differently.
>
> printk(".. if this hangs do ... \r");
> edd_stuff();
> pr
> > But that is not the point. Problem is not widely known, likely happens
> > with very old BIOSes and people who use those systems should be
> > knowing more than simply booting back to Win98.
>
> i don`t see any relation to what a user knows and what kind of system of what
> age he is using.
> > not sure if really all of them are the edd problem i have, but i`m quite
> > sure for some of those.
> > can provide more links if somebody likes.
>
> None of them seemed like they were determined as EDD problems -
so - see how difficult it is to determine, what`s the problem is ? ;)
>some
> Why tax other people with a warning/hang etc. in printk when the
> problem is very unlikely on their systems?
I think there is sense in it if you do it subtly differently.
printk(".. if this hangs do ... \r");
edd_stuff();
printk(" \r");
On Dec 16, 2007 2:11 PM, <[EMAIL PROTECTED]> wrote:
> some of them
> http://forums.suselinuxsupport.de/lofiversion/index.php/t61581.html
> http://suseforums.net/index.php?showtopic=1302
> http://forums.suselinuxsupport.de/lofiversion/index.php/t3157.html
> http://www.linuxforums.org/forum/installa
TED]>
> Gesendet: 16.12.07 19:17:40
> An: [EMAIL PROTECTED]
> CC: linux-kernel@vger.kernel.org, [EMAIL PROTECTED]
> Betreff: Re: [PATCH] [RFC] be more verbose when probing EDD
>
> [EMAIL PROTECTED] wrote:
> > /* Query EDD information */
> > #if defined(CONFIG_
IL PROTECTED]>
> Gesendet: 16.12.07 18:34:48
> An: [EMAIL PROTECTED]
> CC: linux-kernel@vger.kernel.org, [EMAIL PROTECTED], [EMAIL PROTECTED]
> Betreff: Re: [PATCH] [RFC] be more verbose when probing EDD
>
> On Sun, 16 Dec 2007, [EMAIL PROTECTED] wrote:
>
> >
>
[EMAIL PROTECTED] wrote:
/* Query EDD information */
#if defined(CONFIG_EDD) || defined(CONFIG_EDD_MODULE)
- query_edd();
+printf("Probing EDD (query Bios for boot-device information)\n");
+printf("If boot hangs here, you may have a buggy Bios. Try edd=skipmbr or
e
On Sun, 16 Dec 2007, [EMAIL PROTECTED] wrote:
- it seems there are buggy Bios implementations out there which have problems
with EDD
- your favourite distro may have set CONFIG_EDD=y|m , so EDD probe is on by
default quite often nowadays.
- setting "edd=off" when you get that hang on boot is
Hello!
i`m sysadmin for quite some time and while being that, i have come across the
one or another system, which refused to boot a linux kernel. typical symptom i
have seen is a blinking cursor in the upper left just after kernel/initrd were
loaded.
i never spent much time on that and either
18 matches
Mail list logo
