Date: Thu, 05 Jan 2017 20:20:16 +0100 From: swjatoslaw gerus <milstar2@eml.cc> To: Polytropon <freebsd@edvax.de> Cc: freebsd-questions@freebsd.org Subject: Re: Mr.Edison tactic ... performed to date -thank you for assistance Message-ID: <1483644016.1447892.838558553.55CAAF02@webmail.messagingengine.com> In-Reply-To: <20170105193234.37780fbb.freebsd@edvax.de> References: <1483454858.4190708.835937993.300F2713@webmail.messagingengine.com> <20170103160657.GB43153@neutralgood.org> <20170103203023.b2396c95.freebsd@edvax.de> <861swjx6mv.fsf@WorkBox.homestead.org> <1483475176.874533.836320369.7B612577@webmail.messagingengine.com> <20170103214548.1d726a06.freebsd@edvax.de> <1483564140.1178887.837521761.7D1930C8@webmail.messagingengine.com> <20170105004510.44e54ddc.freebsd@edvax.de> <1483639288.1431717.838467905.64F6B28C@webmail.messagingengine.com> <20170105193234.37780fbb.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank you for assistance ,would check after this e-mail sended
but your suggest possibly not correlated with local Hamburg University
conditions
Linux 64 ,which can work with wlan asked
WPA & WPA 2 Enterprise
tunneled TLS
CA -Zertifikate keine (no)
CA-Zertifikate -ignorieren(no certifikate needed )
PAP
anonymous@uni-hamburg.de (that for all , can read all)
-----------------------------------------------------------------------------------------
autorwlanid@uni-hamburg.de ( that is author specific )
passw (that is author specific)
---------------------------------------------------------
ipv4 -automat
ipv4 -automat
that is for linux ,for windows and mac another instructions
####################################################
Can be ,that local wlan would not accept freebsd
than ideja of author to use more stable as linux platform freebsd
or solaris from start
is false
###########
--
swjatoslaw gerus
milstar2@eml.cc
On Thu, Jan 5, 2017, at 07:32 PM, Polytropon wrote:
> On Thu, 05 Jan 2017 19:01:28 +0100, swjatoslaw gerus wrote:
> > And problem
> > #################
> > Graphics enter do not work
>
> You probably did not install X and configure it. Please
> refer to my previous message which lists what to do,
> including pointers to the relevant documentation.
>
>
>
> > arrow ,tab - if use tab system typed to password + *
>
> It's much simpler: username <Enter> password <Enter>.
> No tab or arrow key is needed.
>
>
>
> > sytem will not go no enter on graphics press simple enter from keyboard
>
> Because the software for this kind of operation has not
> been installed yet. As a multi-purpose operating system,
> FreeBSD does not install X automatically.
>
>
>
> > in this test reboot ,terminal short time black -in this time sandisk
> > out
> > if not out sandisk in this time ,than downloading process started new
>
> You probably mean installation process, not download.
>
>
>
> > ifconfig -lot of text ...
>
> Text with relevant information. Is the wireless device listed?
>
>
>
> > no carrier
>
> That probably refers to your wired network card, msk0. Your
> wireless network card is iwn0. You should see both in the
> output of "ifconfig -a".
>
> Example from my home PC:
>
> vr0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
> options=82808<VLAN_MTU,WOL_UCAST,WOL_MAGIC,LINKSTATE>
> ether de:ad:be:ef:00:01
> inet 123.456.789.100 netmask 0xffffff00 broadcast 123.456.789.255
> media: Ethernet autoselect (none)
> status: no carrier
>
> This network card isn't connected to anything.
>
>
>
> > ifconfig ssid -interface ssid does not exist
>
> You're entering a nonsense command. See "man ifconfig" for
> how to use this tool, or even better, check the following
> excellent page which is one of the primary sources on how
> to get wireless working without pain:
>
> http://www.wonkity.com/~wblock/docs/html/wireless.html
>
> Of course the handbook also has plenty of information:
>
> https://www.freebsd.org/doc/handbook/network-wireless.html
>
> It's so dead simple, hardly anything will stop you from
> activating your WLAN as long as the hardware is supported,
> which seems to be the case for you.
>
> In /etc/wpa_supplicant.conf, set your access information:
>
> network={
> ssid="<SSID>"
> psk="<key>"
> }
>
> Replace <SSID> with the SSID you want to connect to, and
> <key> with the corresponding password.
>
> Add those to /etc/rc.conf:
>
> wlans_iwn0="wlan0"
> ifconfig_wlan0="WPA SYNCDHCP"
>
> Then just restart networking:
>
> # service netif restart
>
> The wireless connection should be up now.
>
> For diagnostic purposes, do the following "step by step" and
> check if (and where) problems occur:
>
> # ifconfig wlan0 create wlandev iwn0
> # wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf
> # dhclient wlan0
>
> This is what the system basically does on its own from the
> configuration data.
>
>
>
> > another variant -poweroff
> > poweron without sandisk
> > lot of text before login
>
> That is the kernel messages and the system services. They
> show you what exactly is happening - a great help in case
> of problems.
>
>
>
> > sended down signal to iwn0
>
> What signal? How?
>
>
>
> --
> Polytropon
> Magdeburg, Germany
> Happy FreeBSD user since 4.0
> Andra moi ennepe, Mousa, ...
--
http://www.fastmail.com - mmm... Fastmail...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1483644016.1447892.838558553.55CAAF02>