Download " antergos-wallpapers-extra " and enjoy community sponsored wallpapers.
Use the "Linux Beginner Search Engine"
So I should just ask at this point. I’ve had a look at the video and I"m curious to understand if there might be additional information that I could use to install as a persistant system on the SSD USB.
So for example, taking from the Arch Wiki, would I need to add or configure on the portable system as desribed here on this link from the Arch Wiki
and as here
Those links above are what I used to guide me and hence the above questions.
Hi all. I’d just like to throw this out there and inquire if anyone may have tried to place a persistant system on a SSD as per the Arch Wiki’s procedure. link text
I’ve done pretty much all they’ve described and I’m having quite some trouble with it.
The main question is if anyone else may have tried it as well and if so, have you been successful with it or have you had issues like I"ve experienced where the Arch/Antergos system with it’s own Grub and all on it’s own independant USB won’t boot via the main laptop’s Grub.
What have your experiences been with this? Success or not?
Piece of cake or a walk through a jungle?
Frustrated and given up?
Honestly, I feel like I want to give up.
By the way, I bought this new Sandisk extreme Pro SSD USB. Would love to use it with Antergos on it, but it ain’t work’in. Maybe a different distro might.
htopmight be able to help you stop the process that’s ‘hard freezing’ your laptop.
can also try
bto forcefully reboot.
Having said that, this combination means that you have to have a QWERTY keyboard.
or can try
Ito send the SIGKILL signal to all processes.
It’s a little bit more aggressive.
sysrqit’s the Print Screen button on your laptop.
can also try Ctrl+Alt+Backspace. This last one may or may not work but if it does to help you in the ‘freezing’ problems, then at least it provides some help.
this is what mine says
# # /etc/pacman.conf # # See the pacman.conf(5) manpage for option and repository directives # # GENERAL OPTIONS # [options] # The following paths are commented out with their default values listed. # If you wish to use different paths, uncomment and update the paths. #RootDir = / #DBPath = /var/lib/pacman/ #CacheDir = /var/cache/pacman/pkg/ #LogFile = /var/log/pacman.log #GPGDir = /etc/pacman.d/gnupg/ #HookDir = /etc/pacman.d/hooks/ HoldPkg = pacman glibc #XferCommand = /usr/bin/curl -C - -f %u > %o #XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u #CleanMethod = KeepInstalled #UseDelta = 0.7 Architecture = auto # Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup #IgnorePkg = #IgnoreGroup = #NoUpgrade = #NoExtract = # Misc options #UseSyslog #Color #TotalDownload CheckSpace #VerbosePkgLists # By default, pacman accepts packages signed by keys that its local keyring # trusts (see pacman-key and its man page), as well as unsigned packages. SigLevel = Required DatabaseOptional LocalFileSigLevel = Optional #RemoteFileSigLevel = Required # NOTE: You must run `pacman-key --init` before first using pacman; the local # keyring can then be populated with the keys of all official Arch Linux # packagers with `pacman-key --populate archlinux`. # # REPOSITORIES # - can be defined here or included from another file # - pacman will search repositories in the order defined here # - local/custom mirrors can be added here or in separate files # - repositories listed first will take precedence when packages # have identical names, regardless of version number # - URLs will have $repo replaced by the name of the current repo # - URLs will have $arch replaced by the name of the architecture # # Repository entries are of the format: # [repo-name] # Server = ServerName # Include = IncludePath # # The header [repo-name] is crucial - it must be present and # uncommented to enable the repo. # # The testing repositories are disabled by default. To enable, uncomment the # repo name header and Include lines. You can add preferred servers immediately # after the header, and they will be used before the default mirrors. #[antergos-staging] #SigLevel = PackageRequired #Server = http://mirrors.antergos.com/$repo/$arch/ [antergos] SigLevel = PackageRequired Include = /etc/pacman.d/antergos-mirrorlist #[testing] #Include = /etc/pacman.d/mirrorlist [core] Include = /etc/pacman.d/mirrorlist [extra] Include = /etc/pacman.d/mirrorlist #[community-testing] #Include = /etc/pacman.d/mirrorlist [community] Include = /etc/pacman.d/mirrorlist # If you want to run 32 bit applications on your x86_64 system, # enable the multilib repositories as required here. #[multilib-testing] #Include = /etc/pacman.d/mirrorlist [multilib] Include = /etc/pacman.d/mirrorlist # An example of a custom package repository. See the pacman manpage for # tips on creating your own repositories. #[custom] #SigLevel = Optional TrustAll #Server = file:///home/custompkgs
You can try to copy/paste mine and use the
qoption might help to briefly list if the files differ or not.
And then determine if and where.
Or you could use
diff -yfor side to side comparison
Maybe this tells you something.
rfkill listdid when it showed that it was soft blocked and then became unblocked after the second
rfkillcommand was actualized.
There is nothing in the udev rules that is remarkable.
We can skip those.
The only reason why I asked of those is in case you at some point in history had created a udev rule for reasons of your own that was interfering.
So, nothing remarkable there.
Have you tried running
manpages for that to scan for your devices, connect, etc.
One thing that we should go over right about now is that via
bluetoothctlI would strongly encourage you to BLOCK all other bluetooth devices. So for example, suppose you live in an apartment. There are other neighbours nearby with bluetooth devices of their own.
I have found that through my own experiences, other people’s bluetooth devices always seem to interfere. I don’t know why, they just do.
Also, prior to connecting to your own device, remove your own bluetooth device from your system’s bluetooth device history.
Also, this here from your output
Unable to get on D-Bus
this means that another running daemon is using the same bus name.
there for do
ps aux | grep blue
Also something else that comes to mind is, is your bluetooth device is even visible?
Also, I don’t know what your set up is like but if there is a bluetooth. conf file in
can you open it and see what is there?
Does the daemon need root priviliages to be started with or something else?
The D-bus policy only allows for the root to own the service.
Read the wiki on D-bus, please link text
can you try
systemctl status dbus.service
Also, can you check the
/var/log/syslogfor any bluetooth related problems?