Curt writes:
> On 2015-07-08, Rodolfo Medina wrote:
It seems it is `0x6000': with it, the message didn't appear any more.
>>>
>>> What were the consequences of the message appearing (besides the message
>>> appearing)?
>>
>> Actually, none at all. But the start off has sometimes its o
On 2015-07-08, Rodolfo Medina wrote:
>>>
>>> It seems it is `0x6000': with it, the message didn't appear any more.
>>
>> What were the consequences of the message appearing (besides the message
>> appearing)?
>
> Actually, none at all. But the start off has sometimes its own form of
> `aesthetics
Curt writes:
> On 2015-07-07, Rodolfo Medina wrote:
>>>
>>> Thanks, I will. The file should be modesetting.conf. But how do I know
>>> what the appropriate parameter for `0xaddr' will be?
>>>
>>> Rodolfo
>>
>> It seems it is `0x6000': with it, the message didn't appear any more.
>
> What were
On 2015-07-07, Rodolfo Medina wrote:
>>
>> Thanks, I will. The file should be modesetting.conf. But how do I know what
>> the appropriate parameter for `0xaddr' will be?
>>
>> Rodolfo
>
> It seems it is `0x6000': with it, the message didn't appear any more.
What were the consequences of the mes
Rodolfo Medina writes:
> Darac Marjal writes:
>
>> On Tue, Jul 07, 2015 at 01:23:01PM +0100, Rodolfo Medina wrote:
>>> Hi all.
>>>
>>> On my old Pentiium III, at boot the following message appears:
>>>
>>> via686a :00:04.4: base address not set - upgrade BIOS or use
>>> force_addr=0xaddr
>
5 matches
Mail list logo
