Re: USB mouse hiccups (was RFD: Kernel release numbering)

Re: USB mouse hiccups (was RFD: Kernel release numbering)

[Andrew Morton]

Guys, we seem to have a tridentfb regression in 2.6.12-rc1.

viking <viking@flying-brick.caverock.net.nz> wrote:
>
> Also (and this is something I've noticed since I tried tridentfb) the video
>  buffer never seems to get cleared, except when I change virtual terminals,
>  then change back to the terminal concerned. THEN it's cleared. So for the
>  moment, I've gone back to using VESAfb.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Re: USB mouse hiccups (was RFD: Kernel release numbering)

[Antonino A. Daplas]

On Tuesday 22 March 2005 04:44, Andrew Morton wrote:
> Guys, we seem to have a tridentfb regression in 2.6.12-rc1.
>
> viking <viking@flying-brick.caverock.net.nz> wrote:
> > Also (and this is something I've noticed since I tried tridentfb) the
> > video buffer never seems to get cleared, except when I change virtual
> > terminals, then change back to the terminal concerned. THEN it's cleared.
> > So for the moment, I've gone back to using VESAfb.
>

Smells like a fillrect problem.

1. First, can you do an fbset and make sure that yres_virtual and yres are
the same? If you run fbset -i, in the line that starts with 'geometry', the
2nd and 4th number should be the same (or have a difference not more than
7). This disables ypan.

mode "800x600-85"
    # D: 56.252 MHz, H: 53.676 kHz, V: 85.065 Hz
    geometry 800 600 832 32767 8
                 ^^^      ^^^    <- same number

If not the same, do:

fbset -vyres n

where n: is equal to the vertical resolution

2. If you still get a non-clearing display, then check if
CONFIG_FB_TRIDENT_ACCEL is set to y.  If it is, set it to n. Recompile and
reboot.

3. Please send your .config, dmesg, lspci -vvv, and fbset -i.

4. What is the last kernel version where tridentfb worked for you?

BTW, there are no major changes in tridentfb for months, so I'm surprised
about this regression.

Tony
 




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Re: USB mouse hiccups (was RFD: Kernel release numbering)

[Andrew Morton]

"Antonino A. Daplas" <adaplas@hotpop.com> wrote:
>
> On Tuesday 22 March 2005 04:44, Andrew Morton wrote:
> > Guys, we seem to have a tridentfb regression in 2.6.12-rc1.
> >
> > viking <viking@flying-brick.caverock.net.nz> wrote:
> > > Also (and this is something I've noticed since I tried tridentfb) the
> > > video buffer never seems to get cleared, except when I change virtual
> > > terminals, then change back to the terminal concerned. THEN it's cleared.
> > > So for the moment, I've gone back to using VESAfb.
> >
> 
> Smells like a fillrect problem.
> 
> 1. First, can you do an fbset and make sure that yres_virtual and yres are
> the same? If you run fbset -i, in the line that starts with 'geometry', the
> 2nd and 4th number should be the same (or have a difference not more than
> 7). This disables ypan.
> 
> mode "800x600-85"
>     # D: 56.252 MHz, H: 53.676 kHz, V: 85.065 Hz
>     geometry 800 600 832 32767 8
>                  ^^^      ^^^    <- same number
> 
> If not the same, do:
> 
> fbset -vyres n
> 
> where n: is equal to the vertical resolution
> 
> 2. If you still get a non-clearing display, then check if
> CONFIG_FB_TRIDENT_ACCEL is set to y.  If it is, set it to n. Recompile and
> reboot.
> 
> 3. Please send your .config, dmesg, lspci -vvv, and fbset -i.
> 
> 4. What is the last kernel version where tridentfb worked for you?
> 
> BTW, there are no major changes in tridentfb for months, so I'm surprised
> about this regression.
> 

Guys, is this problem still present in 2.6.12-rc5?

Thanks.


-------------------------------------------------------
SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
online with coworkers and clients while avoiding the high cost of travel and
communications. There is no equipment to buy and you can meet as often as
you want. Try it free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click

Re: Re: USB mouse hiccups (was RFD: Kernel release numbering)

[James Simmons]

> > If not the same, do:
> > 
> > fbset -vyres n
> > 
> > where n: is equal to the vertical resolution
> > 
> > 2. If you still get a non-clearing display, then check if
> > CONFIG_FB_TRIDENT_ACCEL is set to y.  If it is, set it to n. Recompile and
> > reboot.
> > 
> > 3. Please send your .config, dmesg, lspci -vvv, and fbset -i.
> > 
> > 4. What is the last kernel version where tridentfb worked for you?
> > 
> > BTW, there are no major changes in tridentfb for months, so I'm surprised
> > about this regression.
> > 
> 
> Guys, is this problem still present in 2.6.12-rc5?

Anyone with a trident card out there?



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.  
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20

Re: Re: USB mouse hiccups (was RFD: Kernel release numbering)

[Lars Tobias Børsting]

James Simmons <jsimmons@www.infradead.org> writes:

> Anyone with a trident card out there?

I have an old laptop with a Trident CyberBlade Ai1 integrated on an
ALI-chipset lying around. Happy to help. Just joined this list, though,
so I don't have the rest of this thread.

-- 
Regards,

Lars Tobias Børsting



-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r 

Tridentfb troubles

[viking]

On Mon, Mar 21, 2005 at 12:44:26PM -0800, Andrew Morton wrote:
> 
> Guys, we seem to have a tridentfb regression in 2.6.12-rc1.
> 
> viking <viking@flying-brick.caverock.net.nz> wrote:
> >
> > Also (and this is something I've noticed since I tried tridentfb) the video
> >  buffer never seems to get cleared, except when I change virtual terminals,
> >  then change back to the terminal concerned. THEN it's cleared. So for the
> >  moment, I've gone back to using VESAfb.

**********
Actually, it's in every release I've ever tested. 
**********

I hadn't mentioned it before, because vesafb does what I want, apart from not
being resizable.  I have a Apollo MVP4, VIA686A (or B) video chipset, though
the Video shows itself as a CyberBlade/i7:

brick$ lspci -v -v
...
01:00.0 VGA compatible controller: Trident Microsystems CyberBlade/i7 (rev 5d)
(prog-if 00 [VGA])
Subsystem: FIRST INTERNATIONAL Computer Inc: Unknown device 9915
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping-
SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 32
Interrupt: pin A routed to IRQ 10
Region 0: Memory at e5800000 (32-bit, non-prefetchable) [size=8M]
Region 1: Memory at e6000000 (32-bit, non-prefetchable) [size=128K]
Region 2: Memory at e5000000 (32-bit, non-prefetchable) [size=8M]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [80] AGP version 1.0
Status: RQ=33 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3-
Rate=x1,x2
Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=<none>
Capabilities: [90] Power Management version 1
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-


I have via-agp and agpgart loaded, though those aren't for 2d. Not sure what
else to tell you, to be honest. If I put BOTH the vesafb AND the tridentfb
into the kernel, and select vesafb on lilo (video=vesafb:mtrr,ypan), the
kernel boots up using tridentfb regardless.

The 640x480-60 (the one the kernel seems to boot up on unless told otherwise)
screenmode looks absolutely shocking, with a very wiggly screen mainly in the
X direction. That's probably due to the definition in drivers/video/modedb.c,
something I can either tweak myself, or avoid using.

I'll do more testing, see what I come up with aside from that. You may need to
tell me what other details you want though.

Andrew - you still wish to be CC:ed on this video issue?

-- 
 /|   _,.:*^*:.,   |\  Cheers from the Viking family, including Pippin, our cat
| |_/'  viking@ `\_| |
|    flying-brick    | $FunnyMail   : What do you mean, I've lost the plot?
 \_.caverock.net.nz_/     5.40      : I planted them carrots right here!!


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Tridentfb troubles

[Andrew Morton]

viking <viking@flying-brick.caverock.net.nz> wrote:
>
> Andrew - you still wish to be CC:ed on this video issue?

Yes please.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click