On 9/17/06, Leandro Motta Barros <[EMAIL PROTECTED]> wrote: > First, I tried the LiveCD. The booting process was going smoothly. > Then, I think it has detected that it could use a 1440x900 nvidiafb > framebuffer (I'm using a GeForce FX Go5200 here, so sounds OK, though > I have always used vesafb instead of nvidiafb). > > Then it "changed something". (I would say that it switched from a > "real text mode console" to a "framebuffer console", but I don't know > even if it is possible to make such a switch). Anyway, "something > changed": the console was resized to something larger than my screen. > I mean, it was resized to something so large that its bottom half was > "hidden bellow the screen", just the upper half was visible.
We noticed some weird things happening when framebuffer drivers were being loaded by udev, too. We have all fbdev drivers blacklisted now, which means that they need to be either explicitly called by modprobe, statically compiled or simply make usage of vesafb, as in 012. The next pre-release is going to have that fixed. > I tried running X, but it didn't work. Duh, I forgot to take note on > the error, but IIRC it is the same as I describe a few paragraphs > below. I also ran the Installer, but it was not nice to use it being > only able to see its upper half ;-) hehe, that's true. We've detected 2 problems on Xorg: we had some Sun drivers compiled in, which were making the autodetection to hang on Qemu and on real machines. The other problem is that Xorg is looking for /Programs/Xorg/Variable/log, which doesn't exist. We'll probably be recompiling it this week to fix this second issue (the first one is already gone). > So, I decided to reboot passing different options to the kernel, in > order to use my old and trusted vesafb. Here I make my first concrete > request: would it be possible to include an editable line in the > LiveCD grub? (I mean, just pressing "e" to edit, changing what I want > and then booting). That would be nice, because I had to boot my normal > Gobo system, mount the CD, and search for the configuration file that > tells me which line was being used to boot. Hmm, I don't think so, because that's not Grub -- that's isolinux. I have never looked more closely to its options, but I think that it's possible to have more than one "boot profile" (but again without allowing the modification of a given instance). > Then, I booted without using the "video=vesafb:off" option that was > apparently being used. This gave me my familiar 1024x768 framebuffer > console. I tried starting X, but got an error (the same error as > before, IIRC): > > (==) Using default built-in configuration (53 lines) > [...] > Fatal server error: > Cannot run in framebuffer mode. Please specify busIDs for all > framebuffer devices. This is the reason why we're booting in text-mode in the iso :-( > My next step was running the Installer, and install this pre-release > in my spare partition. Installation proceeded without errors. Well, > actually, I noticed a message saying > > Error creating lilo.conf file > > but I ignored it. Thanks for the report. > So, I booted this freshly installed GoboLinux. It says "Welcome to > GoboLinux 013-pre1". Isn't it pre2? (Just exercising my nitpicking > skills ;-)) Ops :-) > Tried running X, didn't work (again, forgot to write the error message > :-(). What I noticed is that there was no 'xorg.conf' file, so X tried > to use its "default built-in" configurations. Previous GoboLinux > versions used to ship a 'xorg.conf', didn't they? Yes. We did a rollback on that decision last week, and now we have a sample xorg.conf again. > Then I copied the 'xorg.conf' file I use in my "production GoboLinux", > changed it to use framebuffer instead of the nvidia driver, and tried > to startx again. Got another error, but this time I wrote some > seemingly useful messages: > > (EE) Failed to load module "bitmap" (module does not exist, 0) > (EE) Failed to load module "pcidata" (module does not exist, 0) Indeed, IIRC bitmap module is out of the build, but I can't say anything about pcidata. We'll give a look at it when recompiling Xorg this week, thanks. > Finally, I noticed that 'man' doesn't work: the 'Man' wrapper is > broken, it contains some invalid characters (something like "ãã"). > Removing these characters from 'Man', fixed it. Eww. > Then it was late and I went to bed. > > That's it for now. I'll have time for playing with these things in the > next weeks, so if you want me to perform some specific tests in the > upcoming days, just ask me. Thanks! -- Lucas powered by /dev/dsp _______________________________________________ gobolinux-devel mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
