I use for **/ **BTRFS !
I don’t find anything similar for btrfs…
back on topic:
the boot stalls here: http://i.imgur.com/FvqTn7T.jpg
then…
another halt here: http://i.imgur.com/V378IE0.jpg
do I need to quit **openS ? ** gettin sick of long long long boots…
> systemd-analyze
Startup finished in 6.926s (kernel) + 29.188s (userspace) = 36.114s
os@linux-x0u1:~> systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @29.133s
└─multi-user.target @29.132s
└─sshd.service @28.968s +162ms
└─network.target @28.954s
└─NetworkManager.service @24.807s +4.146s
└─basic.target @24.763s
└─timers.target @24.761s
└─systemd-tmpfiles-clean.timer @24.761s
└─sysinit.target @24.757s
└─apparmor.service @22.721s +2.035s
└─systemd-tmpfiles-setup.service @22.443s +277ms
└─local-fs.target @22.442s
└─var-lock.mount @22.432s +10ms
└─local-fs-pre.target @22.431s
└─systemd-remount-fs.service @4.812s +17.618s
└─systemd-readahead-replay.service @2.919s +1.826s
tia!
Well, that’s when your / partition is mounted.
another halt here: http://i.imgur.com/V378IE0.jpg
Seems to be related to the b43 wireless driver:
http://forum.manjaro.org/index.php?topic=8394.0
https://bbs.archlinux.org/viewtopic.php?id=170588
http://unix.stackexchange.com/questions/93738/b43-wireless-driver-error
Maybe try to add the boot option “b43.allhwsupport=1” as the message supposedly suggests? (it is cut-off)
You can also specify that in a file in /etc/modprobe.d/ as the 3rd link suggests.
Or try to install the broadcom-wl driver from Packman?
do I need to quit **openS ? ** gettin sick of long long long boots…
long long long boots? That’s ridiculous. My one system needs over 2 mins, and the other one (which I am sitting in front of right now) 1min 643ms… 
On 2014-03-22 23:46, wolfi323 wrote:
> long long long boots? That’s ridiculous. My one system needs over 2
> mins, and the other one (which I am sitting in front of right now) 1min
> 643ms…
Mine takes 3 minutes. When it goes fast.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
On 2014-03-22 23:36, goro goren wrote:
>
> back on topic:
>
>
>
> the boot stalls here: http://i.imgur.com/FvqTn7T.jpg
Apparently it does a filesystem check, then mounts the root filesystem
read/write.
As I don’t use btrfs on any of my system (only some test data
partition, sometimes), I do not know if the filesystem test is done on
all boots normally, or only on some. I do know that some filesystems are
checked always, quickly, and only if some problem is found it stops and
does things to it.
But it seems that it is the mounting step a bit later that is the
hurdle. Well… again, I can not compare myself, but guessing, maybe you
have a lot of snapshots in it, and the kernel has to study them during
the mount process, so that it takes some time thinking about it.
Or maybe it has to re-apply journal changes, cleanups, whatever? Dunno.
> then…
>
> another halt here: http://i.imgur.com/V378IE0.jpg
I don’t know what this one is. Some problem with your CPU cores, it can
not enable them at this point? :-? Something else totally different?
What “cores” is it talking about?
> do I need to quit *openS ? * gettin sick of long long long boots…
Mine is way longer: 3 minutes and more, which is why I hibernate my
system instead of halt and boot.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Hi!
just installed that driver minutes ago! …how to disable/unistall the **b43 **driver to avoid conflicts?
plz: asap
tia!
You cannot uninstall it. It is part of the kernel package.
But, if you install the package “broadcom-wl” from Packman, it will blacklist the b43 driver.
You do need the appropriate broadcom-wl-kmp-xxx package for your kernel as well (this is the actual driver). If you are using kernel-desktop, you need broadcom-wl-kmp-desktop. If you are using kernel-default, you need broadcom-wl-kmp-default.