Why it's so complicated

USB stick still empty?
Thats strange. The output of the command looks like it worked.

Code:
  Mounts the USB device. I guessed it was at da0s1. You might have others disks!
# mount -t msdosfs /dev/da0s1 /mnt

  Copy the log file into the mounted directory
# cp /var/log/Xorg.0.log /mnt

  Unmount it again ready to unplug safely
# umount /mnt

You might want to consider before unmounting it, to check the contents of the USB stick with ls.

Code:
# ls /mnt

Though, possibly if you are not familiar enough with FreeBSD (yet!) to get a log off it, you might want to focus on learning this a little more first before jumping to graphics. Perhaps just the basics of how to mount a USB stick and using tools like mv, cp, ls, cat to move, copy, list directories and output files respectively will be enough!
Even though it may not be quite as visually stimulating as X11, take your time with this and enjoy the process. This is the whole point of using FreeBSD and learning UNIX after all.

Unless you can think of another way to get that info to us? Video perhaps of # cat /var/log/Xorg.0.log | less and gradually scrolling down to the bottom.
 
This should make sure that all pending write actions are completed.
Worth a try. Though I believe that is only if you are doing raw operations (i.e dd). When you unmount the device it should do all of that for you.

That said, I am a little concerned that the OP didn't see the files after. I have only seen this one because it was a corrupted partition table which Windows read one thing and Linux read another.
 
Hi there noob noob,
I am someone who has used FreeBSD off and on over the years and I am currently evaluating using it on my daily driver with R13. I am currently using EndeavourOS and have installed vanilla Arch ( archlinux.org) a few times. Having followed the Arch Install Guide and a few different YouTube tutorials, you have to remember that a content provider who deviates from the official way of installing whatever distro or BSD is potentially inviting some issues into your install. If they miss a step in their production, it WILL result in an issue. Also their “guide” works on their machine for their use case. Just bear this in mind and take those videos as “study” and at least have the official guide handy. My particular method involves a test laptop with a working installation to bring the webpage or document up while installing the new machine. This works for me, but normally I am putting the “new” install on metal and not a VM. Not definitive as an answer, but it is my method.

I hope that as I evaluate FreeBSD 13 for my daily driver, I continue to increase my knowledge and actually will be posting my own question about some quirks of my machine and particular use case. I do want to close by stating: 1) the Handbook is one of the best written documents there is on a *NIX-like OS and actually some stuff on Arch wiki does apply, just beware that you research package names as on *BSD they can differ from Arch and often do from one Linux distro to another and finally this community is very helpful in my experience, but please remember to try to find the answer in the handbook and if still having an issue, do ask.
 
just the basics of how to mount a USB stick and using tools like mv, cp, ls, cat to move, copy, list directories and output files respectively will be enough!
That's what I'm going to do with time for now I need to use the system as my daily driver to get things done and learn about it as well with time
 
corrupted partition table
Witch one?
My motherboard: Asrock z370 gaming k6 I have 2 disks (NVMe 512 for Windows / HDD 1T for FreeBSD >>before it was Fedora on it)
I guess I see ones when I start FreeBSD when these texts load so fast i try to focus i guess i read partition table corrupted
 
Hi there noob noob,
I am someone who has used FreeBSD off and on over the years and I am currently evaluating using it on my daily driver with R13. I am currently using EndeavourOS and have installed vanilla Arch ( archlinux.org) a few times. Having followed the Arch Install Guide and a few different YouTube tutorials, you have to remember that a content provider who deviates from the official way of installing whatever distro or BSD is potentially inviting some issues into your install. If they miss a step in their production, it WILL result in an issue. Also their “guide” works on their machine for their use case. Just bear this in mind and take those videos as “study” and at least have the official guide handy. My particular method involves a test laptop with a working installation to bring the webpage or document up while installing the new machine. This works for me, but normally I am putting the “new” install on metal and not a VM. Not definitive as an answer, but it is my method.

I hope that as I evaluate FreeBSD 13 for my daily driver, I continue to increase my knowledge and actually will be posting my own question about some quirks of my machine and particular use case. I do want to close by stating: 1) the Handbook is one of the best written documents there is on a *NIX-like OS and actually some stuff on Arch wiki does apply, just beware that you research package names as on *BSD they can differ from Arch and often do from one Linux distro to another and finally this community is very helpful in my experience, but please remember to try to find the answer in the handbook and if still having an issue, do ask.
Thank you for your reply and i will try to become familiar with Handbook i really try to do my best in English and when i open the Handbook I'm not familiar yet with all those technical stuff that's why i like to ask so much, i try vanilla Arch just follow a video tutorial but i can't install it from or using the wiki because i still don't reach that level yet, chrbr comment above thanks to him for his reply for additional option i open that page sync(8) i read but i didn't understand i will try to search later to understand and i just feel embarrassed to tell him or ask for easy explanation
 
Dear Noob Noob,
there is no reason not to ask about sync(8). Nobody can know that by nature. sync just asks the operating system to finish all write activities. The purpose is to have everything settled before an unmount, shutdown or so.

About the login screen I think you are more far than you are aware of. It is just the password which is missing or wrong. You can fix that from single user mode. In the boot menue you can boot into single user mode. Then you end up in a console (no gui) with root access. The disks are ready only in that situation. You can re-mount then to read-write access. The procedure depends on the file system. UFS and ZFS are different. This has been asked regulary. I do not have the commands in mind. From that point you can use password(1) to set or change your password.

As far as I remember exit exits the single user mode is left and the system boots normally. Have you ever booted to the console without login manager? Usually it is better to setup the booting to the console first to be sure that the basic stuff is working. If so you can configure X11 with a simple window manager as twm. Finally you can setup a login manager.

The single user mode sounds scary, but there is nothing you can not manage.
 
Dear Noob Noob,
there is no reason not to ask about sync(8). Nobody can know that by nature. sync just asks the operating system to finish all write activities. The purpose is to have everything settled before an unmount, shutdown or so.

About the login screen I think you are more far than you are aware of. It is just the password which is missing or wrong. You can fix that from single user mode. In the boot menue you can boot into single user mode. Then you end up in a console (no gui) with root access. The disks are ready only in that situation. You can re-mount then to read-write access. The procedure depends on the file system. UFS and ZFS are different. This has been asked regulary. I do not have the commands in mind. From that point you can use password(1) to set or change your password.

As far as I remember exit exits the single user mode is left and the system boots normally. Have you ever booted to the console without login manager? Usually it is better to setup the booting to the console first to be sure that the basic stuff is working. If so you can configure X11 with a simple window manager as twm. Finally you can setup a login manager.

The single user mode sounds scary, but there is nothing you can not manage.
Thank you so much i really appreciate it ?
 
OK.. on fresh new FreeBSD installs, SSH is usually enabled by default. It is one of the last things the installer asks about (See the Handbook chapter on installation, it does have good screenshots). Once you boot into your fresh installation, and log in as regular user, then you can run ifconfig and get your system's IP address that way. With that in hand, you can ssh in from elsewhere.
 
get some sleep and then follow the handbook. This is not linux or windows. try ask direct questions and we will help you. I hope you succeed tomorrow after getting enough sleep and then when you stumble upon an issue try searching the forums and the handbook and If nothing helps don't hesitate to ask here we are more than happy to help you.
good night
amr
 
OK.. on fresh new FreeBSD installs, SSH is usually enabled by default. It is one of the last things the installer asks about (See the Handbook chapter on installation, it does have good screenshots). Once you boot into your fresh installation, and log in as regular user, then you can run ifconfig and get your system's IP address that way. With that in hand, you can ssh in from elsewhere.
Thank you actuality was password wrong(not my fault ?) in the console I was typing my password correctly as I set it SDDM was English by default I didn't know that and, I'm using AZERTY keyboard I try and it worked I logged in but I have resolution issue no 1920x1080 and refresh rate 0 HZ
https://ibb.co/gDK6Px2
https://ibb.co/rG47WW1
 
I guess I see ones when I start FreeBSD when these texts load so fast i try to focus i guess i read partition table corrupted
Don't worry about this. I am sure you are fine. I was mostly thinking (typing?) aloud and my experience of seeing files differently on a usb stick per platform. I am fairly sure everything is fine and at worst, your USB stick might be a little weirdly formatted.

Keep going! Great to see you have something graphical going :)
 
Don't worry about this. I am sure you are fine. I was mostly thinking (typing?) aloud and my experience of seeing files differently on a usb stick per platform. I am fairly sure everything is fine and at worst, your USB stick might be a little weirdly formatted.

Keep going! Great to see you have something graphical going :)
Thank you really for your time and reply i appreciate it really I do all of you God bless you
 
Back
Top