Arch Linux

john beals

Member

Registered: 2021-02-17

Posts: 6

Waiting for IWD to start... temporarily fixed, but not really

I see the error message a lot, and one post gets me to where I can get graphics going.  But, if someone could point me to the proper fix, that would be great. There are a few out there, and the one I tried so far had no effect.

I think that the bigger lesson here is that linux is now systemd, with everything init is obsolete - except to start systemd.  My thinking is the trick is to become a systemd expert first, w containers being a possible career outcome, then fix IW.

Thanks

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,346

Re: Waiting for IWD to start... temporarily fixed, but not really

Not sure if you want to rant or are actually asking a question, if you are actually asking a question, then you need to include details of how you set this up, which service did you enable what's your wifi card, does it eventually continue past the blocker message.

Read https://bbs.archlinux.org/viewtopic.php?id=57855

You might want to post a

sudo journalctl -b

during a session.

Also please post the links to "threads were you see this a lot" and the solutions you claim to have tried and what their effect on the issue were so we can prevent duplications of effort. Have you seen: https://wiki.archlinux.org/index.php/Iw … ter_reboot

john beals

Member

Registered: 2021-02-17

Posts: 6

Re: Waiting for IWD to start... temporarily fixed, but not really

#oddlysatisfying

I tarred the /etc/systemd directory on the install and over-wrote /mnt/etc/systemd and it works
- other than that I did he obvious which is to restart IW in /root/.profile

(Making me wonder if just tarring the entire install in and out to /mnt .. I have a pile of disks like everybody else, so I am going to try this! Blew my mind that tar is even included.  Maybe it should be removed.)

Ok, now on to updating! (hope it isn't TOO mangled)

Update: all is good, xorg installed, but it needed xinit, TWM, xterm, and a few other things - so just keep xinit'n until it runs.  Need to find a little time to see if I can clone the install f/s.  If so, that is what I have been wanting since, hmm, mid-90s.

Postmortem: The main issue with my tarring the systemd etc was that it preserved the the root autologin (which I liked for the install period), but had a bad effect on the dbus.  (I changed that in getty@tty1.service.d/autologin.conf .)  The dbus problem is that it only seems to create the socket and set the env variables for a true login, not an 'su -' login.  But, if I logged in as root, and used the root env variables for my user (to run a browser), I got permission denied for the socket.  If I logged in as a user, then root didn't get dbus access because it uses a different socket number.  So, if I logged in through telnet (whitelisted to 127.0..), maybe be that would give me the full dbus login benefits for any user.

I also had trouble with audio, and there is long thread describing the same situation that happens to also be with an i7.   (The i7 is probably old like mine as the user didn't have any details about it).  Audio was never necessary for this, but I just gave in and installed XFCE.  All is good including wifi.  I got a thrill from TWM being it is so old - I wonder if Tom is even still with us.

So, I am on to the next spare disk to see if I can just tar in the whole file system (and the boot f/s) from the install USB.  Thanks for reading this!

Last edited by john beals (2021-02-19 12:02:06)