Description of Problem:
Tried a nfs install on my laptop (beta hw #12). Anaconda will try to start
but seems to fail and exits. No usable errors (anaconda exited abnormally).
everything is stopped and unmounted it is hard to figure out
what is going wrong.
This is a SMI 910 card which works with both the fbdev and the XF86_SVGA
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
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:
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:
append initrd=initrd.img lang=ja devfs=nomount ramdisk_size=7168
append initrd=initrd.img lang=ja text devfs=nomount ramdisk_size=7168
append expert initrd=initrd.img lang=ja devfs=nomount ramdisk_size=7168
append ks initrd=initrd.img lang=ja devfs=nomount ramdisk_size=7168
This is strange: It says "lang=ja" but this is the file
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
Has this been resolved? This is a serious problem.
This has been fixed according to abrown.