Search results

The problem is on an external storage disk, not the system drive

Windows does not even sees it, nor does testdisk suite

I have a dual boot system, Win 10 with a FreeBSD bootable Ext.Drive. The Win module has an ext. NTFS storage disk that has failed apparently- lost partition & bad clusters. CHKDSK and similar tools have been ineffective as neither the disk nor the partition is seen. Booting with a KNOPPIX USB...

See expanded post and apparent solution at possible solution

I am using an external bootable disk on my laptop for a dual boot UNIX access. But I have a persistent post installation problem of Release 12.0; System boots into 'mountroot' consistently. I've published several POSTS, Google querries, and followed several leads but nothing fruitfull has...

I am going to make a more detailed POST of the problem

Now I have the following partition / slices: da2p1 efi filesystem da2p2 freebsd-ufs da2p3 freebsd-swap should I label as below without applicable labeling to the efi system da2p2 freebsd-ufs ==> gptrootfs da2p3 freebsd-swap ==> gptswap Now, should I put a label e.g...

I usually label my disks for this very reason but had not done this yet, as the USB device configuration was consistent in dmesg on each installation step and I was still working on my set up. However the data is as follows; ls dev | grep da dev/da0 /dev/da0s1 /dev/da1 /dev/da1s1 /dev/da2...

I should have mentioned, that this is an OS in an external disk configuration. Again mounting from the mountroot prompt only makes the system disk available, other disks, cdrom etc. would each have to be added separately as the fstab file is not seen or run.

Can bsdinstall be used to change, fix or repair a post-installation OS; specifically a network issue. Yes, editing the netconfig file may suffice but one is never sure if this covers all the entries required. Thanks!

I have completed several 'repeat' installation of release 12.0 from an ISO disc to a 'new' clean HD using the GPT formatting option. As a pre-installation step of each, the prior file partition(s) were deleted and then then the disk filesystems was destroyed. At the initial startup and...

What do I have to add and to which file? I already have this network={ ssid="ZZZvvvvvvvvvvccc" psk="sktgknt83boodl43n" in the /etc/wpa_supplicant.conf file, do I need to have it somewhere else? if so where?

How do I correct this?

Point about the static IP taken, but before that why is the 192.168.1.83 invisible to the WiFi, is there something amiss with my setup? If I use a cable to a hub it 'glows', I can remotely ping it, use (s)ftp or have shell access (sshd) to it.

Following up from the last posting: The ifconfig utility added the following (wlan0) to the listing of re0 and lo0. Here is the wlan0 w/ some modifications. lan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 ether **:**:**:**:**:** hwaddr...

Thanks! Quite correct, the two machines are on the same LAN, using the same 192.168.1.... address.

Hi! I am running a double booted HP Laptop (17-ak013dx; O/S Windows 64 bit) with a USB mounted external HD, from which FreeBSD 11.1 is operating I have configured an Edimax EW-7811Un WiFi Nano adapter as follows - Added to /boot/loader.conf: if_urtwn_load="YES"...

Nope! I was thinking of the FreeBSD 11.1-RELEASE workaround but I do see the hardware limitation. I;ll just have to sweat it out. Thanks again!

Now that you have mentioned TrueOS, is it possible that the use of an emulator can be an effective 'work around'. If feasible would you recommend a few. Thanks!

Thanks for your input But how does one change the driver [to VESA] without tinkering with the config file, which Handbook: 5.4. Xorg Configuration seems to advise against? Perhaps, dust pull it down from the ports.