Re: Cannot startx on FreeBSD10 Current

[Miguel Clara]

On Sat Jun 22 04:39:09 2013, Matthew D. Fuller wrote:
> On Sat, Jun 22, 2013 at 12:29:49AM + I heard the voice of
> Miguel Clara, and lo! it spake thus:
>>
>> The only way to turn off is but "force" and this can cause damage to
>> filesystems, this is indeed a very big issue, and I'm not sure if
>> its specific to KMS or some freebsd-current problem cause I have no
>> way to look into it!
>
> One little trick you might try is to login to a second VTY and run
> something like "sleep 60 ; shutdown -r now" before switching back and
> running startx; if it's just a UI crash/lockup rather than a
> whole-system such, that'll give you a clean reboot without FS damage.
> Of course, if it's a whole-system lockup, it won't, but that also
> means you can tell which it is, which may be diagnostically useful...
>
> (ssh'ing in from another machine is another way to track such things,
> but may be less convenient depending on your own setup...)
>
>

I tried the ssh trick, first thing that crossed my mind... but its no 
good after the reboot or shutdown, I guess by then sshd is not running 
anymore but I have no way to know!

I know this is something in active development but this seams to be of 
significant importance, I wish I could help somehow but I can't even 
see what's happening!
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Matthew D. Fuller]

On Sat, Jun 22, 2013 at 12:29:49AM + I heard the voice of
Miguel Clara, and lo! it spake thus:
> 
> The only way to turn off is but "force" and this can cause damage to
> filesystems, this is indeed a very big issue, and I'm not sure if
> its specific to KMS or some freebsd-current problem cause I have no
> way to look into it!

One little trick you might try is to login to a second VTY and run
something like "sleep 60 ; shutdown -r now" before switching back and
running startx; if it's just a UI crash/lockup rather than a
whole-system such, that'll give you a clean reboot without FS damage.
Of course, if it's a whole-system lockup, it won't, but that also
means you can tell which it is, which may be diagnostically useful...

(ssh'ing in from another machine is another way to track such things,
but may be less convenient depending on your own setup...)


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Miguel Clara]

Mark Felder  feld.me> writes:

> 
> On Fri, 14 Jun 2013 12:05:13 -0500, Miguel Clara 
gmail.com>  
> wrote:
> >
> > I wouldn't consider having no visual output from a laptop when you
> > reboot/shutdown low priority...
> > But that's not for me to decide... in any case is there any Bug
> > Report/PR open about this that we can follow up? I would like to keep up
> > to date with this.
> >
> 
> The driver is still in heavy development and considered incomplete, so  
> there is no PR. Keep an eye on this Wiki page, and note the FAQ at the  
> bottom:
> 
> https://wiki.freebsd.org/Intel_GPU
> ___
> freebsd-current  freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe 
freebsd.org"
> 
> 

Sorry to get back to this, but I was testing other stuff in the meantime and
had no time to reply.

It seams that the issue is not just the black screen, the laptop won't trun
off at all or reboot!

If the other problem wasn't already a big issue this is indeed a major one!

The only way to turn off is but "force" and this can cause damage to
filesystems, this is indeed a very big issue, and I'm not sure if its
specific to KMS or some freebsd-current problem cause I have no way to look
into it!




___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

xorg-server bug fix committed (was: Re: Cannot startx on FreeBSD10 Current)

[Dimitry Andric]

On Jun 17, 2013, at 00:02, Anton Shterenlikht  wrote:
...
> http://www.freebsd.org/cgi/query-pr.cgi?pr=179625
> 
> Perhaps you could follow it up with the details of
> your graphics card, Xorg log, etc.


Just as a heads-up, this was due to a bug in xorg-server 1.7.7, and it
has been patched in ports with the following commit:

http://svnweb.freebsd.org/changeset/ports/321157

-Dimitry

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Anton Shterenlikht]

From: Walter Hurry 
Subject: Re: Cannot startx on FreeBSD10 Current
Date: Sun, 16 Jun 2013 17:53:53 + (UTC)

On Sun, 16 Jun 2013 11:27:36 +0100, Anton Shterenlikht wrote:

> From: Walter Hurry 
>   Subject: Re: Cannot startx on FreeBSD10 Current Date: Fri, 14 
Jun 
2013
>   20:50:59 + (UTC)
> 
>   On Fri, 14 Jun 2013 09:33:48 -0700, Craig Rodrigues wrote:
> 
>   > On Fri, Jun 14, 2013 at 7:42 AM, Walter Hurry 

>   > wrote:
>   > 
>   >> I'm running FreeBSD 10.0-CURRENT (r251572) amd64 in a 
VirtualBox VM.
>   >>
>   >>
>   >  Recently, I started mentoring a Google Summer of Code 
student 
for
>   >  the
>   > FreeBSD project.
>   > I worked with the student to set up a VM to run FreeBSD, with 
full
>   > graphical desktop.
>   > 
>   > You might want to follow the instructions that the student 
followed
>   > here:
>   > 
>   > 
http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-
for-
>   doing-gsoc-work/
>   > 
>   > Only interesting details:
>   >   (1)  Student used VMWare player instead of VirtualBox  
(shouldn't
>   >   be a
>   > big deal).
>   >   (2)  We used pkgng to install binary packages (3)  We used 
one of
>   >   the pkgng mirrors, since pkgng packages from
>   > FreeBSD.org aren't fully available yet
>   > 
>   > Other than that, things worked fine, and the student was able 
to get
>   > a full FreeBSD with graphical desktop inside a VM.
> 
>   Thanks for the pointer to the blog.
> 
>   With hindsight, it seems that your student avoided the issue I 
ran into
>   by installing precompiled binaries, whereas I was using the 
Ports
>   collection.
> 
>   The problem was the Clang miscompilation of xorg-server, as 
pointed out
>   so kindly by Jung-uk Kim.
> 
> Have you, or anybody else, sent a PR on this?

I haven't. I don't know whether anyone else has.

http://www.freebsd.org/cgi/query-pr.cgi?pr=179625

Perhaps you could follow it up with the details of
your graphics card, Xorg log, etc.

Anton
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Walter Hurry]

On Sun, 16 Jun 2013 11:27:36 +0100, Anton Shterenlikht wrote:

> From: Walter Hurry 
>   Subject: Re: Cannot startx on FreeBSD10 Current Date: Fri, 14 Jun 
2013
>   20:50:59 + (UTC)
> 
>   On Fri, 14 Jun 2013 09:33:48 -0700, Craig Rodrigues wrote:
> 
>   > On Fri, Jun 14, 2013 at 7:42 AM, Walter Hurry 

>   > wrote:
>   > 
>   >> I'm running FreeBSD 10.0-CURRENT (r251572) amd64 in a 
VirtualBox VM.
>   >>
>   >>
>   >  Recently, I started mentoring a Google Summer of Code student 
for
>   >  the
>   > FreeBSD project.
>   > I worked with the student to set up a VM to run FreeBSD, with 
full
>   > graphical desktop.
>   > 
>   > You might want to follow the instructions that the student 
followed
>   > here:
>   > 
>   > http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-
for-
>   doing-gsoc-work/
>   > 
>   > Only interesting details:
>   >   (1)  Student used VMWare player instead of VirtualBox  
(shouldn't
>   >   be a
>   > big deal).
>   >   (2)  We used pkgng to install binary packages (3)  We used 
one of
>   >   the pkgng mirrors, since pkgng packages from
>   > FreeBSD.org aren't fully available yet
>   > 
>   > Other than that, things worked fine, and the student was able 
to get
>   > a full FreeBSD with graphical desktop inside a VM.
> 
>   Thanks for the pointer to the blog.
> 
>   With hindsight, it seems that your student avoided the issue I 
ran into
>   by installing precompiled binaries, whereas I was using the Ports
>   collection.
> 
>   The problem was the Clang miscompilation of xorg-server, as 
pointed out
>   so kindly by Jung-uk Kim.
> 
> Have you, or anybody else, sent a PR on this?

I haven't. I don't know whether anyone else has.

> I used xorg-server with clang until recently.
> Now I'm on r249781. I think the problem started after the perl updates,
> but I might be wrong.
> Anyway, if nobody filed a PR yet, I'll do it.

Thanks.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Anton Shterenlikht]

From: Walter Hurry 
Subject: Re: Cannot startx on FreeBSD10 Current
Date: Fri, 14 Jun 2013 20:50:59 + (UTC)

On Fri, 14 Jun 2013 09:33:48 -0700, Craig Rodrigues wrote:

> On Fri, Jun 14, 2013 at 7:42 AM, Walter Hurry 
> wrote:
> 
>> I'm running FreeBSD 10.0-CURRENT (r251572) amd64 in a VirtualBox VM.
>>
>>
>  Recently, I started mentoring a Google Summer of Code student for the
> FreeBSD project.
> I worked with the student to set up a VM to run FreeBSD, with full
> graphical desktop.
> 
> You might want to follow the instructions that the student followed
> here:
> 
> http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-
doing-gsoc-work/
> 
> Only interesting details:
>   (1)  Student used VMWare player instead of VirtualBox  (shouldn't 
be a
> big deal).
>   (2)  We used pkgng to install binary packages (3)  We used one of 
the
>   pkgng mirrors, since pkgng packages from
> FreeBSD.org aren't fully available yet
> 
> Other than that, things worked fine, and the student was able to get a
> full FreeBSD with graphical desktop inside a VM.

Thanks for the pointer to the blog.

With hindsight, it seems that your student avoided the issue I ran into 
by installing precompiled binaries, whereas I was using the Ports 
collection.

The problem was the Clang miscompilation of xorg-server, as pointed out 
so kindly by Jung-uk Kim.

Have you, or anybody else, sent a PR on this?
I used xorg-server with clang until recently.
Now I'm on r249781. I think the problem started
after the perl updates, but I might be wrong.
Anyway, if nobody filed a PR yet, I'll do it.

Anton



___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Walter Hurry]

On Fri, 14 Jun 2013 09:33:48 -0700, Craig Rodrigues wrote:

> On Fri, Jun 14, 2013 at 7:42 AM, Walter Hurry 
> wrote:
> 
>> I'm running FreeBSD 10.0-CURRENT (r251572) amd64 in a VirtualBox VM.
>>
>>
>  Recently, I started mentoring a Google Summer of Code student for the
> FreeBSD project.
> I worked with the student to set up a VM to run FreeBSD, with full
> graphical desktop.
> 
> You might want to follow the instructions that the student followed
> here:
> 
> http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-
doing-gsoc-work/
> 
> Only interesting details:
>   (1)  Student used VMWare player instead of VirtualBox  (shouldn't be a
> big deal).
>   (2)  We used pkgng to install binary packages (3)  We used one of the
>   pkgng mirrors, since pkgng packages from
> FreeBSD.org aren't fully available yet
> 
> Other than that, things worked fine, and the student was able to get a
> full FreeBSD with graphical desktop inside a VM.

Thanks for the pointer to the blog.

With hindsight, it seems that your student avoided the issue I ran into 
by installing precompiled binaries, whereas I was using the Ports 
collection.

The problem was the Clang miscompilation of xorg-server, as pointed out 
so kindly by Jung-uk Kim.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[miguelmclara]

Portupgrade upgrades installed ports...  But you might also need to fetch and 
update you're /usr/ports.

portsnap fetch update 

Should do the trick!


Enviado a partir do meu smartphone BlackBerry® www.blackberry.com

-Original Message-
From: Walter Hurry 
Sender: owner-freebsd-current@freebsd.orgDate: Fri, 14 Jun 2013 19:57:01 
To: 
Subject: Re: Cannot startx on FreeBSD10 Current

On Fri, 14 Jun 2013 18:20:32 +0200, Koop Mast wrote:

> On 14-6-2013 18:11, Walter Hurry wrote:
>> On Fri, 14 Jun 2013 15:56:26 +, Miguel Clara wrote:
>>> I had the same issue the first time I've built Xorg, when I've first
>>> read:
>>> "As of revision r235859 of FreeBSD 10.0-CURRENT, no patches should be
>>> needed to get GEM/KMS. See Intel_GPU
>>> <https://wiki.freebsd.org/Intel_GPU> for more details." at
>>> https://wiki.freebsd.org/Xorg
>>>
>>> I assume It worked out of the box just b installing Xorg...
>>>
>>> Intel_GPU <https://wiki.freebsd.org/Intel_GPU> page however pointed me
>>> to the right direction, which is:
>>> WITH_NEW_XORG=true and WITH_KMS=true to /etc/make.conf.  and then
>>> rebuild (portmaster -f for example) and it now starts.
>>>
>>> I still have some problems though... I can't switch to console with
>>> CRTL+ALT+F1...2..3... etc I get a very weired screen, like my kde all
>>> nuts... the good thing is I can at least switch back to kde.
>>> I also noted that at shutdown/reboot I get a black screen  nothing
>>> shows on screen, I just have to wait for it to turn off... I get the
>>> feeling that this is somehow related!
>>>
>>> Please note that I'm using a Acer S3 Ultrabook with a integrated Intel
>>> card... AMD info is here: https://wiki.freebsd.org/AMD_GPU
>>>
>> Thanks for the reply.
>>
>> Well, this is in a VM, which reports the graphics adapter as:
>>
>> vgapci0@pci0:0:2:0:  class=0x03 card=0x chip=0xbeef80ee
>> rev=0x00 hdr=0x00
>>  vendor = 'InnoTek Systemberatung GmbH'
>>  device = 'VirtualBox Graphics Adapter'
>>  class  = display subclass   = VGA
>>
>> When I put the two suggested enties into make.conf, xorg-server fails
>> to compile, saying that it requires dri >= 7.8, whereas my installed
>> dri is 7.6.1_3,2 (from the Ports collection).
> You will need to run portmaster/portupgrade -a first to update your
> installed ports first. Mostly dri/libGL/libdrm. Did you know that the
> emulators/virtualbox-ose-additions port has xorg-server drivers for
> virtualbox video.
> 
Thanks, but my ports are fully up-to-date, and virtualbox-ose-additions 
is installed and running.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

SOLVED: Cannot startx on FreeBSD10 Current

[Walter Hurry]

On Fri, 14 Jun 2013 14:21:46 -0400, Jung-uk Kim wrote:

> 
> I had a similar problem a week ago.  Basically, that Clang version
> mis-compiles xorg-server.  You may want to try the latest Clang on -
> -CURRENT or build it with "make USE_GCC=any".
> 

Thenk you so much! Yes, recompiling xorg-server with gcc did the trick.

Deeply appreciated.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Walter Hurry]

On Fri, 14 Jun 2013 18:20:32 +0200, Koop Mast wrote:

> On 14-6-2013 18:11, Walter Hurry wrote:
>> On Fri, 14 Jun 2013 15:56:26 +, Miguel Clara wrote:
>>> I had the same issue the first time I've built Xorg, when I've first
>>> read:
>>> "As of revision r235859 of FreeBSD 10.0-CURRENT, no patches should be
>>> needed to get GEM/KMS. See Intel_GPU
>>>  for more details." at
>>> https://wiki.freebsd.org/Xorg
>>>
>>> I assume It worked out of the box just b installing Xorg...
>>>
>>> Intel_GPU  page however pointed me
>>> to the right direction, which is:
>>> WITH_NEW_XORG=true and WITH_KMS=true to /etc/make.conf.  and then
>>> rebuild (portmaster -f for example) and it now starts.
>>>
>>> I still have some problems though... I can't switch to console with
>>> CRTL+ALT+F1...2..3... etc I get a very weired screen, like my kde all
>>> nuts... the good thing is I can at least switch back to kde.
>>> I also noted that at shutdown/reboot I get a black screen  nothing
>>> shows on screen, I just have to wait for it to turn off... I get the
>>> feeling that this is somehow related!
>>>
>>> Please note that I'm using a Acer S3 Ultrabook with a integrated Intel
>>> card... AMD info is here: https://wiki.freebsd.org/AMD_GPU
>>>
>> Thanks for the reply.
>>
>> Well, this is in a VM, which reports the graphics adapter as:
>>
>> vgapci0@pci0:0:2:0:  class=0x03 card=0x chip=0xbeef80ee
>> rev=0x00 hdr=0x00
>>  vendor = 'InnoTek Systemberatung GmbH'
>>  device = 'VirtualBox Graphics Adapter'
>>  class  = display subclass   = VGA
>>
>> When I put the two suggested enties into make.conf, xorg-server fails
>> to compile, saying that it requires dri >= 7.8, whereas my installed
>> dri is 7.6.1_3,2 (from the Ports collection).
> You will need to run portmaster/portupgrade -a first to update your
> installed ports first. Mostly dri/libGL/libdrm. Did you know that the
> emulators/virtualbox-ose-additions port has xorg-server drivers for
> virtualbox video.
> 
Thanks, but my ports are fully up-to-date, and virtualbox-ose-additions 
is installed and running.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Jung-uk Kim]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 2013-06-14 10:42:23 -0400, Walter Hurry wrote:
> I'm running FreeBSD 10.0-CURRENT (r251572) amd64 in a VirtualBox
> VM.
> 
> Everything seems to work properly, except that I cannot 'startx'.
> All I get is a blank screen and an apparently hung box. The only
> way out of it is Machine -> Close -> Send the shutdown signal.
> 
> The following appears in /var/log/Xorg.0.log:
> 
> --
>
> 

> (II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless 
> otherwise stated. (II) VBoxVideo(0): RandR 1.2 enabled, ignore the
> following RandR disabled message.
> 
> Fatal server error: AddScreen/ScreenInit failed for driver 0
> 
> 
> Please consult the The X.Org Foundation support at
> http://wiki.x.org for help. Please also check the log file at
> "/var/log/Xorg.0.log" for additional information.
> 
> Segmentation fault at address 0x290 
> --
>
>  I don't know how to investigate this further. Any ideas?

I had a similar problem a week ago.  Basically, that Clang version
mis-compiles xorg-server.  You may want to try the latest Clang on
- -CURRENT or build it with "make USE_GCC=any".

Jung-uk Kim
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.20 (FreeBSD)

iQEcBAEBAgAGBQJRu186AAoJECXpabHZMqHOKTEH/jBqWoDWAL9JbMhdLE//fb8/
2RXV+gqqdxqnRCD7gMDtZN9RtMBCyqvJPXYxfM45u4HprvWBKlVkAWsG6qB6MSN8
N5kmkfQyfVPB0AZhKBu2Z39Wbv/zJnjfXKWjCQfVsOYq4qHNFTMKjXZSOKcKNcuB
yRxeJMQsH3q6Goj2vYe02ZLPiBz10UaDaLYJOWBbmEFymvZs4WGDirH+NnHHoeMZ
5a7jKGxPfUp1xRL6KcXCiBOGowpqq7BQCE1tsAQF2MJTHtyQyM9cQFHVGzM2FpM/
TuXz6D5/94zPwNB27TxkBAkYuXzUYR+gjzf4QKSV+KkC2zXSYGOXJgGthmjt9XM=
=zFrZ
-END PGP SIGNATURE-
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Craig Rodrigues]

On Fri, Jun 14, 2013 at 7:42 AM, Walter Hurry  wrote:

> I'm running FreeBSD 10.0-CURRENT (r251572) amd64 in a VirtualBox VM.
>

 Recently, I started mentoring a Google Summer of Code student for the
FreeBSD project.
I worked with the student to set up a VM to run FreeBSD, with full
graphical desktop.

You might want to follow the instructions that the student followed here:

http://blogs.freebsdish.org/rodrigc/2013/05/24/setting-up-a-vm-for-doing-gsoc-work/

Only interesting details:
  (1)  Student used VMWare player instead of VirtualBox  (shouldn't be a
big deal).
  (2)  We used pkgng to install binary packages
  (3)  We used one of the pkgng mirrors, since pkgng packages from
FreeBSD.org aren't fully available yet

Other than that, things worked fine, and the student was able to get a full
FreeBSD with graphical desktop inside
a VM.

--
Craig
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Koop Mast]

On 14-6-2013 18:11, Walter Hurry wrote:

On Fri, 14 Jun 2013 15:56:26 +, Miguel Clara wrote:

I had the same issue the first time I've built Xorg, when I've first
read:
"As of revision r235859 of FreeBSD 10.0-CURRENT, no patches should be
needed to get GEM/KMS. See Intel_GPU
 for more details." at
https://wiki.freebsd.org/Xorg

I assume It worked out of the box just b installing Xorg...

Intel_GPU  page however pointed me
to the right direction, which is:
WITH_NEW_XORG=true and WITH_KMS=true to /etc/make.conf.  and then
rebuild (portmaster -f for example) and it now starts.

I still have some problems though... I can't switch to console with
CRTL+ALT+F1...2..3... etc I get a very weired screen, like my kde all
nuts... the good thing is I can at least switch back to kde.
I also noted that at shutdown/reboot I get a black screen  nothing
shows on screen, I just have to wait for it to turn off... I get the
feeling that this is somehow related!

Please note that I'm using a Acer S3 Ultrabook with a integrated Intel
card... AMD info is here: https://wiki.freebsd.org/AMD_GPU


Thanks for the reply.

Well, this is in a VM, which reports the graphics adapter as:

vgapci0@pci0:0:2:0: class=0x03 card=0x chip=0xbeef80ee
rev=0x00 hdr=0x00
 vendor = 'InnoTek Systemberatung GmbH'
 device = 'VirtualBox Graphics Adapter'
 class  = display
 subclass   = VGA

When I put the two suggested enties into make.conf, xorg-server fails to
compile, saying that it requires dri >= 7.8, whereas my installed dri is
7.6.1_3,2 (from the Ports collection).
You will need to run portmaster/portupgrade -a first to update your 
installed ports first. Mostly dri/libGL/libdrm. Did you know that the 
emulators/virtualbox-ose-additions port has xorg-server drivers for 
virtualbox video.



___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Mark Felder]

On Fri, 14 Jun 2013 12:05:13 -0500, Miguel Clara   
wrote:


I wouldn't consider having no visual output from a laptop when you
reboot/shutdown low priority...
But that's not for me to decide... in any case is there any Bug
Report/PR open about this that we can follow up? I would like to keep up
to date with this.



The driver is still in heavy development and considered incomplete, so  
there is no PR. Keep an eye on this Wiki page, and note the FAQ at the  
bottom:


https://wiki.freebsd.org/Intel_GPU
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Walter Hurry]

On Fri, 14 Jun 2013 15:56:26 +, Miguel Clara wrote:
> 
> I had the same issue the first time I've built Xorg, when I've first
> read:
> "As of revision r235859 of FreeBSD 10.0-CURRENT, no patches should be
> needed to get GEM/KMS. See Intel_GPU
>  for more details." at
> https://wiki.freebsd.org/Xorg
> 
> I assume It worked out of the box just b installing Xorg...
> 
> Intel_GPU  page however pointed me
> to the right direction, which is:
> WITH_NEW_XORG=true and WITH_KMS=true to /etc/make.conf.  and then
> rebuild (portmaster -f for example) and it now starts.
> 
> I still have some problems though... I can't switch to console with
> CRTL+ALT+F1...2..3... etc I get a very weired screen, like my kde all
> nuts... the good thing is I can at least switch back to kde.
> I also noted that at shutdown/reboot I get a black screen  nothing
> shows on screen, I just have to wait for it to turn off... I get the
> feeling that this is somehow related!
> 
> Please note that I'm using a Acer S3 Ultrabook with a integrated Intel
> card... AMD info is here: https://wiki.freebsd.org/AMD_GPU
> 
Thanks for the reply.

Well, this is in a VM, which reports the graphics adapter as:

vgapci0@pci0:0:2:0: class=0x03 card=0x chip=0xbeef80ee 
rev=0x00 hdr=0x00
vendor = 'InnoTek Systemberatung GmbH'
device = 'VirtualBox Graphics Adapter'
class  = display
subclass   = VGA

When I put the two suggested enties into make.conf, xorg-server fails to 
compile, saying that it requires dri >= 7.8, whereas my installed dri is 
7.6.1_3,2 (from the Ports collection). 

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Miguel Clara]

On 06/14/13 15:24, Mark Felder wrote:
> On Fri, 14 Jun 2013 11:11:17 -0500, Miguel Clara  
> wrote:
>
>>
>> Is this something that will be fixed anytime soon?
>> What about the black screen on reboot? Is that normal?
>
> That is also the same issue -- once you start KMS you can't get a tty
back, which is what would happen with other video drivers when you kill
X as part of the reboot process. I believe this is considered low
priority right now, but it will eventually behave properly.

I wouldn't consider having no visual output from a laptop when you
reboot/shutdown low priority...
But that's not for me to decide... in any case is there any Bug
Report/PR open about this that we can follow up? I would like to keep up
to date with this.

And thanks for explaining the situation!

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Mark Felder]

On Fri, 14 Jun 2013 11:11:17 -0500, Miguel Clara   
wrote:




Is this something that will be fixed anytime soon?
What about the black screen on reboot? Is that normal?


That is also the same issue -- once you start KMS you can't get a tty  
back, which is what would happen with other video drivers when you kill X  
as part of the reboot process. I believe this is considered low priority  
right now, but it will eventually behave properly.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Miguel Clara]

On 06/14/13 15:02, Mark Felder wrote:
> On Fri, 14 Jun 2013 10:56:26 -0500, Miguel Clara
>  wrote:
>
>> I still have some problems though... I can't switch to console with
>> CRTL+ALT+F1...2..3... etc I get a very weired screen, like my kde all
>> nuts... the good thing is I can at least switch back to kde.
>> I also noted that at shutdown/reboot I get a black screen  nothing
>> shows on screen, I just have to wait for it to turn off... I get the
>> feeling that this is somehow related!
>
> With KMS you can't get to a tty after it's running. That's known
> errata, so once you start X you can't leave it without a reboot.

I see, thanks for the info, since this works on linux I was thinking If
I forgot some step...
Is this something that will be fixed anytime soon?

What about the black screen on reboot? Is that normal? I know a friend
who had this issue and AFAIK he was able to solved it, but he is using 9.1.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Mark Felder]

On Fri, 14 Jun 2013 10:56:26 -0500, Miguel Clara   
wrote:



I still have some problems though... I can't switch to console with
CRTL+ALT+F1...2..3... etc I get a very weired screen, like my kde all
nuts... the good thing is I can at least switch back to kde.
I also noted that at shutdown/reboot I get a black screen  nothing
shows on screen, I just have to wait for it to turn off... I get the
feeling that this is somehow related!


With KMS you can't get to a tty after it's running. That's known errata,  
so once you start X you can't leave it without a reboot.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Cannot startx on FreeBSD10 Current

[Miguel Clara]

On 06/14/13 14:42, Walter Hurry wrote:
> I'm running FreeBSD 10.0-CURRENT (r251572) amd64 in a VirtualBox VM.
>
> Everything seems to work properly, except that I cannot 'startx'. All I 
> get is a blank screen and an apparently hung box. The only way out of it 
> is Machine -> Close -> Send the shutdown signal.
>
> The following appears in /var/log/Xorg.0.log:
>
> --
> 
> (II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless 
> otherwise stated.
> (II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled 
> message.
>
> Fatal server error:
> AddScreen/ScreenInit failed for driver 0
>
>
> Please consult the The X.Org Foundation support 
>at http://wiki.x.org
>  for help. 
> Please also check the log file at "/var/log/Xorg.0.log" for additional 
> information.
>
> Segmentation fault at address 0x290
> --
>
> I don't know how to investigate this further. Any ideas?
>
> ___
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Hi,

I had the same issue the first time I've built Xorg, when I've first read:
"As of revision r235859 of FreeBSD 10.0-CURRENT, no patches should be
needed to get GEM/KMS. See Intel_GPU
 for more details." at
https://wiki.freebsd.org/Xorg

I assume It worked out of the box just b installing Xorg...

Intel_GPU  page however pointed me
to the right direction, which is:
WITH_NEW_XORG=true and WITH_KMS=true to /etc/make.conf.  and then
rebuild (portmaster -f for example) and it now starts.

I still have some problems though... I can't switch to console with
CRTL+ALT+F1...2..3... etc I get a very weired screen, like my kde all
nuts... the good thing is I can at least switch back to kde.
I also noted that at shutdown/reboot I get a black screen  nothing
shows on screen, I just have to wait for it to turn off... I get the
feeling that this is somehow related!

Please note that I'm using a Acer S3 Ultrabook with a integrated Intel
card... AMD info is here: https://wiki.freebsd.org/AMD_GPU


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Cannot startx on FreeBSD10 Current

[Walter Hurry]

I'm running FreeBSD 10.0-CURRENT (r251572) amd64 in a VirtualBox VM.

Everything seems to work properly, except that I cannot 'startx'. All I 
get is a blank screen and an apparently hung box. The only way out of it 
is Machine -> Close -> Send the shutdown signal.

The following appears in /var/log/Xorg.0.log:

--

(II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless 
otherwise stated.
(II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled 
message.

Fatal server error:
AddScreen/ScreenInit failed for driver 0


Please consult the The X.Org Foundation support 
 at http://wiki.x.org
 for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional 
information.

Segmentation fault at address 0x290
--

I don't know how to investigate this further. Any ideas?

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"