Hi Bill, Thanks for the logs -- I had assumed that you were installing all of this on a UEFI setup, but the logs indicate that you have a BIOS-based setup. So, the efifb parameter is not going to have any effect on your machine. The LiveDVD and the installed system logs do not differ significantly to explain the errors you've got.
Regarding the USB port, could you try to type the following command as root? $ echo -1 > /sys/module/usbcore/parameters/autosuspend The logs are suggesting that the network interface is not named eth0 but something else. If you type "ifconfig -a" you should have its actual name -- then typing "dhcpcd <that_interface_name>" should give you an IP address, as long as you have a DHCP server around. Given that you have faced some problems with the Live environment too, could you try a simple thing? If you enter the BIOS, there must be an option that lets you choose between booting in "BIOS legacy mode" and booting in "UEFI mode". If you have that option, could you try to switch it to UEFI and then try to give the LiveDVD another spin? -- note that you won't be able to install Gobo (or to boot into other installed operating systems) unless you update your partition tables. I'm not suggesting that you do that, it's only the results with the LiveDVD test alone that I'm curious to hear about. On another question of yours, we currently have no recipe for building Mate on GoboLinux. Those things usually come in as contributions from our user base. Thank you once again, Lucas On Thu, Dec 22, 2016 at 2:01 PM, William Dudley <[email protected]> wrote: > The more I use this, the more broken-ness I discover. > > The ethernet interface doesn't come up on the hd install. > To get the debug files to you, I had to dick around with a USB flash > drive, complicated by the next bug: > > The hd install keeps turning off the USB port that my keyboard > plugs into. Hence, after a few seconds delay, the first character > typed is lost, but does result in powering up the USB port. I think this > is what is happening, because my keyboard has LED's in it, and they > all go dark a few seconds after I type my last character. > > Anyway, there is no mention of efifb in dmesg in either boot (live or hd). > > The outputs of all the commands are in text files here: > > http://www.dudley.nu/GoboLinux > > I didn't try the experiment with diddling grub, because I don't remember > all > the magic incantations to get that working, and I'm retired, so I only work > on stuff that is fun, and this is getting to be less fun by the minute. > > I'll continue with this debugging some more, but between the broken X, > the broken networking, the broken USB keyboard input, I'm real close to > doing a mkfs on this partition and writing this off to experience. > > Thanks for hanging in there with me. I'm continuing at this point just to > help > you debug GoboLinux for the greater good. > > Bill Dudley > > This email is free of malware because I run Linux. > > On Thu, Dec 22, 2016 at 7:12 AM, Lucas C. Villa Real < > [email protected]> wrote: > >> Thanks, Bill -- and apologies for the bumps! We have had only a handful >> of people actively testing the ISO this time. >> >> The Grub menu generation is currently performed by a third-party tool >> called OSProber. The snapshot of that tool that I used in the ISO was a bit >> broken and had to be tweaked a bit -- it could be that some bug like that >> was hiding and was not properly caught. I will look into reproducing that >> soon and will update the wiki accordingly. >> >> Best regards, >> Lucas >> >> >> >> On Thu, Dec 22, 2016 at 12:46 AM, William Dudley <[email protected]> >> wrote: >> >>> This is major homework. I'll perform some of the experiments tomorrow >>> and get back >>> to you with the results. >>> >>> Another problem: The GoboLinux installer messed up the boot of the >>> existing Ubuntu >>> installation. I used gparted to make the sda1 partition smaller, >>> created sda3, installed >>> GoboLinux to sda3. The resulting grub menu lists both GoboLinux and the >>> pre-existing >>> Ubuntu installation, but the Ubuntu install wouldn't boot; it was trying >>> to load the GoboLinux >>> kernel, if my interpretation of the error message is correct. >>> >>> I repaired the grub install with the Ubuntu live CD, so now I can boot >>> either OS. >>> >>> More tomorrow. >>> >>> Bill Dudley >>> >>> >>> This email is free of malware because I run Linux. >>> >>> On Wed, Dec 21, 2016 at 9:16 PM, Lucas C. Villa Real < >>> [email protected]> wrote: >>> >>>> Hi Bill, >>>> >>>> This is indeed odd. Does /var/log/Xorg.0.log give any hints on the >>>> problem? >>>> Also, could you let me know what's the output of "dmesg | grep efifb" >>>> on the LiveDVD? >>>> Could you tell me whether "efivar -l" outputs anything? >>>> >>>> Regarding your Nvidia setup: >>>> One thing you could try is to edit GRUB's command line to add extra >>>> arguments to the kernel. Some options that may help you are: >>>> video=vesafb:off >>>> video=efifb:off >>>> video=efifb:stride:2048,width:1440,height:900 >>>> >>>> Note that, if you are running in pure UEFI mode (that is, "efivar -l" >>>> outputs something), then booting with video=efifb:off will leave you with a >>>> blank screen until nvidiafb is loaded by udev. >>>> >>>> Regarding your Matrox setup: >>>> Is there any difference in the output of "lsmod" when you boot from the >>>> LiveDVD and when you boot it from the installed system? Ditto for the >>>> output of "dmesg". >>>> >>>> If possible, could you post the output of lsmod and dmesg somewhere? >>>> (e.g. http://gist.github.com) >>>> >>>> Thanks, >>>> Lucas >>>> >>>> >>>> >>>> >>>> On Wed, Dec 21, 2016 at 5:31 PM, William Dudley <[email protected]> >>>> wrote: >>>> >>>>> Addendum. I installed GoboLinux 16 to the hard disk. Tried to fire up >>>>> X. That fails. Run Xorg -configure and startx -- -config >>>>> xorg.conf.new; >>>>> that fails. Reboot the Live DVD. Re-generate the xorg.conf.new that >>>>> I had generated last time. I can get X session from the Live DVD. >>>>> Save >>>>> THAT xorg.conf.new to the GoboLinux partition on the hard disk. >>>>> >>>>> I reboot to GoboLinux on the hard disk. X doesn't work. The two >>>>> different >>>>> xorg.conf files only differ in things that are commented out, and yet, >>>>> the Live >>>>> DVD can run X, and the hard disk installation cannot. >>>>> >>>>> This is beginning to surpass the amount of time that can be wasted on >>>>> a problem >>>>> that I thought we solved 20 years ago -- how to get X running. >>>>> >>>>> Any suggestions on how to get X to run on the hard disk install? >>>>> >>>>> Thanks, >>>>> Bill Dudley >>>>> >>>>> >>>>> This email is free of malware because I run Linux. >>>>> >>>>> On Wed, Dec 21, 2016 at 9:33 AM, William Dudley <[email protected]> >>>>> wrote: >>>>> >>>>>> Lucas, >>>>>> >>>>>> Thanks for the reply. >>>>>> >>>>>> I should have noted in my original email that my video card on this >>>>>> machine is >>>>>> an Nvidia GeForce 6800. I eventually found this page: >>>>>> https://github.com/gobolinux/Documentation/wiki/Afterboot#Kn >>>>>> own_Issues >>>>>> where it says Nvidia cards are "problematic" (my word). >>>>>> >>>>>> I cannot try running the two commands you suggest (at least with the >>>>>> Nvidia card >>>>>> installed), as the screen is unreadable from the very start. I see >>>>>> the boot messages >>>>>> scroll up the screen, and then when the extra-special GoboLinux font >>>>>> kicks in, >>>>>> I get "nothing" as described in my last email. >>>>>> >>>>>> I now know what the screen is *supposed* to look like, as I stuck an >>>>>> old PCI bus >>>>>> video card (Matrox Millenium II) in the machine (no on-motherboard >>>>>> video) and got as far as the >>>>>> text prompt where one is prompted to either run startx or Installer. >>>>>> startx fails >>>>>> as the Xorg on the DVD does not like my ancient Matrox video card. >>>>>> >>>>>> I tried the commands you suggest with the Matrox video card. That >>>>>> also failed to get >>>>>> an X session up. I then edited the xorg.conf.new file so that it had >>>>>> video driver set >>>>>> to "vesa" and now, finally, I have X and "awesome" up and running. >>>>>> >>>>>> So far I can't say I'm real impressed with "awesome", at least not >>>>>> with the Goth "purple >>>>>> on black" theme, and no apparent way (at least from the GUI) to >>>>>> change the theme, >>>>>> wallpaper, window focus rules, etc. I tried "Config" and that put me >>>>>> in a nano session >>>>>> editing a text file, but without significant documentation, I'll not >>>>>> be changing anything >>>>>> in there. I did look, and there appears to be only the one theme >>>>>> installed on the machine. >>>>>> >>>>>> Is it possible to run Mate window manager in GoboLinux? >>>>>> >>>>>> Finally, somebody should update gobolinux.org to fix the search >>>>>> link. The page that >>>>>> needs fixing is this one: https://gobolinux.org/community.html >>>>>> >>>>>> Again, thanks for your help. >>>>>> >>>>>> Bill Dudley >>>>>> retired software developer >>>>>> >>>>>> This email is free of malware because I run Linux. >>>>>> >>>>>> On Tue, Dec 20, 2016 at 10:19 PM, Lucas C. Villa Real < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> On Wed, Dec 21, 2016 at 12:50 AM, William Dudley <[email protected] >>>>>>> > wrote: >>>>>>> >>>>>>>> I've tried two different monitors, and both of them don't work with >>>>>>>> GoboLinux 016 DVD. >>>>>>>> >>>>>>>> The Dell just tells me that the video is out of range, and try to >>>>>>>> use it's native 1600x1200. >>>>>>>> >>>>>>>> The (newer) Viewsonic just shows flashing vertical colored strips. >>>>>>>> Good thing I'm not >>>>>>>> an epileptic. >>>>>>>> >>>>>>>> Is it possible to boot the DVD up in "safe" mode at some "normal" >>>>>>>> video resolution? >>>>>>>> >>>>>>> >>>>>>> Hi Bill, >>>>>>> >>>>>>> Could you try running the two commands below? >>>>>>> >>>>>>> $ Xorg -configure >>>>>>> $ startx -- -config xorg.conf.new >>>>>>> >>>>>>> You may also make changes to the generated xorg.conf.new, as >>>>>>> documented here: >>>>>>> https://github.com/gobolinux/Documentation/wiki/Running-unde >>>>>>> r-VirtualBox >>>>>>> >>>>>>> >>>>>>>> I'd have tried searching the archives, but the search link on the >>>>>>>> gobolinux web site, to >>>>>>>> search.gmane.org, doesn't work, Firefox says search.gmane.org >>>>>>>> doesn't exist. >>>>>>>> >>>>>>>> ping search.gmane.org >>>>>>>> ping: unknown host search.gmane.org >>>>>>>> >>>>>>>> >>>>>>> gmane.org has been shut down recently: >>>>>>> https://lars.ingebrigtsen.no/2016/07/28/the-end-of-gmane/ >>>>>>> >>>>>>> As an alternative, you may use the following resource to search the >>>>>>> mailing list archives: >>>>>>> http://marc.info/?l=gobolinux-users&r=1&w=3 >>>>>>> >>>>>>> Lucas >>>>>>> >>>>>>> _______________________________________________ >>>>>>> gobolinux-users mailing list >>>>>>> [email protected] >>>>>>> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users >>>>>>> >>>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> gobolinux-users mailing list >>>>> [email protected] >>>>> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> gobolinux-users mailing list >>>> [email protected] >>>> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users >>>> >>>> >>> >>> _______________________________________________ >>> gobolinux-users mailing list >>> [email protected] >>> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users >>> >>> >> >> _______________________________________________ >> gobolinux-users mailing list >> [email protected] >> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users >> >> > > _______________________________________________ > gobolinux-users mailing list > [email protected] > http://lists.gobolinux.org/mailman/listinfo/gobolinux-users > >
_______________________________________________ gobolinux-users mailing list [email protected] http://lists.gobolinux.org/mailman/listinfo/gobolinux-users
