* vgaigfx problem on sandy (core-i5) (0x0126)
@ 2020-07-27 2:19 kokamoto
2020-08-14 4:35 ` [9front] " kokamoto
0 siblings, 1 reply; 4+ messages in thread
From: kokamoto @ 2020-07-27 2:19 UTC (permalink / raw)
To: 9front
I updated above kernel, and got problem like:
init: starting /bin/rc
aux/vga: igfx: a
ttaching mmio: bad arg in system call
bind: #i: no frame buffer
...
This machine has been working properly for a log time.
The differences of vagigfx.c in kernel are very small
igfxenable(VGAscr* scr)
{
Pcidev *p;
if(scr->mmio != nil) <== these two lines added
return;
...
The two cmd/aux/vga/jgfx.c are same.
Above two lines are not related to this problem, I think.
Kenji
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [9front] vgaigfx problem on sandy (core-i5) (0x0126)
2020-07-27 2:19 vgaigfx problem on sandy (core-i5) (0x0126) kokamoto
@ 2020-08-14 4:35 ` kokamoto
2020-08-17 3:30 ` kokamoto
0 siblings, 1 reply; 4+ messages in thread
From: kokamoto @ 2020-08-14 4:35 UTC (permalink / raw)
To: 9front
Thank you very much.
Now I can boot this safely.
Kenji
> I updated above kernel, and got problem like:
>
> init: starting /bin/rc
> aux/vga: igfx: a
> ttaching mmio: bad arg in system call
> bind: #i: no frame buffer
> ...
>
> This machine has been working properly for a log time.
> The differences of vagigfx.c in kernel are very small
>
> igfxenable(VGAscr* scr)
> {
> Pcidev *p;
>
> if(scr->mmio != nil) <== these two lines added
> return;
>
> ...
>
> The two cmd/aux/vga/jgfx.c are same.
>
> Above two lines are not related to this problem, I think.
>
> Kenji
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [9front] vgaigfx problem on sandy (core-i5) (0x0126)
2020-08-14 4:35 ` [9front] " kokamoto
@ 2020-08-17 3:30 ` kokamoto
0 siblings, 0 replies; 4+ messages in thread
From: kokamoto @ 2020-08-17 3:30 UTC (permalink / raw)
To: 9front
No, I made mistake.
I booted this machine with older version for pxe, sorry.
The problem still remains.
Kenji
> Thank you very much.
> Now I can boot this safely.
>
> Kenji
>
>> I updated above kernel, and got problem like:
>>
>> init: starting /bin/rc
>> aux/vga: igfx: a
>> ttaching mmio: bad arg in system call
>> bind: #i: no frame buffer
>> ...
>>
>> This machine has been working properly for a log time.
>> The differences of vagigfx.c in kernel are very small
>>
>> igfxenable(VGAscr* scr)
>> {
>> Pcidev *p;
>>
>> if(scr->mmio != nil) <== these two lines added
>> return;
>>
>> ...
>>
>> The two cmd/aux/vga/jgfx.c are same.
>>
>> Above two lines are not related to this problem, I think.
>>
>> Kenji
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [9front] vgaigfx problem on sandy (core-i5) (0x0126)
@ 2020-08-14 4:35 kokamoto
0 siblings, 0 replies; 4+ messages in thread
From: kokamoto @ 2020-08-14 4:35 UTC (permalink / raw)
To: kokamoto, 9front
Very sorry making noise. It was my careless mistake to copy a file
under /sys/stc/9/port/devpnp.c.
Now, I can use core-i5 machine as now.
Kenji
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2020-08-21 0:39 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-27 2:19 vgaigfx problem on sandy (core-i5) (0x0126) kokamoto
2020-08-14 4:35 ` [9front] " kokamoto
2020-08-17 3:30 ` kokamoto
2020-08-14 4:35 kokamoto
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).