|
Bugzilla – Full Text Bug Listing |
| Summary: | graphical installation does not start on Dell Latitude D505 -> Textmode installation possible | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Forgotten User 1GBkbCnI0A <forgotten_1GBkbCnI0A> |
| Component: | Installation | Assignee: | Stefan Dirsch <sndirsch> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P2 - High | CC: | ms, yast2-maintainers |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
hwinfo for Dell Latitude D505
log files SaX2 log file from running system |
||
|
Description
Forgotten User 1GBkbCnI0A
2005-08-26 05:52:08 UTC
Please provide YaST2 logs, see: http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST Ok, here is the requested information: hwinfo for the Dell Latitude D505 and a tar archive containing /etc/X11/xorg.conf and /var/log (from /). I will attach both files. Created attachment 47832 [details]
hwinfo for Dell Latitude D505
Created attachment 47833 [details]
log files
A non-existing glx module shouldn't matter. I couldn't find anything obvious in the logfiles. The only interesting thing I can see is that you use "vesa" for installation. Maybe you were the first that tried this with 10.0. Steffen, how can I force to use "vesa" during installation. Maybe I can reproduce this problem. Actually I did not request vesa mode. I made an PXE/TFTP boot installation, the parameters from tftpboot/pxelinux.cfg/ default are: ==== # install label install100b3 kernel linux.10b3 append initrd=initrd.10b3 ramdisk_size=65536 showopts server=192.168.2.1 serverdir=/dist/i386/10.0b3/CD1 install=nfs://192.168.2.1/dist/i386/10.0b3/CD1 ==== so no videomode request at all. An additional info: I had trouble setting up X with the sax2-detected monitor (only 1024x768, while there is a 1400x1050 display - but no mode for that without 855resolution). Maybe there is a problem with the detection or the modes for the detected monitor in Instsys? ad 5: 'x11i=vesa' or just 'vga=normal' see below ad 6: yast will revert to use the vesa driver if no framebuffer is available. So unless you explicitly set an fb mode via vga=xxx you *do* make yast use the vesa driver Steffen, x11i=vesa does *not* work. The fbdev driver is used nevertheless. I tried 'vga=normal', =0x317, =0x305, all with the same result. I have the feeling, that the BIOS of the DELL is fscked up. Sorry. The Xorg.0. log file says something about VESA modi not available and refresh rates not fitting the display. Can I try something else? Stefan, no you can't do anything right now. I wanted to force a "vesa" driver installation to be able to reproduce this problem, but failed so far. Ok. Currently using "x11i=<drive>" option is broken. Using vga=normal - which results in a vesa driver installation - works fine for me. Therefore I need to close this one as WORKSFORME. The broken "x11i=<drive>" option will be handled in a seperate bugreport. OK. I digged a bit deeper and found strange values for monitor data in the log file during installation startup and later during configuration using SaX2. Is it possible, that a) the monitor database has wrong values, or b) the BIOS of the netobook has wrong values? I do not know where the information comes from (horizontal sync rates 30-40kHz, see SaX.log). Sorry for re-opening, but I believe, both problems are connected. Created attachment 48478 [details]
SaX2 log file from running system
Don't know. This is all kind of strange. Try "acceleratedx=1" as boot option to use the native i810 driver. Maybe this will work for you. Thanks, but it does not help either :( It complains about missing agpgart device. Let us close this problem for now, or lets have a look at this after the release rush. Thank you for your effort! I have no idea why vesa is used for installation. Intel 855 works with fbdev. I would like to know, which framebuffer resolutions this notebooks knows about. Which resolutions (F2) can you choose during installation (boot menu)? Soory for the delay, I was not able to test over the weekend. Booting from first CD I can choose: "Text Mode", "VESA", "800 x 600" and "1024 x 768". If I choose 800x600 or 1024x768 manually, the graphical system starts, VESA yields the same result as above -> no X server. So why the hell do you chose "VESA"? What is the default? As stated above I made a PXE installation with the command line from the CD isolinux.cfg. This usually brings up a graphical installation on all other computers I have (regular PCs and a Fujitsu-Siemens Lifebook E 4010 notebook). The Dell I am only able to install in text mode. I did not choose "VESA", this seems to be the default value, if I am using pxelinux without any parameter for video mode. If this is by design or because of my BIOS, then OK - we cannot do anything about this. I have no idea, why i855 does not work together with "vesa" driver, but you should simply add another option to your kernel command line in your isolinux.cfg file. Something like "vga=0x317" (1024x768@16). |