Bug 48027
| Summary: | anacona fails to start xserver | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Gerald Teschl <gt> |
| Component: | anaconda | Assignee: | Aaron Brown <abrown> |
| Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.3 | CC: | katzj |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2001-08-07 14:18:52 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Gerald Teschl
2001-07-09 14:31:55 UTC
Did you try with the 'nofb' boot option? Just found some time to do further testing: (1) Tried a regular cd install -> makes no difference (2) "nofb" -> no difference Messages from anaconda: Silicon Mation Lynx (generic) Monitor: unable to probe ..X started succesfully <snip - traceback> runtime error: cannot open display GUI install worked fine under 7.1 on this laptop. This defect considered MUST-FIX for Fairfax gold-release. Have you tried this laptop with beta2 + the update disk that msf posted to testers-list? That _should_ fix the problem I believe, but if not, it'd be good to know because that would mean there's something else lingering there. I just came back and tested beta2 (I booted from cdrom) and the problem persists. Did you use the update disk? Works in beta 3 if I boot from cdrom. But if I use the pcmcia.img and do an nfs install it will still fail to start the X server. The NFS install fails because it was not trying to use framebuffer. Try adding 'vga=791' and try the NFS install again. Also the traceback you snipped out would be important to have to proceed further with this issue. Yes, there is no "vga=.." option in the bootnet.img. Isn't this a bug? Now I understand why it cannot start the X server. The SVGA server will fail in 800x600 on this laptop since the X server reports invalid mode 800x600 for panel size 1024x768! Brent please review the syslinux config files to verify we have not lost any vga=xxx magic for the various images. I'm looking at the syslinux.cfg file on the bootnet.img from beta3 and this is what I see for the default boot entry: label linux kernel vmlinuz append initrd=initrd.img lang= devfs=nomount ramdisk_size=7168 vga=788 Looks like 'vga=788' is there to me. Are you using a non-English boot disk? Please attach the syslinux.cfg file from the bootdisk that does not work. This is the content of syslinux.cfg from the bootnet.img I have downloaded from the beta ftp site: ------------- default linux prompt 1 timeout 600 display boot.msg F1 boot.msg F2 general.msg F3 expert.msg F4 param.msg F5 rescue.msg label linux kernel vmlinuz append initrd=initrd.img lang=ja devfs=nomount ramdisk_size=7168 label text kernel vmlinuz append initrd=initrd.img lang=ja text devfs=nomount ramdisk_size=7168 label expert kernel vmlinuz append expert initrd=initrd.img lang=ja devfs=nomount ramdisk_size=7168 label ks kernel vmlinuz append ks initrd=initrd.img lang=ja devfs=nomount ramdisk_size=7168 label nofb kernel vmlinuz This is strange: It says "lang=ja" but this is the file ftp://beta@ftp.beta.redhat.com/pub/roswell/linux/i386/images/bootnet.img and not the one from the "ja" subdir!? Aack! The Japanese boot disk is somehow in the root of the Roswell tree. This is not supposed to happen. I pointed this out to the guys in QA who run the ftp site, and they said they would fix it. I'm transferring ownership of this bug to abrown. Has this been resolved? This is a serious problem. This has been fixed according to abrown. |