Re: Getting Asus FM200 working with FreeBSD

2015-07-19 Thread Daniel Peyrolon
Hi there,

I'm using the latest CURRENT image they're updated not long ago.
It somehow manages to pull the right drivers to get X working. :)

Thanks for the suggestion.

El lun., 13 jul. 2015 a las 13:15, Daniel Peyrolon (tucha...@gmail.com)
escribió:

 Hi,

  what about PCBSD?
 Probably should have said something about PCBSD... It didn't work when
 trying to start X, it couldn't find the adapter.
 I will nevertheless try the last images tomorrow, when I can, and let you
 know.

 El lun., 13 jul. 2015 a las 6:19, Julian Elischer (jul...@freebsd.org)
 escribió:

 On 7/11/15 8:29 PM, Daniel Peyrolon wrote:
  Hi everyone,
 
  I'm trying to get FreeBSD-CURRENT up and running with anything different
  than console-only on an Asus FM200. I created a wiki page for it: [1].
 
  I've tried GhostBSD on it, and everything pretty much worked, except
  suspend/resume, and audio.
 what about PCBSD?
  I've CURRENT [2] installed on it, but so far, I haven't been able to
 get it
  working, vesa is not even being loaded (error 19). Any idea,
 suggestions?
 
  [1]: https://wiki.freebsd.org/Laptops/ASUS_FM200
  [2]: FreeBSD BlackBox 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r285358: Fri
 Jul
  10 18:40:27 CEST 2015 root@BlackBox:/usr/obj/usr/src/sys/GENERIC amd64
 
 

 --
 Daniel

-- 
Daniel
___
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: Getting Asus FM200 working with FreeBSD

2015-07-13 Thread Daniel Peyrolon
Hi,

 what about PCBSD?
Probably should have said something about PCBSD... It didn't work when
trying to start X, it couldn't find the adapter.
I will nevertheless try the last images tomorrow, when I can, and let you
know.

El lun., 13 jul. 2015 a las 6:19, Julian Elischer (jul...@freebsd.org)
escribió:

 On 7/11/15 8:29 PM, Daniel Peyrolon wrote:
  Hi everyone,
 
  I'm trying to get FreeBSD-CURRENT up and running with anything different
  than console-only on an Asus FM200. I created a wiki page for it: [1].
 
  I've tried GhostBSD on it, and everything pretty much worked, except
  suspend/resume, and audio.
 what about PCBSD?
  I've CURRENT [2] installed on it, but so far, I haven't been able to get
 it
  working, vesa is not even being loaded (error 19). Any idea, suggestions?
 
  [1]: https://wiki.freebsd.org/Laptops/ASUS_FM200
  [2]: FreeBSD BlackBox 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r285358: Fri
 Jul
  10 18:40:27 CEST 2015 root@BlackBox:/usr/obj/usr/src/sys/GENERIC amd64
 
 

 --
Daniel
___
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

Getting Asus FM200 working with FreeBSD

2015-07-11 Thread Daniel Peyrolon
Hi everyone,

I'm trying to get FreeBSD-CURRENT up and running with anything different
than console-only on an Asus FM200. I created a wiki page for it: [1].

I've tried GhostBSD on it, and everything pretty much worked, except
suspend/resume, and audio.

I've CURRENT [2] installed on it, but so far, I haven't been able to get it
working, vesa is not even being loaded (error 19). Any idea, suggestions?

[1]: https://wiki.freebsd.org/Laptops/ASUS_FM200
[2]: FreeBSD BlackBox 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r285358: Fri Jul
10 18:40:27 CEST 2015 root@BlackBox:/usr/obj/usr/src/sys/GENERIC amd64


-- 
Daniel
___
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


Problems with zpool upgrade embedded_data, and rebooting

2014-08-08 Thread Daniel Peyrolon
Hello everyone,

I just would like to gratuitously rant about something that happened on my
machine.

Basically, I upgraded my zpool to use embedded_data, since it would be more
efficient, and rebooted. (I installed the system with zfs using bsdinstall).
It turned out that gptzfsboot wasn't able to load that filesystem, so I
tried to get it working from a live system that I have on a USB drive.
It didn't work on that particular live system, but, fortunately, someone
could do me a favor and download the latest snapshot, and burn it to my USB
drive.

From there, it was a matter of importing zroot, mounting it at /mnt, and
taking a look at the code of bsdinstall, trying to find the actual command
to update the bootloader.
I could manage to find it, and hopefully, everything worked again. Thanks
to those who helped me :)

What would be the better way to avoid this happening in the future?

-- 
Daniel
___
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


VT and kms is broken on a Lenovo Thinkpad E530

2014-07-18 Thread Daniel Peyrolon
Hello there, I have both and a end-of-June installed kernels (the second at
/boot/kernel.old), and somehow, the console stops working when it changes
its mode.
I'm using the most recent one, I installed xdm and I'm running xorg over
here, without problems.

The problems arise when I try to use the console, the screen just shows a
static image of the last xorg frame, with some weird colors.
What info do you need to fix this?

-- 
Daniel
___
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: VT and kms is broken on a Lenovo Thinkpad E530

2014-07-18 Thread Daniel Peyrolon
I basically installed from a FreeBSD VT enabled ISO. You presume correctly.
On Jul 18, 2014 3:42 PM, Ed Maste ema...@freebsd.org wrote:

 On 18 July 2014 10:32, Daniel Peyrolon tucha...@gmail.com wrote:
  The problems arise when I try to use the console, the screen just shows a
  static image of the last xorg frame, with some weird colors.

 I presume you mean you try to access the console by pressing
 Ctrl-Alt-F1 (for example), and then see the static odd-coloured image.
 This behaviour is consistent with syscons(4), which cannot properly
 switch back to a vty.

 Can you describe how you tried to enable a vt(4) kernel?

___
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: VT and kms is broken on a Lenovo Thinkpad E530

2014-07-18 Thread Daniel Peyrolon
Allright, it seems that the kernel switched back to sysconsole. (kern.vty:
sc)

The wiki says that I should add this to the loader:
To enable Newcons on i386 or amd64, set the loader tunable kern.vty=vt.

I guess that I should do:
# echo kern.vty=\vt\  /boot/loader.conf



2014-07-18 18:58 GMT+02:00 Ed Maste ema...@freebsd.org:

 On 18 July 2014 12:36, Daniel Peyrolon tucha...@gmail.com wrote:
  I basically installed from a FreeBSD VT enabled ISO.

 Ok, it seems those are not available any longer.

 To confirm that you're actually using vt, check sysctl kern.vty.  It
 will report either sc, vt, or an error.  If you get an error the
 kernel predates the addition of that entry, so check sysctl
 hw.syscons and sysctl kern.vt.




-- 
Daniel
___
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: VT and kms is broken on a Lenovo Thinkpad E530

2014-07-18 Thread Daniel Peyrolon
 I guess that I should do:
 # echo kern.vty=\vt\  /boot/loader.conf

That did the trick. Thanks Ed!


2014-07-19 0:57 GMT+02:00 Daniel Peyrolon tucha...@gmail.com:

 Allright, it seems that the kernel switched back to sysconsole. (kern.vty:
 sc)

 The wiki says that I should add this to the loader:
 To enable Newcons on i386 or amd64, set the loader tunable kern.vty=vt.

 I guess that I should do:
 # echo kern.vty=\vt\  /boot/loader.conf



 2014-07-18 18:58 GMT+02:00 Ed Maste ema...@freebsd.org:

 On 18 July 2014 12:36, Daniel Peyrolon tucha...@gmail.com wrote:
  I basically installed from a FreeBSD VT enabled ISO.

 Ok, it seems those are not available any longer.

 To confirm that you're actually using vt, check sysctl kern.vty.  It
 will report either sc, vt, or an error.  If you get an error the
 kernel predates the addition of that entry, so check sysctl
 hw.syscons and sysctl kern.vt.




 --
 Daniel




-- 
Daniel
___
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