|
Bugzilla – Full Text Bug Listing |
| Summary: | HUGE letters on login screen | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Gerd Hoffmann <kraxel> |
| Component: | SaX2 | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | forgotten_9WJQF5tTlz, hugo.costelha |
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
X server log
config file matching the log file initial config file created during installation ... |
||
|
Description
Gerd Hoffmann
2006-11-10 13:20:08 UTC
Seen on both vmware and qemu installs. hwinfo --monitor ? sysp -q xstuff ? This was an issue in libhd and has been fixed, I'm wondering why you stumbled over it ? by no means a blocker ;) hwinfo --monitor ? sysp -q xstuff ? This was an issue in libhd and has been fixed, I'm wondering why you stumbled over it ? by no means a blocker ;) factory root ~# hwinfo --monitor
19: None 00.0: 10000 Monitor
[Created at fb.71]
Unique ID: rdCR.EY_qmtb9YY0
Hardware Class: monitor
Model: "Generic Monitor"
Vendor: "Generic"
Device: "Monitor"
Resolution: 800x600@75Hz
Driver Info #0:
Max. Resolution: 800x600
Vert. Sync Range: 50-90 Hz
Hor. Sync Range: 31-48 kHz
Config Status: cfg=new, avail=yes, need=no, active=unknown
factory root ~# sysp -q xstuff
Card0 => DDC : <undefined>
Card0 => Name : Monitor
Card0 => Vendor : Generic
Card0 => Primary : 00-02-0
Card0 => Chipset : <undefined>
Card0 => Vsync : 61
Card0 => Hsync : 38
Card0 => Vesa : 800 600 37 60
Card0 => FbTiming : "800x600" 38.34 800 832 928 1024 600 604 608 624 -HSy
nc -VSync
Card0 => Dacspeed : 220
Card0 => Modeline : <undefined>
Card0 => Memory : 4096
Card0 => Current : 00-02-0
Card0 => RawDef : None
Card0 => Option : None
Card0 => Extension : None
Card0 => Module : cirrus
Card0 => Display : CRT
Card0 => Size : 16x16
Card0 => VesaBios : 2.0
Hmm, very strange there is no size info in hwinfo. Do you have a Xorg log file from this driver ? Thanks Created attachment 104913 [details]
X server log
Created attachment 104914 [details]
config file matching the log file
Created attachment 104915 [details]
initial config file created during installation ...
... with the bogus displaysize line commented out.
After first login an popup showed up asking me whenever I want adjust the displaysize manually, which I did, so I got a new config file.
there is no size information in the log either. If you don't mind could you call: init 3 hwinfo --monitor is there a difference in the output compared to comment #4 ? By the way is there a possibility for me to login to the machine for debugging ? Thanks set to needinfo I'm sorry but I cannot reproduce this problem. If you call sysp -s xstuff ( new scan) you will get: Card0 => DDC : <undefined> Card0 => Name : Monitor Card0 => Vendor : Generic Card0 => Primary : 00-02-0 Card0 => Chipset : <undefined> Card0 => Vsync : 61 Card0 => Hsync : 38 Card0 => Vesa : 800 600 37 60 Card0 => FbTiming : "800x600" 38.34 800 832 928 1024 600 604 608 624 -HSync -VSync Card0 => Dacspeed : 220 Card0 => Modeline : <undefined> Card0 => Memory : 4096 Card0 => Current : 00-02-0 Card0 => RawDef : None Card0 => Option : None Card0 => Extension : None Card0 => Module : cirrus Card0 => Display : CRT Card0 => VesaBios : 2.0 which is ok. I don't have any clue who reports displaysize 16x16. I'm pretty sure if you simply call sax2 -r on this system now you will not be able to reproduce the problem do you ? Yep, it is gone now. So something must have been different when installing the machine? Although I havn't changed much since installing it ... yes it's very weird, sometimes such effects come back when rebooting the machine. We had the problem that we can access the BIOS one time providing wrong data and every subsequently call doesn't provide any data. Well better than wrong data. In your case we can always access the bios which you can see on the BIOS version information but the data is different which is a new behaviour. I added a sanity check for the display size value, hoping this will help for the future. But I do have bad feelings about all that Booted using an older qemu version. It's back now, try again. "sax2 -r" greats me with huge letters too (machine is in that state right now). Guess it's either the vga bios or timing (older qemu doesn't use vt and thus is much slower). the sanity check fixed the problem: cd ~root ./sysp -s xstuff *** Bug 221576 has been marked as a duplicate of this bug. *** *** Bug 216587 has been marked as a duplicate of this bug. *** *** Bug 222618 has been marked as a duplicate of this bug. *** See bug #217790, starting at comment #16, for the workaround we'll use in GNOME. |