[Bug 329581] New: Can't install 10.3 on Dell Optiplex GX260
https://bugzilla.novell.com/show_bug.cgi?id=329581 Summary: Can't install 10.3 on Dell Optiplex GX260 Product: openSUSE 10.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Blocker Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: vrb@novell.com QAContact: jsrain@novell.com Found By: IS&T Can't install 10.3 on Dell Optiplex GX260. Symptom: After successful network configuration and test, it displays the release notes. Right after that, the screen flashes a few times and then goes blank. I'd be glad to provide log files, but not sure how since the screen is blank. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c1
--- Comment #1 from Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=329581#c2
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c3
Vance Baarda
Could you try to create a "i810" driver based configuration by running "sax2 -r -m 0=i810"? Does this configuration work?
I killed the "Xorg -deferglyphs 16 vt07" process, and the machine finished booting (although the graphics screen is blank). Then I went to init level 3 and ran the sax2 command you suggested. The symptoms are the same as during the initial installation. The graphics screen is blank. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c4
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c5
Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c6
--- Comment #6 from Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c7
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c8
--- Comment #8 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c9
--- Comment #9 from Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c10
--- Comment #10 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c11
--- Comment #11 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c12
--- Comment #12 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c13
--- Comment #13 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c14
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c15
--- Comment #15 from Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c16
--- Comment #16 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c17
--- Comment #17 from Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c18
Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c19
--- Comment #19 from Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c20
--- Comment #20 from Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c21
--- Comment #21 from Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c22
--- Comment #22 from Felix Miata
-(II) intel(0): Output VGA using initial mode 1152x768
Where does a 1.5:1 aspect ratio mode come from? Standard display modes are either 1.25:1 (SXGA & QSXGA), 1.333:1 (standard CRT modes), 1.6:1 (wide panel computer displays) or 1.778:1 (HDTV screens). http://mrmazda.no-ip.com/auth/displays.html -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c23
--- Comment #23 from Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c24
Stefan Dirsch
(In reply to comment #13 from Stefan Dirsch) -(II) intel(0): Output VGA using initial mode 1152x768 Where does a 1.5:1 aspect ratio mode come from? Please don't ask. It's some magic in RANDR 1.2 code, which takes some strange assumptions. This issue is not part of this bugreport.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c25
Vance Baarda
PXE means in your case that you didn't enable the framebuffer.
What does this mean? How did I not enable the framebuffer? If this is a bad idea, why allow it?
See also comment #5. This is a bad idea. I'm therefore closing this one as WORKSFORME.
Your monitor was not detected and got the default values for a Generic monitor.
Hmm, so how do we get the system to detect this monitor? Maybe this bug needs to move to the hwinfo package? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c26
--- Comment #26 from Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c27
--- Comment #27 from Stefan Dirsch
(In reply to comment #24 from Stefan Dirsch)
PXE means in your case that you didn't enable the framebuffer.
What does this mean? How did I not enable the framebuffer? If this is a bad idea, why allow it?
I don't know why, but it seems everbody who is using PXE boot does not specify the vga=0xXXX parameter on the kernel commandline, although nowadays really any monitor is capable of displaying a resolution of 1024x768. So why not simply specifying vga=0x317 by default?!? The result when not doing so is the use of vesa driver (instead of fbdev), which is not recommended to use at all and obviously has all kind of different problems (it seems especially when intel driver is started as second Xserver for testing purposes during installation).
Your monitor was not detected and got the default values for a Generic monitor.
Hmm, so how do we get the system to detect this monitor? Maybe this bug needs to move to the hwinfo package?
You can try, but some monitors simply cannot be detected due to broken DDC or providing wrong data. In this case you need to specify the correct values. AFAIK this is possible during the installation as well. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c28
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c29
--- Comment #29 from Vance Baarda
(In reply to comment #25 from Vance Baarda)
(In reply to comment #24 from Stefan Dirsch)
PXE means in your case that you didn't enable the framebuffer.
What does this mean? How did I not enable the framebuffer? If this is a bad idea, why allow it?
I don't know why, but it seems everbody who is using PXE boot does not specify the vga=0xXXX parameter on the kernel commandline, although nowadays really any monitor is capable of displaying a resolution of 1024x768. So why not simply specifying vga=0x317 by default?!? The result when not doing so is the use of vesa driver (instead of fbdev), which is not recommended to use at all and obviously has all kind of different problems (it seems especially when intel driver is started as second Xserver for testing purposes during installation).
Thanks for all this good info. You have jogged my memory -- I did indeed choose VESA on the initial install screen. I didn't know this was a bad idea. Maybe we shouldn't offer it as a choice. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c30
--- Comment #30 from Stefan Dirsch
Thanks for all this good info. You have jogged my memory -- I did indeed choose VESA on the initial install screen. I didn't know this was a bad idea. Maybe we shouldn't offer it as a choice. There is no other choice for a graphical installation, if kernel framebuffer has been disabled.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c31
--- Comment #31 from Felix Miata
nowadays really any monitor is capable of displaying a resolution of 1024x768
Is any Matrox card capable of any common fb mode higher than 0x314 (800x600) on the ttys (natch, up to at least 2048x1536 in X)? vga=0x317, vga=791, vga=0x31a etc on any of mine gets rejected. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c32
--- Comment #32 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c33
--- Comment #33 from Vance Baarda
What are the remaining issues?
1) Choosing VESA on first install screen caused installation to fail. (Intel i845) 2) We do not detect parameters for Sony SDM-S95D, which causes X to use low resolution. The first problem is pretty serious -- the installation stops with a black screen and no indication of what to do next. The second one is not as bad, but users should not need to enter sync rates manually, especially when the EDID from the monitor is correct. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c34
Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c35
Stefan Dirsch
1) Choosing VESA on first install screen caused installation to fail. (Intel i845) The first problem is pretty serious -- the installation stops with a black screen and no indication of what to do next.
Obviously only happens with broken PXE installations (missing vga parameter). Can't this be finally fixed by the admin?
2) We do not detect parameters for Sony SDM-S95D, which causes X to use low resolution. The second one is not as bad, but users should not need to enter sync rates manually, especially when the EDID from the monitor is correct.
Open a separate bugreport for this against hwinfo. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c36
Vance Baarda
1) Choosing VESA on first install screen caused installation to fail. (Intel i845) The first problem is pretty serious -- the installation stops with a black screen and no indication of what to do next.
Obviously only happens with broken PXE installations (missing vga parameter). Can't this be finally fixed by the admin?
I'll see whether I can reproduce this with a local DVD install.
2) We do not detect parameters for Sony SDM-S95D, which causes X to use low resolution. The second one is not as bad, but users should not need to enter sync rates manually, especially when the EDID from the monitor is correct.
Open a separate bugreport for this against hwinfo.
Will do -- thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
Obviously only happens with broken PXE installations (missing vga parameter). Can't this be finally fixed by the admin? I'll see whether I can reproduce this with a local DVD install. Not sure what you want to reproduce. A local DVD install sets the vga
https://bugzilla.novell.com/show_bug.cgi?id=329581#c37
--- Comment #37 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c38
--- Comment #38 from Vance Baarda
Obviously only happens with broken PXE installations (missing vga parameter). Can't this be finally fixed by the admin? I'll see whether I can reproduce this with a local DVD install. Not sure what you want to reproduce. A local DVD install sets the vga parameter, so fbdev will be in use and you already told me that you can't reproduce the problem with a local DVD install.
With my network install, I chose VESA. With my local DVD install, I didn't change the video setting -- I left it at 1024x768. (I know -- bad me. I didn't remember what I had done on that first install screen.) This time, I'm trying a local DVD install after switching video to VESA using the drop-down list on the first install screen.
Of course you can also unset the vga parameter with a local DVD install and then run into the same problem as with the PXE installation.
I'm not unsetting any params -- I'm just using VESA instead of 1024x768. Install is progressing at the moment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c39
--- Comment #39 from Felix Miata
It is my understanding that at least for VBE 2.0 compliant graphics cards the modes up to 1024x768 are standardized. Of which kind of prehistorical Matrox card are you talking here?
All of them. They were way ahead of the pack when they were new, and currently very usable whether PCI or AGP in newer systems with no silly 3D requirement. e.g. Mystique, Millenium, G200, G400, G450 and maybe even newer. On my 20+ functional machines, not counting those with motherboard video, only two have video cards designed and manufactured this century, and neither of those are in systems that see much use. When I run out of video cards, I goto eBay for Tseng or Matrox for cheap. I know they work when I need SVGA text in DOS, or to simply work in Linux. Just try and find DOS support info for any card designed in the last 10 years. :-p OTOH, just look at the bug traffic from people trying to use NVidia, ATI & Intel video. Sheesh, who needs that aggravation? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c40
Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581
Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c41
--- Comment #41 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c42
--- Comment #42 from Stefan Dirsch
Your PXE installation setup should really be fixed by the admin. This was not a joke. http://en.opensuse.org/SuSE_install_with_PXE_boot#Text_based_YaST_Loads_Inst...
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c43
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c44
--- Comment #44 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c45
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c46
--- Comment #46 from Vance Baarda
https://bugzilla.novell.com/show_bug.cgi?id=329581#c47
--- Comment #47 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c48
Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c49
--- Comment #49 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=329581#c50
--- Comment #50 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c51
--- Comment #51 from Felix Miata
I'll check on both 845G machines I have whether 0x317 (1024x768@16bpp) works. If I should forget about this, please remind me on monday.
It's Monday. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581#c52
--- Comment #52 from Stefan Dirsch
https://bugzilla.novell.com/show_bug.cgi?id=329581#c53
--- Comment #53 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=329581
User mrmazda@ij.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=329581#c54
--- Comment #54 from Felix Miata
0x317 works fine on FSC/845G and Dell Optiplex GX260 (845G).
vga=0x317 does not work fine on my Dell Optiplex GX260 (845G) with latest available BIOS Revision A09. Attempting to use it gives "Undefined video mode number: 317". From the resulting SCAN selecting VESA mode 7 0309 132x25 puts the display to sleep. My display has non-functional DDC. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=329581
User mrmazda@ij.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=329581#c55
--- Comment #55 from Felix Miata
https://bugzilla.novell.com/show_bug.cgi?id=329581
User mrmazda@ij.net added comment
https://bugzilla.novell.com/show_bug.cgi?id=329581#c56
--- Comment #56 from Felix Miata
participants (1)
-
bugzilla_noreply@novell.com