running scripts in bulder ./4.sh everything goes ok until passwords and grub configuration

eddowlingiv · 08-07-2016, 09:04 PM

After entering partition locations it asks for Password for root ( no username for regular user prompt just for root ). I ran

grub-install /dev/sda

grub-mkconfig -o /boot/grub/grub.cfg

seemed to execute ok but still does not detect aryalinux os

also when reboot the login is for user aryalinux instead of me as regular user ed ( even though reg user ed exists ) and no root.

In aryalinux login prompt i tried both my root password and my user password neither works although password aryalinux works and there are my partitins there and i can see filesystem but cannot unlock them probably because no way to enter my root password or even user password because login prompt for those users is not there.

Any help would be appreciated- Thanks

chandrakant · 08-07-2016, 09:33 PM

Could you try two things:
1) In case your VirtualBox has some other OS, try getting into the terminal in that and as root do the following:

mount

Look through the output and figure out which partition is used as root for that. Let's assume its /dev/sda1. Then run the following:

grub-install /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg

Then reboot this VM and see if in its grub AryaLinux is listed. In case it gets listed, it means both the OS are intact. Then you can try the step mentioned below:

2) Shutdown all other VMs and from AryaLinux VM, remove the iso file from the virtual DVD/CD drive. Now start aryalinux VM. Get to the terminal and login as root. Then run:

grub-install /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg

Then reboot AryaLinux VM. This time(with the other OS VM shutdown) your grub should list both AryaLinux and the other OS. Then you can independently run both AryaLinux and the other OS by starting their respective VMs.

There is a bug in the os-prober which is why mounted partitions are not read when the grub os-list is prepared. This is why the other OS doesnt get detected when its running.

eddowlingiv · 08-08-2016, 01:06 AM

Quote:

Originally Posted by chandrakant

Could you try two things:
1) In case your VirtualBox has some other OS, try getting into the terminal in that and as root do the following:

mount

Look through the output and figure out which partition is used as root for that. Let's assume its /dev/sda1. Then run the following:

grub-install /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg

Then reboot this VM and see if in its grub AryaLinux is listed. In case it gets listed, it means both the OS are intact. Then you can try the step mentioned below:

2) Shutdown all other VMs and from AryaLinux VM, remove the iso file from the virtual DVD/CD drive. Now start aryalinux VM. Get to the terminal and login as root. Then run:

grub-install /dev/sda
grub-mkconfig -o /boot/grub/grub.cfg

Then reboot AryaLinux VM. This time(with the other OS VM shutdown) your grub should list both AryaLinux and the other OS. Then you can independently run both AryaLinux and the other OS by starting their respective VMs.

There is a bug in the os-prober which is why mounted partitions are not read when the grub os-list is prepared. This is why the other OS doesnt get detected when its running.

to Chandrakant,

Thanks for response I have run the grub commands several times they seem to work but problem above persists.

I tried #1 but the only vm that i thought worked 9 it did previously 0 was Slackel- to my surprise it now says no bootable medium maybe trying to run scripts in arya messed up slackel ?

#2 Removing the iso file and then when reboot it boots into mini tool partition wizard. I then put the iso back and re booted and ran the ./enteral.sh and entered my partitions /dev/sda 1 - root, /dev/sda2- swap, /dev/sda3 is home but then instead of it being fine and prompting for passwd it said no such file or directory for all of these ( I suspect that is because of removing the iso )

I have spent from 12:30 pm to 2:06 am on this and have come close but now it looks like I have to start all over another day. I will go to bed now- have to work tomorrow but I will be available after 5 pmNy time if that is good for you. Thanks for your help so far

eddowlingiv · 08-08-2016, 10:45 PM

To chandrakant,

I started over from creating partitions in minitool in arya linux-this time I got through all 4 scripts of the aryalinux builder. Then i removed aryalinux ISO and Minitool ISO from IDE controller. I rebooted and it booted to my virtual hd for arya linux and commandline prompt for login- I logged in as user eddowlingiv entered password and i was at my user prompt.

The problem then is that the commands sudo su. cd, cd scrripts- get error-no such file or directory. Therefore since the partitions are empty even though I thought I created them correctly ( /dev/sda1-root, /dev/sda2-swap, /dev/sda3-home ) I cannot acces the scripts directory to run ./enteral to install xorg and xfce.

Could the problem be that when partitioning I needed to set as active and format them or are they formatted when create them and add ext4 filesystem and swap. There was a message in installer that said swapon failed.

To fix this can I add back the minitool and correct the partitions and then will I have access to the scripts and do I also have to add back the aryalinux ISO to get the builder back to run scripts. when boot to virtual hd there is no aryalinux desktop with the builder.

Any help- i did watch the video and read website instructions a couple time and google searches and virtualbox forum se4arches. I did not find the answer.

chandrakant · 08-09-2016, 02:24 AM

So if I do understand correctly then installation was a success and you are able to log into your username in the freshly built system. Right? Because it seems like it went successful since you are able to log into the system using your username and password. You can check if everything was successful by running the following command once you log into your username:

cat /sources/build-log

Also you can see if partitions got created properly by doing:

sudo fdisk -l

I guess you are trying to build the rest of the system from within the newly created system and that is the reason why you are facing issues. You need to do this from within the builder DVD's environment.

In case that's done(which I believe is the case), and you need to build xorg and xfce do this:

Re-insert the Builder ISO. The tools are only present in the ISO and would be available only if you boot into the ISO. Do not put the minitool iso. Now boot into the Builder DVD. Then when you get into the desktop follow the instructions at http://aryalinux.org/documentation/d...p-environment/

The base system which got built till now would not have the build scripts and the whole build environment to avoid contamination of the freshly created system. They stay in the Builder DVD itself. So you need the builder DVD till at least you install XFCE/Mate. Then you can remove the builder ISO and boot into the freshly created system and use alps to install everything else.

In case you want to build the rest of the system from within the system itself and not the builder DVD (which I do not recommend) then you need to follow the documentation page: http://aryalinux.org/documentation/d...p-environment/ and skip the initial steps and only start running the commands from here:

sudo alps updatescripts
...
...

eddowlingiv · 08-09-2016, 09:22 AM

Chandrakant,

Thanks for your response. Before I saw your post I had thought that have to add Xorg and then either xfce or Mate ( which one integrates better with aryalinux or is it just a matter of personal preference ? ) that because instructions said to reboot into your newly built system that that meant to run the commands from the terminal in the new system- That id not work as builder tools not there. I had thought that the desktop icons and the builder tool would be put in the new system but then when I realized that is not the case, i did re insert the ISO for aryalinux builder and minitool ( I had to repartition because partitions were not mounted- apparently in mini tool besides creating and applying the partitions and even though you specify ext4 and swap it does not format it. You have to first make the partitions active and then format again. So now I may have to run through all the builder scripts again ( after repartitioning ) because when boot into new system I get error- /boot/grub/i386-pc/normal.mod not found. ( the first time I built the system I did have to do grub- install and then grub-mkconfig o- /boot/grub/grub.cfg and that worked but there were other problems so I had to do i again and this time I had forgot to do the grub commands and when i got the error mentioned zabove- I did research on google and virtual box and found that rescue grub only has limited commands that work and grub- instal..etc and grub-mkconfig...etc do not work.

Also cannot try the cat command and the f disk commands in grub rescue--- Even though before I got the grub error i could log into my user account in the new system after the grub rescue error that ius all I get can't get to login screen.

Therefore I think I have to start over from partitioning and run the builder scripts again. I can't run the scripts now because builder says no such file or directory.

chandrakant · 08-09-2016, 11:19 AM

So are you recreating the partitions and trying from the beginning? In that case can you do the following checks before you start off with the first script and after you are done with preparing the partitions using mini tool:

* Boot into the builder, open up a terminal and run:

sudo su
cd
fdisk -l

It should list all partitions and disks. In case it lists all of them - /dev/sda1, /dev/sda2, /dev/sda3 then you can be sure that the things would work without any problems.

Just to be sure format them yourself using these commands:

mkfs.ext4 /dev/sda1
mkfs.ext4 /dev/sda2
mkswap /dev/sda3

* Once partitioning is done remove minitool. Build the whole base system using 1.sh through 4.sh. There can be only once point where scripts might fail i.e. in ncurses. You can re-run the script and it would proceed smoothly.

* Even if you reboot get back to the builder iso to build to the rest of the system. The process is defined this way so that one can easily mail or post in linuxquestions.org in case a failure happens. If you go about building XFCE etc in the freshly built system itself then its very cumbersome to get error logs so that they can be posted or even take screenshots.

eddowlingiv · 08-10-2016, 12:54 PM

To Chandrakant,

Sorry I did not see this post so I did not do those fdisk check not mkfs command.
However i was able to get through all 4 build scripts I think Ok.

Then when running builder for Xorg and Xfce I think it also completed OK except for following errors :

1.sudo did not get installed ( perhaps if cannot fix that I can login as root when need to - I know not generally a good idea )

2. when running the alps install libmxle...shared-mime-utils command- I received error- no such file or directory for libmxle ( Do I need this file ?)

3. when running the command to rm /etc/x11/xorg.conf.d/* I received error can not remove- no such file or directory ( so hopefully that when installing xorg the system cleaned it afterwards so that it removed it so no need to execute the rm command ? )

4.error occurred in /var/cache/alps/scripts/wayland-protocall.sh ( does this mean wayland did not get installed properly or at all ? )

5.error no such file or directory: aryalinux-customizations when running the alps install aryalinux-themes.....etc

6.when running the alps install audio-video-plugins command- error /var/cache/alps/scripts/alsa-tools.sh ( is this a problem for audio ? )

7. when running the alps install cups....-simple-scan command - It appears that it installs gimp ( and it asked for language for gimp help menu ) and epdfview.. and the other things that the instructions say other things that can be installed at this stage are and it lists them- I was under the impression from that that it meant we could choose which, if any, of those programs to install by using the alps install command like for other programs but apparently the instructions are not clear about that because those items get installed without running an alps install command for it. ( not a big problem I would have installed half of those listed programs anyway )

8. simple scan did not get installed- there is a lot of instructions about this and I took a screenshot but I do not find where it got saved to show you.

Note I powered off the vm but still have virtualbox open. i did not remove the aryalinux builder ISo and try to reboot into virtual hd to see if Xorg and XFCE got installed properly because I did not know if should do that until i hear back from you regarding whether the above errors are mostly harmless and will not prevent me from accesing deswktop environment XFCE or whether one or more of the errors could be a problem

Please respond as soon as you can

Also if everything is Ok now ( except for the above errors if they are minor ones ) and after rebooting ( assuming that boots to XFCE- or do I have to run startx from command line first ? ) and after trying it out for a while, if i like it and want to install it on my physical hardware instead of running it in Virtualbox would I have to go through all the partitioning and the builder scripts or is there a way to use the export feature in virtualbox to install it ? )

Sorry this is so long and detailed but I am new to Virtualbox and to doing this kind of installation ( Instalation of Chakra is about 15-20 minutes and relatively easy to do- only slightly more difficult than Ubuntu which I switched from in 2011 to Chakra )

Thanks for all of you help so far you have been excellent in advice and patience. I hope you can find the time to answer these remaining questions so i can feel comfortable to try to boot into the new system.

chandrakant · 08-10-2016, 02:21 PM

1. sudo already gets installed when the base system is built so its not necessary to reinstall it again. Its just done so that an entry is made in the /etc/alps/installed-list file which contains the list of all installed packages. Some packages depend on sudo so if they find no entry in /etc/alps/installed-list, they would try installing it again. Anyways if such a scenario comes, just do the following and it should not try installing sudo again:

echo "sudo=>`date`" | sudo tee -a /etc/alps/installed-list

2. Are you talking about this? alps install libxml2 desktop-file-utils shared-mime-info? There is an issue with shared-mime-info package. When you build it in a multi-core system, sometimes it fails and sometimes it works. So all you need to do is just re-run the command and it would work. i.e. re-run: alps install libxml2 desktop-file-utils shared-mime-info. And yes shared-mime-info is important. Please do not skip.

3. I do not think that these file get removed by the xorg script. Can you just double check by doing ls /etc/X11/xorg.conf.d/ In case its already dealt with, well, that's good.

4. I guess this is a typo. wayland-protocols is present. You should rather have tried alps install wayland-protocols

5. 5.error no such file or directory: aryalinux-customizations when running the alps install aryalinux-themes.....etc - This is not necessary. I am actually re-doing this file so it kind of not-there now.

6. What was the exact error with audio-video-plugins? If you could provide the logs, I can take a look.

7. Actually alps is designed to install packages alongwith their dependencies. So if you are trying to install cups, cups-filters is a dependency for cups which in turn has its own dependencies. Somewhere in the whole dependency chain, gimp gets pulled in. This sequence of install is necessary because packages would fail if their dependencies are not installed first.

I have never used Chakra Linux so I cannot say anything about it. Does chakra also build everything from source code? Maybe its a distro that installs binaries and not one which gets built on your hardware and that is the reason why it gets installed so fast though I am not sure its that way but most distros provide installable binaries. They do not get compiled on your computer.

Exporting stuff out of Virtualbox into a physical partition may not work. There are ways you can do it but the chances of failure are too many. I have never done it and last time I tried I could not get Vbox additions installed in the Builder DVD. Without that its not possible to share stuff between the VM and host. There is one thing that you can try. Just create a tar out of the partition where you built AryaLinux. Then upload it online maybe into a google drive or something using the builder DVD. Then download it in host, untar it to a fresh partition and using the builder dvd on the physical system enter into it (./enteral.sh). Before building on your hardware though, please go through the linuxfromscratch.org book at least once. I am sure a lot of your questions about AryaLinux would get cleared by going through the LFS book available there because AryaLinux is modelled over LFS.

eddowlingiv · 08-10-2016, 07:01 PM

To Chandrakant,

Thanks for your detailed response. I will respond using the same referenced numbered paragraphs as in my original post but only to the paragraphs where you asked for information or where I need curther clarification.

1. Ok, should I run the echo command regarding sudo or wait to see if there is a problem ?

2. Yes that is the command I was referring to and i had read about the error in multi cores. I did run the command thee (3 ) times and still did not work Should I run it a 4th and 5th time ?
3. In the instruction there is a script to remove the /etc/x11/xorg.conf.d/ the cpmmand had a wild card asterisk at the end ( after the ending / ) Maybe that is a typo in the instructions for that command ?. I will check with the ls command even though rm command said no such file or directory.

4. Ok

5.Ok

6. I had taken a screenshot but can not find where it is saved. How do i get the log file from vm to host to send to you ( will the log file still be in builder or on virtual hd ?

7.Ok I thought that it was something like that re dependencies. Does Thunderbird and the other applications also get installed- the instructions lead me to believe that you can install those programs with alps install command if you want to but that they are optional ( only install what programs needed for your own personal system )

Yes Chakra only provides installable binary files- does not compile from source/ I only mentioned it to show tha I only had previous experience with installing OSes from Binary files ( Ubuntu and then Chakra )

8. simple-scan You did not comment on this I assume because I could not provide the detailed information and an alternate procedure the builder recommended because as previously mentioned for other issues- although I took a screenshot I cannot locate where it got saved.

Regarding exporting vm to physical Hd- Thanks for that information. I was not sure before what to do about that because when searching in google, linuxquestions and Virtualbox forums I came across conflicting information-some commenters said similar things to what you said and others said they only had minor problems that were fixable ( in their specific case ). I believe I will agree with your opinion and not try to export it. I like your suggestion of uploading to google drive and downloading to host. If I do decide to install ayalinux on my hd after trying it out for a while, I will try that.

Thanks again for all your help I saw the time of your response so I know you have been burning the midnight oil like I have ( last night when I had finished all 4 scripts for the base system at 11;30 Pm NY time I did not expect that xorg would take so long ( 5 hrs from 11:30-4:30 am.- I stayed up because every 15 minutes i had to move the mouse to get it to continue ( probably that is due to a setting in KDE that I can change like the setting for the screen going dim or computer going into hibernation- but I was afraid to try to change the setting while the builder was in the process of installing xorg. )

Looking forward to your response and then to actually using aryalinux

Just out of curiosity I believe that you are the developer and maintainer of both the distro and the website and i am curious to you have any plans to add other people to create a team of developers and maintainers ( I might be interested in the future after I get more serious linux experience ). Also do you have any future plans to create your own forum or are you intending to only use Linuxquestions forum ? ( I think Linuxquestions forum is great ( friendly to less experienced users, unlike in some other distros' forums ) but I would think in the future as more people start using aryalinux ( by the way do you know approximately how many users of aryalinux there are ?)that it might be more efficient for aryalinux to have its own specialized forum just for its users whereas Linuxquestions is very large and covers questions for all distros and all issues about Linux )

Again sorry this is so lng but I like to know almost everything about things that i am interested in. I am an all or nothing type of guy.

Thanks again for all your help.

eddowlingiv · 08-13-2016, 11:14 AM

To Chandrakant,

I am posting here because I have not received a response from you ( maybe you are busy which is ok ) maybe my email reply to you went to your spam/junk folder since that was the first time I sent an email to you instead of posting here. This email is copied and pasted from my email ( I removed trhings that are not relevant to the technical issues )

Now for the technical issues in response to your email :

echo "sudo=>`date`" | sudo tee -a /etc/alps/installed-list

returned tee - invalid option

sudo rm -r /var/cache/alps/sources/shared-mime-info-1.6

returned cannot remove- no such file or directory

sudo sed -i "s@\`nproc\`@1@g" /var/cache/alps/scripts/shared-mime-info.sh

returned- sed- no input files

alps install shared-mime-info

returned no such file if you want to force install run alps forceinstall shared-mime-info

returned list of packages it will install and installed them

alps install audio-video-plugins

returned- list of packages and started installing them but then returned

No package " gtk+-3.0

1. Consider adjusting the PKG_CONFIG_PATH environment variables if you installed software in a non-srandard prefix

2. Alternatively, you may set the environment variables GTK_CFLAGS and GTK3_LIBS to avoid the need to call pkg-config

see the pkg-config man pages for more detail

error occurred in executing /var/cache/alps/scripts/alsa-tools.sh

8. Simple-scan--got the same error as for alsa-tools except in alternatively option substitute set environment variables SIMPLE_SCAN_CFLAGS and SIMPLE_SCAN_LIBS

Apparently the problem is no gtk+3.0

Which choice or remedy is best 1 or 2 and how do I do the chosen option

side note I copied and pasted this from a document I created in Calligra word processor because I could not find screen shots I took in mate terminal in aryalinux builder and could not get logs to go from vm to host ( issue of screenshots and logs was mentioned in previous posts ) I could have made it an attachment but i kbnow a lot of people do not like attachments because they fear virus or malware so i copied and pasted it. The only remaining issues are the sudo issue and the alsa- tools and simple-scan gtk issues .

Thanks for all your help so far.

eddowlingiv · 08-13-2016, 02:18 PM

To Chandrakant,

I saw your email from 12:40 today ( but not previous one ) in my spam email box.

I ran the echo command regarding sudo. It did not return anything.

2. Regarding alsa-tools and simple-scan I will try to install after get XFCE running.

3. I removed the aryalinux iso builder from virtualbox and rebooted to virtual hd and got to my regular user prompt and ran startx.

Returned- xinit server error. terminating error(1)

Shouild I have run " startx as root instead of regular user ?

Is there a command I should have run before or instead of " startx " ?

eddowlingiv · 08-14-2016, 03:07 PM

To Chandrakant,

I will try to post the code for my Xorg.o.log file ( I do not know if I can get it to work in code setting - never tried before in this forum )

Code:

[     6.855] 
X.Org X Server 1.17.4
Release Date: 2015-10-28
[     6.855] X Protocol Version 11, Revision 0
[     6.855] Build Operating System: Linux 4.2.6-1-CHAKRA x86_64 
[     6.855] Current Operating System: Linux edwardddowlingiv-chpc 4.5.7-1-CHAKRA #1 SMP PREEMPT Wed Jun 8 20:00:23 BST 2016 x86_64
[     6.855] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=04c91cfb-23e6-4084-aa5e-f371a9208bd6 rw quiet resume=UUID=3dff1536-4465-4c50-b01b-14433dcdd014
[     6.855] Build Date: 19 November 2015  10:15:23PM
[     6.855]  
[     6.855] Current version of pixman: 0.32.8
[     6.855] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[     6.855] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[     6.856] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Aug 14 11:47:44 2016
[     6.857] (==) Using config directory: "/etc/X11/xorg.conf.d"
[     6.857] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[     6.858] (==) No Layout section.  Using the first Screen section.
[     6.858] (==) No screen section available. Using defaults.
[     6.858] (**) |-->Screen "Default Screen Section" (0)
[     6.858] (**) |   |-->Monitor "<default monitor>"
[     6.859] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[     6.859] (==) Automatically adding devices
[     6.859] (==) Automatically enabling devices
[     6.859] (==) Automatically adding GPU devices
[     6.862] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[     6.862] 	Entry deleted from font path.
[     6.866] (==) FontPath set to:
	/usr/share/fonts/misc/,
	/usr/share/fonts/TTF/,
	/usr/share/fonts/Type1/,
	/usr/share/fonts/100dpi/,
	/usr/share/fonts/75dpi/
[     6.866] (==) ModulePath set to "/usr/lib/xorg/modules"
[     6.866] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[     6.867] (II) Loader magic: 0x817d60
[     6.867] (II) Module ABI versions:
[     6.867] 	X.Org ANSI C Emulation: 0.4
[     6.867] 	X.Org Video Driver: 19.0
[     6.867] 	X.Org XInput driver : 21.1
[     6.867] 	X.Org Server Extension : 9.0
[     6.868] (EE) systemd-logind: failed to get session: PID 738 does not belong to any known session
[     6.868] (II) xfree86: Adding drm device (/dev/dri/card0)
[     6.870] (--) PCI:*(0:0:2:0) 8086:0102:1458:d000 rev 9, Mem @ 0xfb400000/4194304, 0xe0000000/268435456, I/O @ 0x0000ff00/64
[     6.870] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[     6.870] (II) LoadModule: "glx"
[     6.872] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[     6.889] (II) Module glx: vendor="X.Org Foundation"
[     6.889] 	compiled for 1.17.4, module version = 1.0.0
[     6.889] 	ABI class: X.Org Server Extension, version 9.0
[     6.889] (==) AIGLX enabled
[     6.889] (==) Matched intel as autoconfigured driver 0
[     6.889] (==) Matched intel as autoconfigured driver 1
[     6.889] (==) Matched modesetting as autoconfigured driver 2
[     6.889] (==) Matched fbdev as autoconfigured driver 3
[     6.889] (==) Matched vesa as autoconfigured driver 4
[     6.889] (==) Assigned the driver to the xf86ConfigLayout
[     6.889] (II) LoadModule: "intel"
[     6.889] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
[     6.893] (II) Module intel: vendor="X.Org Foundation"
[     6.893] 	compiled for 1.17.4, module version = 2.99.917
[     6.893] 	Module class: X.Org Video Driver
[     6.893] 	ABI class: X.Org Video Driver, version 19.0
[     6.893] (II) LoadModule: "modesetting"
[     6.893] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[     6.894] (II) Module modesetting: vendor="X.Org Foundation"
[     6.894] 	compiled for 1.17.4, module version = 1.17.4
[     6.894] 	Module class: X.Org Video Driver
[     6.894] 	ABI class: X.Org Video Driver, version 19.0
[     6.894] (II) LoadModule: "fbdev"
[     6.897] (WW) Warning, couldn't open module fbdev
[     6.897] (II) UnloadModule: "fbdev"
[     6.897] (II) Unloading fbdev
[     6.897] (EE) Failed to load module "fbdev" (module does not exist, 0)
[     6.897] (II) LoadModule: "vesa"
[     6.897] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[     6.900] (II) Module vesa: vendor="X.Org Foundation"
[     6.900] 	compiled for 1.17.4, module version = 2.3.4
[     6.900] 	Module class: X.Org Video Driver
[     6.900] 	ABI class: X.Org Video Driver, version 19.0
[     6.900] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
	i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
	915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
	Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
	GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
[     6.900] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
[     6.900] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
[     6.900] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
[     6.900] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     6.900] (II) VESA: driver for VESA chipsets: vesa
[     6.900] (++) using VT number 7

[     6.905] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20151218
[     6.905] (II) intel(0): SNA compiled from 2.99.917-622-gde44aaa
[     6.906] (WW) Falling back to old probe method for modesetting
[     6.906] (WW) Falling back to old probe method for vesa
[     6.907] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 2000
[     6.907] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx; using a maximum of 4 threads
[     6.907] (II) intel(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[     6.907] (==) intel(0): Depth 24, (--) framebuffer bpp 32
[     6.907] (==) intel(0): RGB weight 888
[     6.907] (==) intel(0): Default visual is TrueColor
[     6.907] (II) intel(0): Output VGA1 has no monitor section
[     6.907] (II) intel(0): Enabled output VGA1
[     6.907] (II) intel(0): Output HDMI1 has no monitor section
[     6.907] (II) intel(0): Enabled output HDMI1
[     6.907] (II) intel(0): Output DP1 has no monitor section
[     6.907] (II) intel(0): Enabled output DP1
[     6.907] (II) intel(0): Output HDMI2 has no monitor section
[     6.907] (II) intel(0): Enabled output HDMI2
[     6.907] (II) intel(0): Output HDMI3 has no monitor section
[     6.907] (II) intel(0): Enabled output HDMI3
[     6.907] (II) intel(0): Output DP2 has no monitor section
[     6.908] (II) intel(0): Enabled output DP2
[     6.908] (II) intel(0): Output DP3 has no monitor section
[     6.908] (II) intel(0): Enabled output DP3
[     6.908] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
[     6.908] (II) intel(0): Output VIRTUAL1 has no monitor section
[     6.908] (II) intel(0): Enabled output VIRTUAL1
[     6.908] (--) intel(0): Output VGA1 using initial mode 1920x1080 on pipe 0
[     6.908] (==) intel(0): TearFree disabled
[     6.908] (==) intel(0): DPI set to (96, 96)
[     6.908] (II) Loading sub module "dri2"
[     6.908] (II) LoadModule: "dri2"
[     6.908] (II) Module "dri2" already built-in
[     6.908] (II) Loading sub module "present"
[     6.908] (II) LoadModule: "present"
[     6.908] (II) Module "present" already built-in
[     6.908] (II) UnloadModule: "modesetting"
[     6.908] (II) Unloading modesetting
[     6.908] (II) UnloadModule: "vesa"
[     6.908] (II) Unloading vesa
[     6.908] (==) Depth 24 pixmap format is 32 bpp
[     6.913] (II) intel(0): SNA initialized with Sandybridge (gen6, gt1) backend
[     6.913] (==) intel(0): Backing store enabled
[     6.913] (==) intel(0): Silken mouse enabled
[     6.915] (II) intel(0): HW Cursor enabled
[     6.915] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[     6.916] (==) intel(0): DPMS enabled
[     6.916] (==) intel(0): Display hotplug detection enabled
[     6.916] (II) intel(0): [DRI2] Setup complete
[     6.916] (II) intel(0): [DRI2]   DRI driver: i965
[     6.916] (II) intel(0): [DRI2]   VDPAU driver: va_gl
[     6.916] (II) intel(0): direct rendering: DRI2 enabled
[     6.917] (II) intel(0): hardware support for Present enabled
[     6.917] (--) RandR disabled
[     6.953] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[     6.953] (II) AIGLX: enabled GLX_ARB_create_context
[     6.953] (II) AIGLX: enabled GLX_ARB_create_context_profile
[     6.953] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[     6.953] (II) AIGLX: enabled GLX_INTEL_swap_event
[     6.953] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[     6.953] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
[     6.953] (II) AIGLX: enabled GLX_ARB_fbconfig_float
[     6.953] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[     6.953] (II) AIGLX: enabled GLX_ARB_create_context_robustness
[     6.954] (II) AIGLX: Loaded and initialized i965
[     6.954] (II) GLX: Initialized DRI2 GL provider for screen 0
[     6.957] (II) intel(0): switch to mode 1920x1080@60.0 on VGA1 using pipe 0, position (0, 0), rotation normal, reflection none
[     6.957] (II) intel(0): Setting screen physical size to 508 x 285
[     7.044] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[     7.044] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[     7.044] (**) Power Button: Applying InputClass "system-keyboard"
[     7.044] (II) LoadModule: "evdev"
[     7.044] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[     7.047] (II) Module evdev: vendor="X.Org Foundation"
[     7.047] 	compiled for 1.17.4, module version = 2.10.0
[     7.047] 	Module class: X.Org XInput Driver
[     7.047] 	ABI class: X.Org XInput driver, version 21.1
[     7.047] (II) Using input driver 'evdev' for 'Power Button'
[     7.047] (**) Power Button: always reports core events
[     7.047] (**) evdev: Power Button: Device: "/dev/input/event3"
[     7.047] (--) evdev: Power Button: Vendor 0 Product 0x1
[     7.047] (--) evdev: Power Button: Found keys
[     7.047] (II) evdev: Power Button: Configuring as keyboard
[     7.047] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event3"
[     7.047] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[     7.047] (**) Option "xkb_rules" "evdev"
[     7.047] (**) Option "xkb_model" "pc105"
[     7.047] (**) Option "xkb_layout" "us"
[     7.047] (II) config/udev: Adding input device Power Button (/dev/input/event2)
[     7.047] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[     7.047] (**) Power Button: Applying InputClass "system-keyboard"
[     7.047] (II) Using input driver 'evdev' for 'Power Button'
[     7.047] (**) Power Button: always reports core events
[     7.047] (**) evdev: Power Button: Device: "/dev/input/event2"
[     7.047] (--) evdev: Power Button: Vendor 0 Product 0x1
[     7.047] (--) evdev: Power Button: Found keys
[     7.047] (II) evdev: Power Button: Configuring as keyboard
[     7.047] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3/event2"
[     7.047] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[     7.047] (**) Option "xkb_rules" "evdev"
[     7.047] (**) Option "xkb_model" "pc105"
[     7.047] (**) Option "xkb_layout" "us"
[     7.048] (II) config/udev: Adding input device GiGa HiD (/dev/input/event0)
[     7.048] (**) GiGa HiD: Applying InputClass "evdev keyboard catchall"
[     7.048] (**) GiGa HiD: Applying InputClass "system-keyboard"
[     7.048] (II) Using input driver 'evdev' for 'GiGa HiD'
[     7.048] (**) GiGa HiD: always reports core events
[     7.048] (**) evdev: GiGa HiD: Device: "/dev/input/event0"
[     7.048] (--) evdev: GiGa HiD: Vendor 0x1ea7 Product 0x2
[     7.048] (--) evdev: GiGa HiD: Found keys
[     7.048] (II) evdev: GiGa HiD: Configuring as keyboard
[     7.048] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.0/0003:1EA7:0002.0001/input/input1/event0"
[     7.048] (II) XINPUT: Adding extended input device "GiGa HiD" (type: KEYBOARD, id 8)
[     7.048] (**) Option "xkb_rules" "evdev"
[     7.048] (**) Option "xkb_model" "pc105"
[     7.048] (**) Option "xkb_layout" "us"
[     7.048] (II) config/udev: Adding input device GiGa HiD (/dev/input/event1)
[     7.048] (**) GiGa HiD: Applying InputClass "evdev pointer catchall"
[     7.049] (**) GiGa HiD: Applying InputClass "evdev keyboard catchall"
[     7.049] (**) GiGa HiD: Applying InputClass "system-keyboard"
[     7.049] (II) Using input driver 'evdev' for 'GiGa HiD'
[     7.049] (**) GiGa HiD: always reports core events
[     7.049] (**) evdev: GiGa HiD: Device: "/dev/input/event1"
[     7.049] (--) evdev: GiGa HiD: Vendor 0x1ea7 Product 0x2
[     7.049] (--) evdev: GiGa HiD: Found 12 mouse buttons
[     7.049] (--) evdev: GiGa HiD: Found scroll wheel(s)
[     7.049] (--) evdev: GiGa HiD: Found relative axes
[     7.049] (--) evdev: GiGa HiD: Found x and y relative axes
[     7.049] (--) evdev: GiGa HiD: Found absolute axes
[     7.049] (II) evdev: GiGa HiD: Forcing absolute x/y axes to exist.
[     7.049] (--) evdev: GiGa HiD: Found keys
[     7.049] (II) evdev: GiGa HiD: Configuring as mouse
[     7.049] (II) evdev: GiGa HiD: Configuring as keyboard
[     7.049] (II) evdev: GiGa HiD: Adding scrollwheel support
[     7.049] (**) evdev: GiGa HiD: YAxisMapping: buttons 4 and 5
[     7.049] (**) evdev: GiGa HiD: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[     7.049] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.1/0003:1EA7:0002.0002/input/input2/event1"
[     7.049] (II) XINPUT: Adding extended input device "GiGa HiD" (type: KEYBOARD, id 9)
[     7.049] (**) Option "xkb_rules" "evdev"
[     7.049] (**) Option "xkb_model" "pc105"
[     7.049] (**) Option "xkb_layout" "us"
[     7.049] (II) evdev: GiGa HiD: initialized for relative axes.
[     7.049] (WW) evdev: GiGa HiD: ignoring absolute axes.
[     7.049] (**) GiGa HiD: (accel) keeping acceleration scheme 1
[     7.049] (**) GiGa HiD: (accel) acceleration profile 0
[     7.049] (**) GiGa HiD: (accel) acceleration factor: 2.000
[     7.049] (**) GiGa HiD: (accel) acceleration threshold: 4
[     7.049] (II) config/udev: Adding input device GiGa HiD (/dev/input/mouse0)
[     7.049] (**) GiGa HiD: Applying InputClass "system-keyboard"
[     7.049] (II) No input driver specified, ignoring this device.
[     7.049] (II) This device may have been added with another device file.
[     7.049] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event9)
[     7.049] (II) No input driver specified, ignoring this device.
[     7.049] (II) This device may have been added with another device file.
[     7.050] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event10)
[     7.050] (II) No input driver specified, ignoring this device.
[     7.050] (II) This device may have been added with another device file.
[     7.050] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event11)
[     7.050] (II) No input driver specified, ignoring this device.
[     7.050] (II) This device may have been added with another device file.
[     7.050] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event12)
[     7.050] (II) No input driver specified, ignoring this device.
[     7.050] (II) This device may have been added with another device file.
[     7.050] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=7 (/dev/input/event13)
[     7.050] (II) No input driver specified, ignoring this device.
[     7.050] (II) This device may have been added with another device file.
[     7.050] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event4)
[     7.050] (II) No input driver specified, ignoring this device.
[     7.050] (II) This device may have been added with another device file.
[     7.051] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event5)
[     7.051] (II) No input driver specified, ignoring this device.
[     7.051] (II) This device may have been added with another device file.
[     7.051] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event6)
[     7.051] (II) No input driver specified, ignoring this device.
[     7.051] (II) This device may have been added with another device file.
[     7.051] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event7)
[     7.051] (II) No input driver specified, ignoring this device.
[     7.051] (II) This device may have been added with another device file.
[     7.051] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event8)
[     7.051] (II) No input driver specified, ignoring this device.
[     7.051] (II) This device may have been added with another device file.

chandrakant · 08-15-2016, 01:55 AM

This Xorg.0.log seems to be the log from Chakra(The host Linux). Could you post the log for AryaLinux? Here is how you can do that. Run the VM without the builder iso and then boot into the freshly build system. Run startx and then shutdown the VM. Now reboot the VM with the iso into the builder disk. Then from a terminal:

sudo su
mount /dev/sda1 /mnt/
cp -v /mnt/var/log/Xorg.0.log /home/aryalinux/Desktop

This would copy Arya's Xorg log into the desktop. Now from within the VM you can open up firefox and post the file.

chandrakant · 08-15-2016, 01:58 AM

Just before you do that can you check and see if there are any files in /etc/X11/xorg.conf.d/ In case there are any files please delete them and then try restart. Please remember to do this inside the vm after booting into the freshly built system.