Latest SD image from tangentsoft.com

564 views
Skip to first unread message

James Zeun

unread,
Feb 12, 2018, 12:52:31 PM2/12/18
to PiDP-8
Hi guys

Been happily using my PiDP8i as a fileserver at home until the SD card failed on me over Christmas. I'm trying to set everything back up and hit a bit of a snag. i downloaded the lasted image from tangentsoft but the user name and password its given in the archive doesn't work. I've tried several times but it wont accept what is in the readme file, am i missing something? Was it changed and the text file not updated?

Many thanks

Warren Young

unread,
Feb 12, 2018, 1:39:59 PM2/12/18
to PiDP-8
On Monday, February 12, 2018 at 10:52:31 AM UTC-7, James Zeun wrote:

I've tried several times but it wont accept what is in the readme file, am i missing something? Was it changed and the text file not updated?

That user name and password are changed from their Raspbian defaults by a script, and the change still exists in that script.

On top of that, step 7 in the release process is to boot the re-written SD card, log in, and make sure everything is running, which means I need to type the user name and password correctly to get in.

It's a long password. Case matters. Are you certain you're typing it correctly? The nonstandard lowercase initial 'e' and the uppercase 'd' in "de" may be throwing you.

James Zeun

unread,
Feb 13, 2018, 8:34:50 AM2/13/18
to PiDP-8
Hi Warren

Thanks for the reply

I read through the readme you included in the zip and was using the correct user name and password. After i posted here, i reflashed the image to SD and it seems to have worked, password and all :-)

However I have hit another snag, the PiDP8 does not appear to boot correctly if a USB flash drive is present. Is that expected behaviour?

James

Warren Young

unread,
Feb 13, 2018, 6:45:40 PM2/13/18
to PiDP-8
On Tuesday, February 13, 2018 at 6:34:50 AM UTC-7, James Zeun wrote:

the PiDP8 does not appear to boot correctly if a USB flash drive is present. Is that expected behaviour?

That depends on exactly what "correctly" means here. It might be correct but unexpected-to-you, or it might be incorrect. I need details.

Some possibilities:

  • You have DF != 0 at boot time so it's trying to attach a file on the flash drive to the simulator as a device medium image, throwing it off. Run pidp8i to attach to the screen(1) instance to see what it's saying. 
  • Raspbian itself is doing something with the disk image; hook up an HDMI monitor to define "something."
  • The device has problems and is dragging the USB bus down, preventing even the OS from starting, or rebooting it before the PiDP-8/I software can start. (Doubters: I saw this on two separate machines a couple of weeks ago with a single bad USB drive; the PCs in question weren't even running the same operating system! USB can be a PITA.)
I doubt that list is comprehensive, but that's as far as nearly-unfounded speculation takes me today.

James Zeun

unread,
Feb 13, 2018, 7:33:50 PM2/13/18
to PiDP-8
Hi Warren

I'm running it headless (connecting via ssh over my network), so I'm unable to log in and see what is happening when it hangs.

If I hook power in to the pi with only the wifi dongle connected, all is well. But as soon as I connect a USB pen drive it won't boot. I thought I'd ask as I know you mention on your site about keeping the system locked down for security, something I wholeheartedly agree on :-) I just wasn't sure if this was a facet of your security measures :-)

For the past year I've been using my PiDP8 as a server, with two 64gb san disk flash drives. All was going well until the SD card died a death. So my plan now is to boot off SD but have the system on flash drive. I understand they can be a little more durable in the long term.

I'm using your multi

James Zeun

unread,
Feb 13, 2018, 7:39:02 PM2/13/18
to PiDP-8
To clarify, by 'correctly' I mean the front panel lights up and I'm able to manipulate the switches and interact with the PDP8. When a USB drive is connect this does not occur. I did wonder if simh might be searching the USB for a mountable disk image, but I do not have any switches set, so I wouldn't think it would be looking.
Message has been deleted

James Zeun

unread,
Feb 14, 2018, 5:46:02 AM2/14/18
to PiDP-8

Alright, let me see if i can explain this odd behaviour adequately

This morning I've established the Pi boots fine with my wifi dongle inserted

But the Pi does not boot correctly when a USB flash drive is inserted. By correctly, I mean reach the command prompt, allowing me to login. Things appear to become derailed when it reaches the following point in the boot sequence

[ ok ] Created slice system-usb\x2mount.slice
[ ok ] Reached Target Encrypted Volumes
(1 of 3) A start job is running for.......

The text is truncated so I'm unable to see what it says exactly, but i believe the three devices are tyAMA01, x2d01 and serieal1  It will proceed to think on this for approximately 30 seconds before moving on. Then when it reaches the following, i am unable to use the system. 

[ ok ] Started Load/Save RF Kill Switch Status.
You are in emergency mode. After Logging in, type 2journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try again to into default mode.

At this point I am left with a blinking cursor and I am unable to input any commands to the terminal.

If you like Warren I would be happy to email you a copy of the syslog if that would help, at this point I'm a little lost as to what is happening.


 




On Wednesday, 14 February 2018 09:14:56 UTC, James Zeun wrote:
Hooked the system up to the TV this morning and I'm getting this. Also unable to log in, refuses to accept my user name & password.

Warren Young

unread,
Feb 14, 2018, 6:59:57 AM2/14/18
to PiDP-8
On Wednesday, February 14, 2018 at 3:46:02 AM UTC-7, James Zeun wrote:
> [ ok ] Started Load/Save RF Kill Switch Status.
> You are in emergency mode. After Logging in, type 2journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try again to into default mode.

So what does “journalctl -xb” say?

> At this point I am left with a blinking cursor and I am unable to input any commands to the terminal.

Are you certain it isn’t showing a login prompt just off the bottom edge of the screen? Try hitting Enter several times. If the screen scrolls up, it isn’t actually stuck.

You may need a root login password to get in at this point. I have little experience with Debian type OSes in rescue mode, so I’m just applying my primarily-CentOS experience here, which may not apply.

If by chance my CentOS experience does apply here, you’d boot the system without the USB drive attached, get to a prompt, then say “sudo passwd root”, then give the root user a password. By default, root is locked out on Debian type OSes, requiring that you sudo up from one of the authorized normal users, but I think you need to be really-root in order to log into the rescue mode.

> If you like Warren I would be happy to email you a copy of the syslog if that would help, at this point I'm a little lost as to what is happening.

I think you’ve got a Raspbian Stretch problem here, not a PiDP-8/I problem. I can try to help with that, but there are much better resources. I’d suggest the Raspberry Pi Stack Exchange (https://raspberrypi.stackexchange.com) except that they require that you ask an objectively-answerable question with at least one definite right answer, and your problem definition still seems too vague to me to qualify. But maybe I am wrong, and this is a well-known problem and you’ll get a quick answer rather than a quick rejection there.

James Zeun

unread,
Feb 14, 2018, 7:09:58 AM2/14/18
to pid...@googlegroups.com
Hi Warren

I reflashed your SD multi core image back to memory card just in case I had messed something up, I'm now back to being unable to login. The pi refuses to accept the user name and password you provided with the image. A little way up the screen from the login prompt it says:

[ FAILED ] Failed to start Session c1 of user pidp8i


BTW you wouldn't happen to have a copy of the previous PiDP8 image SD install? Just so I could test to see if that would work? I dont recall which version i downloaded but it would have been late 2016 or early 2017. I was running that for months without a hitch until the sd card died.

Many thanks!

Warren Young

unread,
Feb 14, 2018, 7:31:24 AM2/14/18
to PiDP-8
On Wednesday, February 14, 2018 at 5:09:58 AM UTC-7, James Zeun wrote:
>
> I reflashed your SD multi core image back to memory card just in case I had messed something up, I'm now back to being unable to login.

You claim to have done the same thing twice in a row (reflash the SD card) and you get different results. That means you either did not do the same thing twice in a row or there is something nondeterministic in the system. Here, I think that may be hardware.

To rule it out, try this:

1. Reformat the SD card in your PC using the SD Association’s formatting tool: https://www.sdcard.org/downloads/formatter_4/

2. Flash regular Raspbian Desktop onto the card. Convince yourself that it works. If you still get the same screens as before, either you aren’t booting from the source you think you are, or your system can’t boot *anything* properly at this point.

3. Reflash the card with the PiDP-8/I image. Does it clearly change behavior?

James Zeun

unread,
Feb 14, 2018, 7:43:33 AM2/14/18
to PiDP-8


I'm using etcher on linux to write the sd image 

Yes i've reflashed the SD card two or three times, the reason i did this was because..

First time around, i edited the DHCP and WPA files to lock down a static IP and enable WIFI to connect to the local network
Second time, in the event editing the above files was causing some sort of conflict (i couldn't see why but trying to eliminate possibilities)
Third (final time) just in case the SD card is some how faulty, however I am wondering if etcher is the cause of this.

I'm going to do exactly as you said, i already downloaded the lite version of stretch from the foundation website. I've never had this sort of odd behaviour happen before.

Thanks again for sparing me the time, hopefully i can report back with better news!

James Zeun

unread,
Feb 14, 2018, 9:15:50 AM2/14/18
to pid...@googlegroups.com

Time to report back. I've formatted the SD card in windows with SD formatter, then used win32disk to write the pidp8 image. 

So i'm using a different system to write the card, the only thing that is the same is the memory card.

Inserted the sd in to the pi and on booting up the screen momentary flashed up with a blue border, grey square in the centre, like the screen you get when entering raspi-config. However it soon disappeared, pushed up as the screen scrolled with text. 

Once again it reported

[ FAILED ] Failed to start Session c1 of user pidp8i

I'm now burning a copy of stretch lite from the foundation website, so will see how that works out. 


Just to clarify, i'm using a RPI2 model B and have not made the serial mod, so i connect to my pidp8 over the LAN.

***UPDATE***

Burnt a copy of stretch lite to sd and the pi is working fine, i have all the ports filled with usb pen drives and it is currently sat doing an update. I think we can say with a some degree of certainty that my sd card is not faulty, nor is my Pi (thank goodness). I had begun to wonder if etcher was at fault, but this would appear to indicate that it is not.

Warren could the image you have on your website be faulty? Something as silly as a CRC error? 

I'd very much like to use one of your images, as they work wonderfully in the Pidp8 :-)

Warren Young

unread,
Feb 14, 2018, 10:22:46 AM2/14/18
to PiDP-8
On Wednesday, February 14, 2018 at 7:15:50 AM UTC-7, James Zeun wrote:
>
> Inserted the sd in to the pi and on booting up the screen momentary flashed up with a blue border, grey square in the centre, like the screen you get when entering raspi-config.

It’s expanding itself into the space available on the card, then rebooting.

The disk images as-shipped are shrunk to a near-minimal size, giving little room for user files, to make the download size as small as possible.

This is one of the features added in the current release. In prior releases, you had to go into raspi-config and manually request expansion.

> Once again it reported
>
>
> [ FAILED ] Failed to start Session c1 of user pidp8i

I’ve tried Googling that, and it’s a very rare error, with no useful replies that I could find. If you could get logged in, you could run the command it suggests to get more information, but since you can’t...

> Burnt a copy of stretch lite to sd and the pi is working fine

All right. Maybe try the single-core image next? If that also works, then maybe there’s some issue with the fact that I build the multi-core image on a Pi 3 which makes it incompatible with your Pi 2.

The single-core images are built on a Pi B+, so if that guess is right, it might be upward compatible with your Pi 2.

Or, give up on my disk images, and build from source. That’s what I’d do. :)

> Warren could the image you have on your website be faulty? Something as silly as a CRC error?

As I said, the disk images are re-tested before being released.

If you doubt the download’s integrity, the manifest file that comes with it has hashes you can check.

> I'd very much like to use one of your images, as they work wonderfully in the Pidp8 :-)

Evidently not. :)

James Zeun

unread,
Feb 14, 2018, 11:28:28 AM2/14/18
to PiDP-8
I'm just going out, but when I return, I will burn off a copy of the single core.

Will I still be able to adapted the install to take advantage of the iridescent bulb effect which is on the multicore?

Thanks for you help Warren! :-) it might be annoying that is doesn't work, but that's all part of the joys of computing. If I wanted an easy ride, I buy a fruit branded product and hand in my toolbox ;-)

Warren Young

unread,
Feb 14, 2018, 1:24:15 PM2/14/18
to PiDP-8
On Wednesday, February 14, 2018 at 9:28:28 AM UTC-7, James Zeun wrote:

Will I still be able to adapted the install to take advantage of the iridescent bulb effect


Sure, just re-configure it. See README.md.

James Zeun

unread,
Feb 15, 2018, 7:09:53 AM2/15/18
to pid...@googlegroups.com
Morning all

Sat in front of the pidp8 with a cup of coffee and the single core image wrote to SD. After booting up, I'm sorry to report it behaves exactly the same as the multi core image, with the exception of LED behaviour being more jerky and less bulb like.

They say a picture says a thousand words, so I took the liberty of creating a short clip to demonstrate what I am experiencing. 
I can only hope it will be insightful in some way :-)

As I suspect you might be connecting to your system via serial Warren, I wondered if my using the Pi directly with a keyboard might be the problem (grasping as straws now) I disconnected the hdmi cable, keyboard and wifi adapter, but as I dont have a serial connection on my PiDP8, I connected my laptop up directly with a cat5 cable going in the pi's lan port.

Sadly this didn't work, the pi wont recognise the pidp8i username or password, so i'm unable to log in and access the system. However the simh simulator seems to be working, as i demonstrated in the video.

Any thoughts? At this point I'm wondering if I shouldn't just install stretch lite and install the software that way. Obviously this wont solve the issue with the image and whether what is happening to me, will effect others who download it.

****UPDATE******

After posting the above, I remembered having my Pi Zero upstairs, I'm currently building a Pi Megadrive so I had it out for testing. I booted up the single core pidp8 image and the zero behaved exactly as the Pi2 had done, ending with the 'Failed to start Session C1 of user pidp8i'

I think it is fair to say now that I can eliminate my hardware from being the problem, as I have
A. Tried three separate images of which only the foundations stretch lite image work as expected, letting me log in.
B, Tried different setups e.g headless pi, SSH over wifi and finally direct ethernet connection
C. Tried running same SD on different Pi boards

The only thing I can suggest now, is if someone else where to download the image and see if they encounter the same issue *shrug*

Warren Young

unread,
Feb 15, 2018, 9:01:26 AM2/15/18
to PiDP-8
On Thursday, February 15, 2018 at 5:09:53 AM UTC-7, James Zeun wrote:

As I suspect you might be connecting to your system via serial Warren, I wondered if my using the Pi directly with a keyboard might be the problem

Nope. The images are tested on bare Pi boards with an HDMI monitor and USB keyboard attached. If there is any discrepancy between image building process and what normal users see, it's that I don't use my actual PiDP-8/I hardware to build and test these images. I only have the one, and it's a clumsy physical design for building images anyway -- I need easy access to the SD card slot -- so I have separate "build" Pis for that.
 
Here's a wild idea: type the password at the user name prompt instead, so you can see what characters the Pi *thinks* it is getting. Maybe there's some incompatibliity between the keyboard and the Pi configuration causing...oh, I don't know...case smashing, 1s to be treated as lowercase Ls...random character dropouts...

At this point I'm wondering if I shouldn't just install stretch lite and install the software that way.

Frankly, I wish everyone would do it that way. Then I wouldn't need to produce binary OS images at all. :)

The only thing I can suggest now, is if someone else where to download the image and see if they encounter the same issue *shrug*

I thought you were going to check the SHA-256 hashes on your downloads as well. 

James Zeun

unread,
Feb 15, 2018, 10:11:00 AM2/15/18
to PiDP-8
Hi Warren

They say great minds think alike, yes I had the same thought and typed the password out in "enter username" part and it works. Granted my keyboard is a little sticky some times, but it most certainly is typing out the characters properly. I can't help wonder if the that c1 error is not some how linked? I've looked online but found very little on the subject and nothing relating to the raspberry pi specifically. Here is my wild idea, because I certainly dont have anything concrete to go on. I suspect that error is some how interrupting the link between bash and the user accounts, so when the pi boots up, it acts as if there aren't any user accounts attached to the system. As I said, this branches far from my usual area of experience, so at this point its just my best guess, nothing more. I spent much of this morning trying out combinations, such as username = root in combination with the default password you set. Generally the root account is disabled, but i was getting desperate and was sort of hoping the system might let me in :-)

I've just checked the hash and it checks out fine, it matches what is in the manifest file.

After discovering using Zero made no difference, I've since burnt a copy of the Foundations lite sd image. At present I'm on your site following the instructions on installing and setting up the emulator. :-)

Once I have the system up and running I would be more then happy to make a backup for anyone who might like it. Though I'm still curious as to why one earth something that you clearly had working at your end, is going so pear shaped over here. Last night when you mentioned using a Pi3, I honestly thought we might have cracked it.

Chris Smith

unread,
Feb 16, 2018, 12:19:20 AM2/16/18
to PiDP-8

Just because it's another pair of eyes, I went back through the posts here.

James .. is it really the case that only stretch lite ran successfully on the SD card? And - is this the same SD card that failed much earlier?

If so, I would note that the entirety of all the files on a image are not necessary to the correct running of any system - not just Linux, but almost any complex OS. A successful install and run of a single distro is not a guarantee that the card is free of defects. And ... having a USB stick inserted would almost certainly exercise parts of files that are otherwise not involved at all.

Consider the possibility that the SD card has a permanent, but small, failed region. And only on stretch lite does this area get missed by critical files. Ultimately, it might be necessary to try a new SD card. (Perhaps you have? I didn't think I saw a definitive statement to that effect in the chain.)

Secondly - you have mentioned several time the patterns of PiDP8 lights ... does this mean that every single test has been run with the front panel attached? If so .. try booting without the front panel. The Pi should still start and run just fine. I only mention this because the front panel is also hardware, and it does put signals on the pins. Moreover, because everyone's hand assembly will be slightly different, there is the possibility that your front panel has a unique glitch not shared by any other front panel. (Perhaps you have tried this - I just did not see any explicit mention of this one way or the other.)

It's still an excellent learning experience watching this dialogue on failure analysis.

... Chris

James Zeun

unread,
Feb 16, 2018, 7:45:42 AM2/16/18
to PiDP-8
Morning Chris

Thanks for your comments and also kind words, I'd like to think that while my PDP knowledge is lackluster, I do have a reasonable understanding of Linux, I've used it for 8-9 years now and force myself to use the console where ever possible. I'm by no means an expert, but hopefully not a novice either (i hope). I'll try to answer your questions, best I can.

The SD card that failed has gone in the bin, it write protected itself and wouldn't let me delete or format. After doing some reading, I discovered that when an SD card is near death it will write protect, allowing you to get your files off before it completely goes down the pan. The card I'm using now is brand new, so I would surprised if it has any bad blocks...yet :P

I should mention that at one point I did configure the Pi to boot from a spare 16gb flash drive and it still acted in the same manner as if it had booted from SD. Eventually I want to configure the PiDP8 to run off USB. From what I've read it is more reliable and less susceptible to failure then an SD card. I can always run off a copy of the PiDP8 image to another card, just to be certain.

The PiDP8 sits on a shelf in my room and is active 24/7, I use as my own personal Google drive or PiDP8 Drive, with 2x64gb USB San Flash drives connected. I run software from it remotely, IRC, Wordgrinder to name a couple of applications. Like Warren, security is never far from my thoughts, especially as I have port forwarding enabled, allowing me to SSH in to the Pi remotely. Fail2ban takes care of the unwanted port sniffers and bans them accordingly. Gives me a buzz to use the Pi in way not too dissimilar to how the PDP8 was used remotely back in the 70s with teletype. Except I'm using a laptop and Cool-retro-term :-P

As Warren mentioned earlier, just removing the SD card from the PiDP8 can be a faff, so actually removing the board would be even more bother. Besides I think we've established the board isn't the problem, as the zero acted in the same way and was never connected to the front panel at any point.

I have a spare Pi2 so I might have a go at writing the image to another card. Different Pi, different card, see whats the results are.

I'll wrap up the message by saying, that as of now. My PiDP8 is working fine, I followed the instructions on Warrens site and everything seems to be alright. Its sitting on the coffee table beside me, blinking away :-D

James Zeun

unread,
Feb 17, 2018, 11:47:14 AM2/17/18
to PiDP-8
I got back on with restoring my pidp8 / file server today and noticed that since installing the simH emulator the C1 error has returned. Only difference is that I can still log in to the system. The error wasn't there before I install simh, as per the instructions on the site.

Warren Young

unread,
Feb 17, 2018, 9:06:20 PM2/17/18
to PiDP-8
On Thursday, February 15, 2018 at 8:11:00 AM UTC-7, James Zeun wrote:

I...typed the password out in "enter username" part and it works.

My next guess is transcription error. "Edson" is a strange name; are you typing "esdon" instead, maybe?

Because of all this doubt thrown on the images as-built, I reflashed my own test SD card here with images unpacked from the directory published to the tangentsoft.com web server, and they boot up without error and the password given in doc/OS-images.md works.

I can't help wonder if the that c1 error is not some how linked?

Given your later report about it reappearing under stock Raspbian and the fact that so few Google results come up for it, I'm guessing, "No."

But now that you've got a working OS, you could post the output of the systemctl command it prompts you to enter to get more details.

I'm guessing it has something to do with an interaction between systemd and the pidp8i service script's "su" command. We really should just switch to proper systemd and a user-level service here.

James Zeun

unread,
Feb 20, 2018, 7:00:57 AM2/20/18
to PiDP-8
Hi Warren

Sorry I've not replied sooner

I've been wrestling with the RPi2 (PiDP8), trying to get it to boot from SD and then over to USB flash drive. Needless to say i've been finding it unnecessarily difficult to achieve. When I thought all was sorted, the usb pen went and died, ugh I think I'm jinxed lol

After reading your message I thought it best to check if my 8gb sd card was causing all the problem, so I've burnt the multicore sd image to a fresh 16gb card. I'm sorry to report the Rpi2 didn't boot properly, it times out waiting on the serial, dev-serial1.device & dev-ttyAMA0.device and then it then appears to fail to mount the boot partition. 

[ depend ] dependency failed for /boot
[ depend ] dependency failed for Local File Systems
[ depend ] dependency failed for File System Check on /dev/disk/by-partuuid/0de7b4f8-01

Because it fails to mount boot, i'm left with a blinking cursor and no login prompt, I'm guessing because there is no operating system loaded for me to do anything with.

I can try using the single core image and see if i get a different result. 

James Zeun

unread,
Feb 20, 2018, 11:59:28 AM2/20/18
to pid...@googlegroups.com
So after my last message, I began rebuilding the system using a copy of raspbian lite. All was working fine until I install the pidp8i software and all of a sudden, I'm back in to emergency mode. 

With the great respect to Warren (I think your doing a great job supporting the PiDP8) I think there is clearly something not quite right with how this emulator installs on the latest version of Raspbian, somewhere along the lines its messing up. I'm afraid it will take someone more savvy with linux then I to figure out what that is. 

As it stands I can ssh in to the system and i get no errors, everything seems perfectly fine while running headless, the error appears only when booting up with hdmi hooked up. 

At present i'm running this on a spare Raspberry Pi2 Model B version 1.1, 8GB SD + San Disk Cruzer 16GB flash drive.
The RPi has been configured to boot initially from SD and then swap over to USB. I've not yet hooked the sd card and flash drive up to the actual PiDP8, fingers are firmly crossed that the front panel will light up once I do.

Thanks to everyone who has tried to help, I really do appreciate how hard it is to fault find when your not in front of the offending system. I'm both happy and confused why everything worked for you Warren. Perhaps you can illuminate on what your using to burn the image, what sort of RPI your testing it on. I'll try to replicate it at my end if i can. 

As per your request, below is a copy of my jounalctrl output.

-- Logs begin at Tue 2018-02-20 16:48:59 UTC, end at Tue 2018-02-20 16:51:14 UTC. --
Feb 20 16:48:59 raspberrypi kernel: Booting Linux on physical CPU 0xf00
Feb 20 16:48:59 raspberrypi kernel: Linux version 4.9.59-v7+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611) ) #1047 SMP Sun Oct 29 12:19:23 GMT 2017
Feb 20 16:48:59 raspberrypi kernel: CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
Feb 20 16:48:59 raspberrypi kernel: CPU: div instructions available: patching division code
Feb 20 16:48:59 raspberrypi kernel: CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
Feb 20 16:48:59 raspberrypi kernel: OF: fdt:Machine model: Raspberry Pi 2 Model B Rev 1.1
Feb 20 16:48:59 raspberrypi kernel: cma: Reserved 8 MiB at 0x3ac00000
Feb 20 16:48:59 raspberrypi kernel: Memory policy: Data cache writealloc
Feb 20 16:48:59 raspberrypi kernel: On node 0 totalpages: 242688
Feb 20 16:48:59 raspberrypi kernel: free_area_init_node: node 0, pgdat 80c6f380, node_mem_map ba3a1000
Feb 20 16:48:59 raspberrypi kernel:   Normal zone: 2133 pages used for memmap
Feb 20 16:48:59 raspberrypi kernel:   Normal zone: 0 pages reserved
Feb 20 16:48:59 raspberrypi kernel:   Normal zone: 242688 pages, LIFO batch:31
Feb 20 16:48:59 raspberrypi kernel: percpu: Embedded 14 pages/cpu @ba35c000 s25600 r8192 d23552 u57344
Feb 20 16:48:59 raspberrypi kernel: pcpu-alloc: s25600 r8192 d23552 u57344 alloc=14*4096
Feb 20 16:48:59 raspberrypi kernel: pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
Feb 20 16:48:59 raspberrypi kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 240555
Feb 20 16:48:59 raspberrypi kernel: Kernel command line: bcm2708_fb.fbwidth=1280 bcm2708_fb.fbheight=1024 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000  dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=PARTUUID=37665771-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
Feb 20 16:48:59 raspberrypi kernel: PID hash table entries: 4096 (order: 2, 16384 bytes)
Feb 20 16:48:59 raspberrypi kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Feb 20 16:48:59 raspberrypi kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Feb 20 16:48:59 raspberrypi kernel: Memory: 940368K/970752K available (7168K kernel code, 486K rwdata, 2012K rodata, 1024K init, 770K bss, 22192K reserved, 8192K cma-reserved)
Feb 20 16:48:59 raspberrypi kernel: Virtual kernel memory layout:
                                        vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                                        fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                                        vmalloc : 0xbb800000 - 0xff800000   (1088 MB)
                                        lowmem  : 0x80000000 - 0xbb400000   ( 948 MB)
                                        modules : 0x7f000000 - 0x80000000   (  16 MB)
                                          .text : 0x80008000 - 0x80800000   (8160 kB)
                                          .init : 0x80b00000 - 0x80c00000   (1024 kB)
                                          .data : 0x80c00000 - 0x80c79834   ( 487 kB)
                                           .bss : 0x80c7b000 - 0x80d3b964   ( 771 kB)
Feb 20 16:48:59 raspberrypi kernel: SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Feb 20 16:48:59 raspberrypi kernel: Hierarchical RCU implementation.
Feb 20 16:48:59 raspberrypi kernel:         Build-time adjustment of leaf fanout to 32.
Feb 20 16:48:59 raspberrypi kernel: NR_IRQS:16 nr_irqs:16 16
Feb 20 16:48:59 raspberrypi kernel: arm_arch_timer: Architected cp15 timer(s) running at 19.20MHz (phys).
Feb 20 16:48:59 raspberrypi kernel: clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns
Feb 20 16:48:59 raspberrypi kernel: sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns
Feb 20 16:48:59 raspberrypi kernel: Switching to timer-based delay loop, resolution 52ns
Feb 20 16:48:59 raspberrypi kernel: Console: colour dummy device 80x30
Feb 20 16:48:59 raspberrypi kernel: console [tty1] enabled
Feb 20 16:48:59 raspberrypi kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 38.40 BogoMIPS (lpj=192000)
Feb 20 16:48:59 raspberrypi kernel: pid_max: default: 32768 minimum: 301
Feb 20 16:48:59 raspberrypi kernel: Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
Feb 20 16:48:59 raspberrypi kernel: Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
Feb 20 16:48:59 raspberrypi kernel: Disabling memory control group subsystem
Feb 20 16:48:59 raspberrypi kernel: CPU: Testing write buffer coherency: ok
Feb 20 16:48:59 raspberrypi kernel: ftrace: allocating 22392 entries in 66 pages
Feb 20 16:48:59 raspberrypi kernel: CPU0: update cpu_capacity 1024
Feb 20 16:48:59 raspberrypi kernel: CPU0: thread -1, cpu 0, socket 15, mpidr 80000f00
Feb 20 16:48:59 raspberrypi kernel: Setting up static identity map for 0x100000 - 0x100034
Feb 20 16:48:59 raspberrypi kernel: CPU1: update cpu_capacity 1024
Feb 20 16:48:59 raspberrypi kernel: CPU1: thread -1, cpu 1, socket 15, mpidr 80000f01
Feb 20 16:48:59 raspberrypi kernel: CPU2: update cpu_capacity 1024
Feb 20 16:48:59 raspberrypi kernel: CPU2: thread -1, cpu 2, socket 15, mpidr 80000f02
Feb 20 16:48:59 raspberrypi kernel: CPU3: update cpu_capacity 1024
Feb 20 16:48:59 raspberrypi kernel: CPU3: thread -1, cpu 3, socket 15, mpidr 80000f03
Feb 20 16:48:59 raspberrypi kernel: Brought up 4 CPUs
Feb 20 16:48:59 raspberrypi kernel: SMP: Total of 4 processors activated (153.60 BogoMIPS).
Feb 20 16:48:59 raspberrypi kernel: CPU: All CPU(s) started in HYP mode.
Feb 20 16:48:59 raspberrypi kernel: CPU: Virtualization extensions available.
Feb 20 16:48:59 raspberrypi kernel: devtmpfs: initialized
Feb 20 16:48:59 raspberrypi kernel: VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
Feb 20 16:48:59 raspberrypi kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
Feb 20 16:48:59 raspberrypi kernel: futex hash table entries: 1024 (order: 4, 65536 bytes)
Feb 20 16:48:59 raspberrypi kernel: pinctrl core: initialized pinctrl subsystem
Feb 20 16:48:59 raspberrypi kernel: NET: Registered protocol family 16
Feb 20 16:48:59 raspberrypi kernel: DMA: preallocated 1024 KiB pool for atomic coherent allocations
Feb 20 16:48:59 raspberrypi kernel: hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
Feb 20 16:48:59 raspberrypi kernel: hw-breakpoint: maximum watchpoint size is 8 bytes.
Feb 20 16:48:59 raspberrypi kernel: Serial: AMBA PL011 UART driver
Feb 20 16:48:59 raspberrypi kernel: bcm2835-mbox 3f00b880.mailbox: mailbox enabled
Feb 20 16:48:59 raspberrypi kernel: bcm2835-dma 3f007000.dma: DMA legacy API manager at bb80f000, dmachans=0x1
Feb 20 16:48:59 raspberrypi kernel: SCSI subsystem initialized
Feb 20 16:48:59 raspberrypi kernel: usbcore: registered new interface driver usbfs
Feb 20 16:48:59 raspberrypi kernel: usbcore: registered new interface driver hub
Feb 20 16:48:59 raspberrypi kernel: usbcore: registered new device driver usb
Feb 20 16:48:59 raspberrypi kernel: raspberrypi-firmware soc:firmware: Attached to firmware from 2017-10-24 17:09
Feb 20 16:48:59 raspberrypi kernel: clocksource: Switched to clocksource arch_sys_counter
Feb 20 16:48:59 raspberrypi kernel: VFS: Disk quotas dquot_6.6.0
Feb 20 16:48:59 raspberrypi kernel: VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Feb 20 16:48:59 raspberrypi kernel: FS-Cache: Loaded
Feb 20 16:48:59 raspberrypi kernel: CacheFiles: Loaded
Feb 20 16:48:59 raspberrypi kernel: NET: Registered protocol family 2
Feb 20 16:48:59 raspberrypi kernel: TCP established hash table entries: 8192 (order: 3, 32768 bytes)
Feb 20 16:48:59 raspberrypi kernel: TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
Feb 20 16:48:59 raspberrypi kernel: TCP: Hash tables configured (established 8192 bind 8192)
Feb 20 16:48:59 raspberrypi kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
Feb 20 16:48:59 raspberrypi kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
Feb 20 16:48:59 raspberrypi kernel: NET: Registered protocol family 1
Feb 20 16:48:59 raspberrypi kernel: RPC: Registered named UNIX socket transport module.
Feb 20 16:48:59 raspberrypi kernel: RPC: Registered udp transport module.
Feb 20 16:48:59 raspberrypi kernel: RPC: Registered tcp transport module.
Feb 20 16:48:59 raspberrypi kernel: RPC: Registered tcp NFSv4.1 backchannel transport module.
Feb 20 16:48:59 raspberrypi kernel: hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available
Feb 20 16:48:59 raspberrypi kernel: workingset: timestamp_bits=14 max_order=18 bucket_order=4
Feb 20 16:48:59 raspberrypi kernel: FS-Cache: Netfs 'nfs' registered for caching
Feb 20 16:48:59 raspberrypi kernel: NFS: Registering the id_resolver key type
Feb 20 16:48:59 raspberrypi kernel: Key type id_resolver registered
Feb 20 16:48:59 raspberrypi kernel: Key type id_legacy registered
Feb 20 16:48:59 raspberrypi kernel: Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
Feb 20 16:48:59 raspberrypi kernel: io scheduler noop registered
Feb 20 16:48:59 raspberrypi kernel: io scheduler deadline registered (default)
Feb 20 16:48:59 raspberrypi kernel: io scheduler cfq registered
Feb 20 16:48:59 raspberrypi kernel: BCM2708FB: allocated DMA memory fad00000
Feb 20 16:48:59 raspberrypi kernel: BCM2708FB: allocated DMA channel 0 @ bb80f000
Feb 20 16:48:59 raspberrypi kernel: Console: switching to colour frame buffer device 160x64
Feb 20 16:48:59 raspberrypi kernel: bcm2835-rng 3f104000.rng: hwrng registered
Feb 20 16:48:59 raspberrypi kernel: vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
Feb 20 16:48:59 raspberrypi kernel: vc-sm: Videocore shared memory driver
Feb 20 16:48:59 raspberrypi kernel: brd: module loaded
Feb 20 16:48:59 raspberrypi kernel: loop: module loaded
Feb 20 16:48:59 raspberrypi kernel: Loading iSCSI transport class v2.0-870.
Feb 20 16:48:59 raspberrypi kernel: usbcore: registered new interface driver smsc95xx
Feb 20 16:48:59 raspberrypi kernel: dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
Feb 20 16:48:59 raspberrypi kernel: Core Release: 2.80a
Feb 20 16:48:59 raspberrypi kernel: Setting default values for core params
Feb 20 16:48:59 raspberrypi kernel: Finished setting default values for core params
Feb 20 16:48:59 raspberrypi kernel: Using Buffer DMA mode
Feb 20 16:48:59 raspberrypi kernel: Periodic Transfer Interrupt Enhancement - disabled
Feb 20 16:48:59 raspberrypi kernel: Multiprocessor Interrupt Enhancement - disabled
Feb 20 16:48:59 raspberrypi kernel: OTG VER PARAM: 0, OTG VER FLAG: 0
Feb 20 16:48:59 raspberrypi kernel: Dedicated Tx FIFOs mode
Feb 20 16:48:59 raspberrypi kernel: WARN::dwc_otg_hcd_init:1032: FIQ DMA bounce buffers: virt = 0xbad14000 dma = 0xfad14000 len=9024
Feb 20 16:48:59 raspberrypi kernel: FIQ FSM acceleration enabled for :
                                    Non-periodic Split Transactions
                                    Periodic Split Transactions
                                    High-Speed Isochronous Endpoints
                                    Interrupt/Control Split Transaction hack enabled
Feb 20 16:48:59 raspberrypi kernel: dwc_otg: Microframe scheduler enabled
Feb 20 16:48:59 raspberrypi kernel: WARN::hcd_init_fiq:459: FIQ on core 1 at 0x8058f5b0
Feb 20 16:48:59 raspberrypi kernel: WARN::hcd_init_fiq:460: FIQ ASM at 0x8058f920 length 36
Feb 20 16:48:59 raspberrypi kernel: WARN::hcd_init_fiq:486: MPHI regs_base at 0xbb87a000
Feb 20 16:48:59 raspberrypi kernel: dwc_otg 3f980000.usb: DWC OTG Controller
Feb 20 16:48:59 raspberrypi kernel: dwc_otg 3f980000.usb: new USB bus registered, assigned bus number 1
Feb 20 16:48:59 raspberrypi kernel: dwc_otg 3f980000.usb: irq 62, io mem 0x00000000
Feb 20 16:48:59 raspberrypi kernel: Init: Port Power? op_state=1
Feb 20 16:48:59 raspberrypi kernel: Init: Power Port (0)
Feb 20 16:48:59 raspberrypi kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Feb 20 16:48:59 raspberrypi kernel: usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Feb 20 16:48:59 raspberrypi kernel: usb usb1: Product: DWC OTG Controller
Feb 20 16:48:59 raspberrypi kernel: usb usb1: Manufacturer: Linux 4.9.59-v7+ dwc_otg_hcd
Feb 20 16:48:59 raspberrypi kernel: usb usb1: SerialNumber: 3f980000.usb
Feb 20 16:48:59 raspberrypi kernel: hub 1-0:1.0: USB hub found
Feb 20 16:48:59 raspberrypi kernel: hub 1-0:1.0: 1 port detected
Feb 20 16:48:59 raspberrypi kernel: dwc_otg: FIQ enabled
Feb 20 16:48:59 raspberrypi kernel: dwc_otg: NAK holdoff enabled
Feb 20 16:48:59 raspberrypi kernel: dwc_otg: FIQ split-transaction FSM enabled
Feb 20 16:48:59 raspberrypi kernel: Module dwc_common_port init
Feb 20 16:48:59 raspberrypi kernel: usbcore: registered new interface driver usb-storage
Feb 20 16:48:59 raspberrypi kernel: mousedev: PS/2 mouse device common for all mice
Feb 20 16:48:59 raspberrypi kernel: bcm2835-wdt 3f100000.watchdog: Broadcom BCM2835 watchdog timer
Feb 20 16:48:59 raspberrypi kernel: bcm2835-cpufreq: min=600000 max=900000
Feb 20 16:48:59 raspberrypi kernel: sdhci: Secure Digital Host Controller Interface driver
Feb 20 16:48:59 raspberrypi kernel: sdhci: Copyright(c) Pierre Ossman
Feb 20 16:48:59 raspberrypi kernel: sdhost-bcm2835 3f202000.sdhost: could not get clk, deferring probe
Feb 20 16:48:59 raspberrypi kernel: sdhci-pltfm: SDHCI platform and OF driver helper
Feb 20 16:48:59 raspberrypi kernel: ledtrig-cpu: registered to indicate activity on CPUs
Feb 20 16:48:59 raspberrypi kernel: hidraw: raw HID events driver (C) Jiri Kosina
Feb 20 16:48:59 raspberrypi kernel: usbcore: registered new interface driver usbhid
Feb 20 16:48:59 raspberrypi kernel: usbhid: USB HID core driver
Feb 20 16:48:59 raspberrypi kernel: vchiq: vchiq_init_state: slot_zero = 0xbad80000, is_master = 0
Feb 20 16:48:59 raspberrypi kernel: [vc_sm_connected_init]: start
Feb 20 16:48:59 raspberrypi kernel: [vc_sm_connected_init]: end - returning 0
Feb 20 16:48:59 raspberrypi kernel: Initializing XFRM netlink socket
Feb 20 16:48:59 raspberrypi kernel: NET: Registered protocol family 17
Feb 20 16:48:59 raspberrypi kernel: Key type dns_resolver registered
Feb 20 16:48:59 raspberrypi kernel: Registering SWP/SWPB emulation handler
Feb 20 16:48:59 raspberrypi kernel: registered taskstats version 1
Feb 20 16:48:59 raspberrypi kernel: uart-pl011 3f201000.serial: cts_event_workaround enabled
Feb 20 16:48:59 raspberrypi kernel: 3f201000.serial: ttyAMA0 at MMIO 0x3f201000 (irq = 87, base_baud = 0) is a PL011 rev2
Feb 20 16:48:59 raspberrypi kernel: console [ttyAMA0] enabled
Feb 20 16:48:59 raspberrypi kernel: sdhost: log_buf @ bad13000 (fad13000)
Feb 20 16:48:59 raspberrypi kernel: Indeed it is in host mode hprt0 = 00021501
Feb 20 16:48:59 raspberrypi kernel: mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
Feb 20 16:48:59 raspberrypi kernel: random: fast init done
Feb 20 16:48:59 raspberrypi kernel: of_cfs_init
Feb 20 16:48:59 raspberrypi kernel: of_cfs_init: OK
Feb 20 16:48:59 raspberrypi kernel: Waiting for root device PARTUUID=37665771-02...
Feb 20 16:48:59 raspberrypi kernel: mmc0: host does not support reading read-only switch, assuming write-enable
Feb 20 16:48:59 raspberrypi kernel: usb 1-1: new high-speed USB device number 2 using dwc_otg
Feb 20 16:48:59 raspberrypi kernel: Indeed it is in host mode hprt0 = 00001101
Feb 20 16:48:59 raspberrypi kernel: mmc0: new high speed SDHC card at address 59b4
Feb 20 16:48:59 raspberrypi kernel: mmcblk0: mmc0:59b4 00000 7.48 GiB
Feb 20 16:48:59 raspberrypi kernel:  mmcblk0: p1 p2
Feb 20 16:48:59 raspberrypi kernel: usb 1-1: New USB device found, idVendor=0424, idProduct=9514
Feb 20 16:48:59 raspberrypi kernel: usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 20 16:48:59 raspberrypi kernel: hub 1-1:1.0: USB hub found
Feb 20 16:48:59 raspberrypi kernel: hub 1-1:1.0: 5 ports detected
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.1: new high-speed USB device number 3 using dwc_otg
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Feb 20 16:48:59 raspberrypi kernel: smsc95xx v1.0.5
Feb 20 16:48:59 raspberrypi kernel: smsc95xx 1-1.1:1.0 eth0: register 'smsc95xx' at usb-3f980000.usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:6a:c0:14
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.2: new high-speed USB device number 4 using dwc_otg
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.2: New USB device found, idVendor=0bda, idProduct=8176
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.2: Product: 802.11n WLAN Adapter
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.2: Manufacturer: Realtek
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.2: SerialNumber: 00e04c000001
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.3: new high-speed USB device number 5 using dwc_otg
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.3: New USB device found, idVendor=0781, idProduct=5567
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.3: Product: Cruzer Blade
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.3: Manufacturer: SanDisk
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.3: SerialNumber: 4C530010010712110175
Feb 20 16:48:59 raspberrypi kernel: usb-storage 1-1.3:1.0: USB Mass Storage device detected
Feb 20 16:48:59 raspberrypi kernel: scsi host0: usb-storage 1-1.3:1.0
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.4: new full-speed USB device number 6 using dwc_otg
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.4: New USB device found, idVendor=05ac, idProduct=1002
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.4: Product: Hub in Apple Extended USB Keyboard
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.4: Manufacturer: Mitsumi Electric
Feb 20 16:48:59 raspberrypi kernel: hub 1-1.4:1.0: USB hub found
Feb 20 16:48:59 raspberrypi kernel: hub 1-1.4:1.0: 3 ports detected
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.4.1: new full-speed USB device number 7 using dwc_otg
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.4.1: New USB device found, idVendor=05ac, idProduct=0205
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.4.1: New USB device strings: Mfr=1, Product=3, SerialNumber=0
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.4.1: Product: Apple Extended USB Keyboard
Feb 20 16:48:59 raspberrypi kernel: usb 1-1.4.1: Manufacturer: Mitsumi Electric
Feb 20 16:48:59 raspberrypi kernel: input: Mitsumi Electric Apple Extended USB Keyboard as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.0/0003:05AC:0205.0001/input/input0
Feb 20 16:48:59 raspberrypi kernel: hid-generic 0003:05AC:0205.0001: input,hidraw0: USB HID v1.10 Keyboard [Mitsumi Electric Apple Extended USB Keyboard] on usb-3f980000.usb-1.4.1/input0
Feb 20 16:48:59 raspberrypi kernel: input: Mitsumi Electric Apple Extended USB Keyboard as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4.1/1-1.4.1:1.1/0003:05AC:0205.0002/input/input1
Feb 20 16:48:59 raspberrypi kernel: scsi 0:0:0:0: Direct-Access     SanDisk  Cruzer Blade     1.00 PQ: 0 ANSI: 6
Feb 20 16:48:59 raspberrypi kernel: hid-generic 0003:05AC:0205.0002: input,hidraw1: USB HID v1.10 Device [Mitsumi Electric Apple Extended USB Keyboard] on usb-3f980000.usb-1.4.1/input1
Feb 20 16:48:59 raspberrypi kernel: sd 0:0:0:0: [sda] 15630336 512-byte logical blocks: (8.00 GB/7.45 GiB)
Feb 20 16:48:59 raspberrypi kernel: sd 0:0:0:0: [sda] Write Protect is off
Feb 20 16:48:59 raspberrypi kernel: sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00
Feb 20 16:48:59 raspberrypi kernel: sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Feb 20 16:48:59 raspberrypi kernel:  sda: sda1 sda2
Feb 20 16:48:59 raspberrypi kernel: sd 0:0:0:0: [sda] Attached SCSI removable disk
Feb 20 16:48:59 raspberrypi kernel: EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
Feb 20 16:48:59 raspberrypi kernel: VFS: Mounted root (ext4 filesystem) readonly on device 8:2.
Feb 20 16:48:59 raspberrypi kernel: devtmpfs: mounted
Feb 20 16:48:59 raspberrypi kernel: Freeing unused kernel memory: 1024K
Feb 20 16:48:59 raspberrypi systemd[1]: System time before build time, advancing clock.
Feb 20 16:48:59 raspberrypi kernel: NET: Registered protocol family 10
Feb 20 16:48:59 raspberrypi kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
Feb 20 16:48:59 raspberrypi systemd[1]: systemd 232 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
Feb 20 16:48:59 raspberrypi systemd[1]: Detected architecture arm.
Feb 20 16:48:59 raspberrypi systemd[1]: Set hostname to <raspberrypi>.
Feb 20 16:48:59 raspberrypi kernel: uart-pl011 3f201000.serial: no DMA platform data
Feb 20 16:48:59 raspberrypi systemd[1]: Listening on fsck to fsckd communication Socket.
Feb 20 16:48:59 raspberrypi systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
Feb 20 16:48:59 raspberrypi systemd[1]: Created slice User and Session Slice.
Feb 20 16:48:59 raspberrypi systemd[1]: Listening on udev Control Socket.
Feb 20 16:48:59 raspberrypi systemd[1]: Listening on Journal Socket (/dev/log).
Feb 20 16:48:59 raspberrypi systemd[1]: Listening on /dev/initctl Compatibility Named Pipe.
Feb 20 16:48:59 raspberrypi systemd[1]: Listening on Journal Socket.
Feb 20 16:48:59 raspberrypi systemd-journald[139]: Journal started
-- Subject: The journal has been started
-- Defined-By: systemd
-- 
-- The system journal process has started up, opened the journal
-- files for writing and is now ready to process requests.
Feb 20 16:48:59 raspberrypi systemd-journald[139]: Runtime journal (/run/log/journal/763c6dc451944d169a59b87c57fd992f) is 5.7M, max 46.3M, 40.5M free.
-- Subject: Disk space used by the journal
-- Defined-By: systemd
-- 
-- Runtime journal (/run/log/journal/763c6dc451944d169a59b87c57fd992f) is currently using 5.7M.
-- Maximum allowed usage is set to 46.3M.
-- Leaving at least 69.5M free (of currently available 457.8M of disk space).
-- Enforced usage limit is thus 46.3M, of which 40.5M are still available.
-- 
-- The limits controlling how much disk space is used by the journal may
-- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
-- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
-- /etc/systemd/journald.conf. See journald.conf(5) for details.
Feb 20 16:48:59 raspberrypi fake-hwclock[115]: Tue 20 Feb 16:48:59 UTC 2018
Feb 20 16:48:59 raspberrypi systemd-fsck[127]: e2fsck 1.43.4 (31-Jan-2017)
Feb 20 16:48:59 raspberrypi systemd-fsck[127]: rootfs: clean, 42152/110656 files, 324989/441856 blocks
Feb 20 16:48:59 raspberrypi systemd[1]: Started Apply Kernel Variables.
-- Subject: Unit systemd-sysctl.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-sysctl.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:48:59 raspberrypi systemd[1]: Started Create Static Device Nodes in /dev.
-- Subject: Unit systemd-tmpfiles-setup-dev.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-tmpfiles-setup-dev.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:48:59 raspberrypi systemd[1]: Starting udev Kernel Device Manager...
-- Subject: Unit systemd-udevd.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit systemd-udevd.service has begun starting up.
Feb 20 16:48:59 raspberrypi systemd[1]: Started Remount Root and Kernel File Systems.
-- Subject: Unit systemd-remount-fs.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-remount-fs.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:48:59 raspberrypi kernel: EXT4-fs (sda2): re-mounted. Opts: (null)
Feb 20 16:48:59 raspberrypi systemd[1]: Starting udev Coldplug all Devices...
-- Subject: Unit systemd-udev-trigger.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit systemd-udev-trigger.service has begun starting up.
Feb 20 16:48:59 raspberrypi systemd[1]: Starting Flush Journal to Persistent Storage...
-- Subject: Unit systemd-journal-flush.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit systemd-journal-flush.service has begun starting up.
Feb 20 16:48:59 raspberrypi systemd[1]: Starting Load/Save Random Seed...
-- Subject: Unit systemd-random-seed.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit systemd-random-seed.service has begun starting up.
Feb 20 16:48:59 raspberrypi kernel: random: crng init done
Feb 20 16:48:59 raspberrypi systemd[1]: Started Load/Save Random Seed.
-- Subject: Unit systemd-random-seed.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-random-seed.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:48:59 raspberrypi systemd[1]: Started Set the console keyboard layout.
-- Subject: Unit keyboard-setup.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit keyboard-setup.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:48:59 raspberrypi systemd[1]: Started udev Kernel Device Manager.
-- Subject: Unit systemd-udevd.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-udevd.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:48:59 raspberrypi systemd-journald[139]: Runtime journal (/run/log/journal/763c6dc451944d169a59b87c57fd992f) is 5.7M, max 46.3M, 40.5M free.
-- Subject: Disk space used by the journal
-- Defined-By: systemd
-- 
-- Runtime journal (/run/log/journal/763c6dc451944d169a59b87c57fd992f) is currently using 5.7M.
-- Maximum allowed usage is set to 46.3M.
-- Leaving at least 69.5M free (of currently available 457.8M of disk space).
-- Enforced usage limit is thus 46.3M, of which 40.5M are still available.
-- 
-- The limits controlling how much disk space is used by the journal may
-- be configured with SystemMaxUse=, SystemKeepFree=, SystemMaxFileSize=,
-- RuntimeMaxUse=, RuntimeKeepFree=, RuntimeMaxFileSize= settings in
-- /etc/systemd/journald.conf. See journald.conf(5) for details.
Feb 20 16:48:59 raspberrypi systemd[1]: Reached target Local File Systems (Pre).
-- Subject: Unit local-fs-pre.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit local-fs-pre.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:48:59 raspberrypi systemd[1]: Started Flush Journal to Persistent Storage.
-- Subject: Unit systemd-journal-flush.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-journal-flush.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:49:00 raspberrypi systemd[1]: Started udev Coldplug all Devices.
-- Subject: Unit systemd-udev-trigger.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-udev-trigger.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:49:00 raspberrypi systemd[1]: Starting Show Plymouth Boot Screen...
-- Subject: Unit plymouth-start.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit plymouth-start.service has begun starting up.
Feb 20 16:49:00 raspberrypi systemd[1]: Received SIGRTMIN+20 from PID 204 (plymouthd).
Feb 20 16:49:00 raspberrypi kernel: gpiomem-bcm2835 3f200000.gpiomem: Initialised: Registers at 0x3f200000
Feb 20 16:49:00 raspberrypi systemd[1]: Started Show Plymouth Boot Screen.
-- Subject: Unit plymouth-start.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit plymouth-start.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:49:00 raspberrypi systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
-- Subject: Unit systemd-ask-password-plymouth.path has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-ask-password-plymouth.path has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:49:00 raspberrypi systemd[1]: Reached target Encrypted Volumes.
-- Subject: Unit cryptsetup.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit cryptsetup.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:49:00 raspberrypi systemd[1]: Reached target Paths.
-- Subject: Unit paths.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit paths.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:49:00 raspberrypi systemd[1]: Found device /dev/ttyAMA0.
-- Subject: Unit dev-ttyAMA0.device has finished start-up
-- Defined-By: systemd
-- 
-- Unit dev-ttyAMA0.device has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:49:00 raspberrypi mtp-probe[224]: checking bus 1, device 4: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.2"
Feb 20 16:49:00 raspberrypi mtp-probe[222]: checking bus 1, device 7: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.4/1-1.4.1"
Feb 20 16:49:00 raspberrypi mtp-probe[222]: bus: 1, device: 7 was not an MTP device
Feb 20 16:49:00 raspberrypi mtp-probe[219]: checking bus 1, device 3: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.1"
Feb 20 16:49:00 raspberrypi mtp-probe[224]: bus: 1, device: 4 was not an MTP device
Feb 20 16:49:00 raspberrypi mtp-probe[221]: checking bus 1, device 5: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3"
Feb 20 16:49:00 raspberrypi mtp-probe[221]: bus: 1, device: 5 was not an MTP device
Feb 20 16:49:00 raspberrypi mtp-probe[219]: bus: 1, device: 3 was not an MTP device
Feb 20 16:49:00 raspberrypi kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Feb 20 16:49:01 raspberrypi systemd[1]: Reached target Sound Card.
-- Subject: Unit sound.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit sound.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:49:01 raspberrypi systemd[1]: Created slice system-usb\x2dmount.slice.
-- Subject: Unit system-usb\x2dmount.slice has finished start-up
-- Defined-By: systemd
-- 
-- Unit system-usb\x2dmount.slice has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:49:01 raspberrypi systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.
-- Subject: Unit systemd-rfkill.socket has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-rfkill.socket has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:49:01 raspberrypi systemd[1]: Starting Load/Save RF Kill Switch Status...
-- Subject: Unit systemd-rfkill.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit systemd-rfkill.service has begun starting up.
Feb 20 16:49:01 raspberrypi kernel: usbcore: registered new interface driver rtl8192cu
Feb 20 16:49:01 raspberrypi systemd[1]: Started Load/Save RF Kill Switch Status.
-- Subject: Unit systemd-rfkill.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-rfkill.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:49:01 raspberrypi systemd-udevd[193]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Feb 20 16:49:01 raspberrypi systemd-udevd[194]: Process '/usr/sbin/th-cmd --socket /var/run/thd.socket --passfd --udev' failed with exit code 1.
Feb 20 16:50:01 raspberrypi systemd-udevd[161]: seq 876 '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1' is taking a long time
Feb 20 16:50:01 raspberrypi systemd-udevd[161]: seq 877 '/devices/platform/soc/3f980000.usb/usb1/1-1/1-1.3/1-1.3:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda2' is taking a long time
Feb 20 16:50:28 raspberrypi systemd[1]: dev-disk-by\x2dpartuuid-37665771\x2d01.device: Job dev-disk-by\x2dpartuuid-37665771\x2d01.device/start timed out.
Feb 20 16:50:28 raspberrypi systemd[1]: Timed out waiting for device dev-disk-by\x2dpartuuid-37665771\x2d01.device.
-- Subject: Unit dev-disk-by\x2dpartuuid-37665771\x2d01.device has failed
-- Defined-By: systemd
-- 
-- Unit dev-disk-by\x2dpartuuid-37665771\x2d01.device has failed.
-- 
-- The result is timeout.
Feb 20 16:50:28 raspberrypi systemd[1]: Dependency failed for /boot.
-- Subject: Unit boot.mount has failed
-- Defined-By: systemd
-- 
-- Unit boot.mount has failed.
-- 
-- The result is dependency.
Feb 20 16:50:28 raspberrypi systemd[1]: Dependency failed for Local File Systems.
-- Subject: Unit local-fs.target has failed
-- Defined-By: systemd
-- 
-- Unit local-fs.target has failed.
-- 
-- The result is dependency.
Feb 20 16:50:28 raspberrypi systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Feb 20 16:50:28 raspberrypi systemd[1]: local-fs.target: Triggering OnFailure= dependencies.
Feb 20 16:50:28 raspberrypi systemd-udevd[198]: Process '/bin/systemctl start usb-...@sda1.service' failed with exit code 1.
Feb 20 16:50:28 raspberrypi systemd[1]: boot.mount: Job boot.mount/start failed with result 'dependency'.
Feb 20 16:50:28 raspberrypi systemd[1]: Dependency failed for File System Check on /dev/disk/by-partuuid/37665771-01.
-- Subject: Unit systemd-fsck@dev-disk-by\x2dpartuuid-37665771\x2d01.service has failed
-- Defined-By: systemd
-- 
-- Unit systemd-fsck@dev-disk-by\x2dpartuuid-37665771\x2d01.service has failed.
-- 
-- The result is dependency.
Feb 20 16:50:28 raspberrypi systemd-udevd[190]: Process '/bin/systemctl start usb-...@sda2.service' failed with exit code 1.
Feb 20 16:50:28 raspberrypi systemd[1]: systemd-fsck@dev-disk-by\x2dpartuuid-37665771\x2d01.service: Job systemd-fsck@dev-disk-by\x2dpartuuid-37665771\x2d01.service/start failed with result 'dependency'.
Feb 20 16:50:28 raspberrypi systemd[1]: dev-disk-by\x2dpartuuid-37665771\x2d01.device: Job dev-disk-by\x2dpartuuid-37665771\x2d01.device/start failed with result 'timeout'.
Feb 20 16:50:28 raspberrypi systemd[1]: dev-serial1.device: Job dev-serial1.device/start timed out.
Feb 20 16:50:28 raspberrypi systemd[1]: Timed out waiting for device dev-serial1.device.
-- Subject: Unit dev-serial1.device has failed
-- Defined-By: systemd
-- 
-- Unit dev-serial1.device has failed.
-- 
-- The result is timeout.
Feb 20 16:50:28 raspberrypi systemd[1]: dev-serial1.device: Job dev-serial1.device/start failed with result 'timeout'.
Feb 20 16:50:28 raspberrypi systemd[1]: Starting File System Check on /dev/disk/by-partuuid/37665771-01...
-- Subject: Unit systemd-fsck@dev-disk-by\x2dpartuuid-37665771\x2d01.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit systemd-fsck@dev-disk-by\x2dpartuuid-37665771\x2d01.service has begun starting up.
Feb 20 16:50:28 raspberrypi systemd[1]: Starting Preprocess NFS configuration...
-- Subject: Unit nfs-config.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit nfs-config.service has begun starting up.
Feb 20 16:50:28 raspberrypi systemd[1]: Starting Raise network interfaces...
-- Subject: Unit networking.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit networking.service has begun starting up.
Feb 20 16:50:28 raspberrypi systemd[1]: Starting Set console font and keymap...
-- Subject: Unit console-setup.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit console-setup.service has begun starting up.
Feb 20 16:50:28 raspberrypi systemd[1]: Reached target Timers.
-- Subject: Unit timers.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit timers.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:28 raspberrypi systemd[1]: Reached target Login Prompts.
-- Subject: Unit getty.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit getty.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:28 raspberrypi systemd[1]: Started Emergency Shell.
-- Subject: Unit emergency.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit emergency.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:28 raspberrypi systemd[1]: Reached target Emergency Mode.
-- Subject: Unit emergency.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit emergency.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:28 raspberrypi systemd[1]: Starting Create Volatile Files and Directories...
-- Subject: Unit systemd-tmpfiles-setup.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit systemd-tmpfiles-setup.service has begun starting up.
Feb 20 16:50:28 raspberrypi systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
-- Subject: Unit plymouth-read-write.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit plymouth-read-write.service has begun starting up.
Feb 20 16:50:28 raspberrypi systemd[1]: Closed Syslog Socket.
-- Subject: Unit syslog.socket has finished shutting down
-- Defined-By: systemd
-- 
-- Unit syslog.socket has finished shutting down.
Feb 20 16:50:28 raspberrypi systemd[1]: Reached target Sockets.
-- Subject: Unit sockets.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit sockets.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:28 raspberrypi systemd[1]: Started Preprocess NFS configuration.
-- Subject: Unit nfs-config.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit nfs-config.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:28 raspberrypi systemd[1]: Started Set console font and keymap.
-- Subject: Unit console-setup.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit console-setup.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:28 raspberrypi systemd[1]: Started File System Check Daemon to report status.
-- Subject: Unit systemd-fsckd.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-fsckd.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:28 raspberrypi systemd[1]: Reached target NFS client services.
-- Subject: Unit nfs-client.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit nfs-client.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:28 raspberrypi systemd[1]: Reached target Remote File Systems (Pre).
-- Subject: Unit remote-fs-pre.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit remote-fs-pre.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:28 raspberrypi systemd[1]: Reached target Remote File Systems.
-- Subject: Unit remote-fs.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit remote-fs.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:28 raspberrypi systemd[1]: Started Create Volatile Files and Directories.
-- Subject: Unit systemd-tmpfiles-setup.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-tmpfiles-setup.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:28 raspberrypi systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
-- Subject: Unit plymouth-read-write.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit plymouth-read-write.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:28 raspberrypi systemd[1]: Starting Network Time Synchronization...
-- Subject: Unit systemd-timesyncd.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit systemd-timesyncd.service has begun starting up.
Feb 20 16:50:29 raspberrypi systemd[1]: Starting Update UTMP about System Boot/Shutdown...
-- Subject: Unit systemd-update-utmp.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit systemd-update-utmp.service has begun starting up.
Feb 20 16:50:29 raspberrypi systemd[1]: Started Update UTMP about System Boot/Shutdown.
-- Subject: Unit systemd-update-utmp.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-update-utmp.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:29 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes...
-- Subject: Unit systemd-update-utmp-runlevel.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit systemd-update-utmp-runlevel.service has begun starting up.
Feb 20 16:50:29 raspberrypi systemd-fsck[256]: fsck.fat 4.1 (2017-01-24)
Feb 20 16:50:29 raspberrypi systemd-fsck[256]: /dev/sda1: 144 files, 42655/83705 clusters
Feb 20 16:50:29 raspberrypi systemd[1]: Started File System Check on /dev/disk/by-partuuid/37665771-01.
-- Subject: Unit systemd-fsck@dev-disk-by\x2dpartuuid-37665771\x2d01.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-fsck@dev-disk-by\x2dpartuuid-37665771\x2d01.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:29 raspberrypi systemd[1]: Mounting /boot...
-- Subject: Unit boot.mount has begun start-up
-- Defined-By: systemd
-- 
-- Unit boot.mount has begun starting up.
Feb 20 16:50:29 raspberrypi systemd[1]: Started Update UTMP about System Runlevel Changes.
-- Subject: Unit systemd-update-utmp-runlevel.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-update-utmp-runlevel.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:29 raspberrypi systemd[1]: Mounted /boot.
-- Subject: Unit boot.mount has finished start-up
-- Defined-By: systemd
-- 
-- Unit boot.mount has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:29 raspberrypi systemd[1]: Started Network Time Synchronization.
-- Subject: Unit systemd-timesyncd.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-timesyncd.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:29 raspberrypi systemd[1]: Reached target System Time Synchronized.
-- Subject: Unit time-sync.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit time-sync.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:29 raspberrypi systemd[1]: Started Raise network interfaces.
-- Subject: Unit networking.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit networking.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:29 raspberrypi systemd[1]: Reached target Network.
-- Subject: Unit network.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit network.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:29 raspberrypi systemd[1]: Startup finished in 5.771s (kernel) + 1min 31.975s (userspace) = 1min 37.747s.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- 
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- 
-- Kernel start-up required 5771136 microseconds.
-- 
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- 
-- Userspace start-up required 91975960 microseconds.
Feb 20 16:50:29 raspberrypi systemd[1]: Received SIGRTMIN+21 from PID 204 (plymouthd).
Feb 20 16:50:45 raspberrypi systemd[1]: Stopped target Emergency Mode.
-- Subject: Unit emergency.target has finished shutting down
-- Defined-By: systemd
-- 
-- Unit emergency.target has finished shutting down.
Feb 20 16:50:45 raspberrypi systemd[1]: Stopping Emergency Shell...
-- Subject: Unit emergency.service has begun shutting down
-- Defined-By: systemd
-- 
-- Unit emergency.service has begun shutting down.
Feb 20 16:50:45 raspberrypi systemd[1]: Closed Load/Save RF Kill Switch Status /dev/rfkill Watch.
-- Subject: Unit systemd-rfkill.socket has finished shutting down
-- Defined-By: systemd
-- 
-- Unit systemd-rfkill.socket has finished shutting down.
Feb 20 16:50:45 raspberrypi systemd[1]: Stopped target Sound Card.
-- Subject: Unit sound.target has finished shutting down
-- Defined-By: systemd
-- 
-- Unit sound.target has finished shutting down.
Feb 20 16:50:45 raspberrypi systemd[1]: Stopping File System Check Daemon to report status...
-- Subject: Unit systemd-fsckd.service has begun shutting down
-- Defined-By: systemd
-- 
-- Unit systemd-fsckd.service has begun shutting down.
Feb 20 16:50:45 raspberrypi systemd[1]: Reached target Local File Systems.
-- Subject: Unit local-fs.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit local-fs.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting Preprocess NFS configuration...
-- Subject: Unit nfs-config.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit nfs-config.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting Tell Plymouth To Write Out Runtime Data...
-- Subject: Unit plymouth-read-write.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit plymouth-read-write.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting Show Plymouth Boot Screen...
-- Subject: Unit plymouth-start.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit plymouth-start.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Listening on Syslog Socket.
-- Subject: Unit syslog.socket has finished start-up
-- Defined-By: systemd
-- 
-- Unit syslog.socket has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Stopped File System Check Daemon to report status.
-- Subject: Unit systemd-fsckd.service has finished shutting down
-- Defined-By: systemd
-- 
-- Unit systemd-fsckd.service has finished shutting down.
Feb 20 16:50:45 raspberrypi systemd[1]: Stopped Emergency Shell.
-- Subject: Unit emergency.service has finished shutting down
-- Defined-By: systemd
-- 
-- Unit emergency.service has finished shutting down.
Feb 20 16:50:45 raspberrypi systemd[1]: Started Preprocess NFS configuration.
-- Subject: Unit nfs-config.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit nfs-config.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Started Tell Plymouth To Write Out Runtime Data.
-- Subject: Unit plymouth-read-write.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit plymouth-read-write.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Reached target System Initialization.
-- Subject: Unit sysinit.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit sysinit.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
-- Subject: Unit avahi-daemon.socket has finished start-up
-- Defined-By: systemd
-- 
-- Unit avahi-daemon.socket has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Started Daily Cleanup of Temporary Directories.
-- Subject: Unit systemd-tmpfiles-clean.timer has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-tmpfiles-clean.timer has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Reached target Basic System.
-- Subject: Unit basic.target has finished start-up
-- Defined-By: systemd
-- 
-- Unit basic.target has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting LSB: PiDP-8/I simulator...
-- Subject: Unit pidp8i.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit pidp8i.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting OpenBSD Secure Shell server...
-- Subject: Unit ssh.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit ssh.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting LSB: Autogenerate and use a swap file...
-- Subject: Unit dphys-swapfile.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit dphys-swapfile.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Started Regular background program processing daemon.
-- Subject: Unit cron.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit cron.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Listening on triggerhappy.socket.
-- Subject: Unit triggerhappy.socket has finished start-up
-- Defined-By: systemd
-- 
-- Unit triggerhappy.socket has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting triggerhappy global hotkey daemon...
-- Subject: Unit triggerhappy.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit triggerhappy.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting /etc/rc.local Compatibility...
-- Subject: Unit rc-local.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit rc-local.service has begun starting up.
Feb 20 16:50:45 raspberrypi cron[364]: (CRON) INFO (pidfile fd = 3)
Feb 20 16:50:45 raspberrypi systemd[1]: Listening on D-Bus System Message Bus Socket.
-- Subject: Unit dbus.socket has finished start-up
-- Defined-By: systemd
-- 
-- Unit dbus.socket has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Started D-Bus System Message Bus.
-- Subject: Unit dbus.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit dbus.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi cron[364]: (CRON) INFO (Running @reboot jobs)
Feb 20 16:50:45 raspberrypi thd[367]: Found socket passed from systemd
Feb 20 16:50:45 raspberrypi systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
-- Subject: Unit avahi-daemon.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit avahi-daemon.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting Save/Restore Sound Card State...
-- Subject: Unit alsa-restore.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit alsa-restore.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting Login Service...
-- Subject: Unit systemd-logind.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit systemd-logind.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting LSB: Switch to ondemand cpu governor (unless shift key is pressed)...
-- Subject: Unit raspi-config.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit raspi-config.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting System Logging Service...
-- Subject: Unit rsyslog.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit rsyslog.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting dhcpcd on all interfaces...
-- Subject: Unit dhcpcd.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit dhcpcd.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Starting Permit User Sessions...
-- Subject: Unit systemd-user-sessions.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit systemd-user-sessions.service has begun starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: apt-daily.timer: Adding 7h 21min 26.932356s random time.
Feb 20 16:50:45 raspberrypi systemd[1]: Started Daily apt download activities.
-- Subject: Unit apt-daily.timer has finished start-up
-- Defined-By: systemd
-- 
-- Unit apt-daily.timer has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 35min 38.729892s random time.
Feb 20 16:50:45 raspberrypi systemd[1]: Started Daily apt upgrade and clean activities.
-- Subject: Unit apt-daily-upgrade.timer has finished start-up
-- Defined-By: systemd
-- 
-- Unit apt-daily-upgrade.timer has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Started triggerhappy global hotkey daemon.
-- Subject: Unit triggerhappy.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit triggerhappy.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Received SIGRTMIN+20 from PID 356 (plymouthd).
Feb 20 16:50:45 raspberrypi systemd[1]: Started Show Plymouth Boot Screen.
-- Subject: Unit plymouth-start.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit plymouth-start.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Started /etc/rc.local Compatibility.
-- Subject: Unit rc-local.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit rc-local.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi systemd[1]: Started Save/Restore Sound Card State.
-- Subject: Unit alsa-restore.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit alsa-restore.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi avahi-daemon[374]: Found user 'avahi' (UID 108) and group 'avahi' (GID 112).
Feb 20 16:50:45 raspberrypi avahi-daemon[374]: Successfully dropped root privileges.
Feb 20 16:50:45 raspberrypi avahi-daemon[374]: avahi-daemon 0.6.32 starting up.
Feb 20 16:50:45 raspberrypi systemd[1]: Started Permit User Sessions.
-- Subject: Unit systemd-user-sessions.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-user-sessions.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:45 raspberrypi avahi-daemon[374]: Successfully called chroot().
Feb 20 16:50:45 raspberrypi avahi-daemon[374]: Successfully dropped remaining capabilities.
Feb 20 16:50:45 raspberrypi dhcpcd[379]: dev: loaded udev
Feb 20 16:50:45 raspberrypi avahi-daemon[374]: No service file found in /etc/avahi/services.
Feb 20 16:50:45 raspberrypi liblogging-stdlog[378]:  [origin software="rsyslogd" swVersion="8.24.0" x-pid="378" x-info="http://www.rsyslog.com"] start
Feb 20 16:50:45 raspberrypi avahi-daemon[374]: Network interface enumeration completed.
Feb 20 16:50:45 raspberrypi avahi-daemon[374]: Server startup complete. Host name is raspberrypi.local. Local service cookie is 1246829221.
Feb 20 16:50:45 raspberrypi systemd[1]: Started System Logging Service.
-- Subject: Unit rsyslog.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit rsyslog.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi sshd[386]: Server listening on 0.0.0.0 port 22.
Feb 20 16:50:46 raspberrypi sshd[386]: Server listening on :: port 22.
Feb 20 16:50:46 raspberrypi systemd[1]: Started OpenBSD Secure Shell server.
-- Subject: Unit ssh.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit ssh.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi dphys-swapfile[362]: Starting dphys-swapfile swapfile setup ...
Feb 20 16:50:46 raspberrypi pidp8i[359]: /opt/pidp8i/libexec/scanswitch not found
Feb 20 16:50:46 raspberrypi systemd[1]: Started Avahi mDNS/DNS-SD Stack.
-- Subject: Unit avahi-daemon.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit avahi-daemon.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd-logind[376]: New seat seat0.
-- Subject: A new seat seat0 is now available
-- Defined-By: systemd
-- 
-- A new seat seat0 has been configured and is now available.
Feb 20 16:50:46 raspberrypi systemd[1]: Starting Hold until boot process finishes up...
-- Subject: Unit plymouth-quit-wait.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit plymouth-quit-wait.service has begun starting up.
Feb 20 16:50:46 raspberrypi systemd[1]: Starting Terminate Plymouth Boot Screen...
-- Subject: Unit plymouth-quit.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit plymouth-quit.service has begun starting up.
Feb 20 16:50:46 raspberrypi systemd[1]: Started Login Service.
-- Subject: Unit systemd-logind.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit systemd-logind.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[1]: Received SIGRTMIN+21 from PID 356 (plymouthd).
Feb 20 16:50:46 raspberrypi systemd[1]: Started Hold until boot process finishes up.
-- Subject: Unit plymouth-quit-wait.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit plymouth-quit-wait.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[1]: Started Terminate Plymouth Boot Screen.
-- Subject: Unit plymouth-quit.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit plymouth-quit.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi dhcpcd[379]: wlan0: starting wpa_supplicant
Feb 20 16:50:46 raspberrypi systemd[1]: Started Serial Getty on ttyAMA0.
-- Subject: Unit serial...@ttyAMA0.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit serial...@ttyAMA0.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[1]: Started Getty on tty1.
-- Subject: Unit ge...@tty1.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit ge...@tty1.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi dhcpcd-run-hooks[434]: wlan0: starting wpa_supplicant
Feb 20 16:50:46 raspberrypi dphys-swapfile[362]: want /var/swap=100MByte, checking existing: keeping it
Feb 20 16:50:46 raspberrypi su[415]: Successful su for pi by root
Feb 20 16:50:46 raspberrypi su[415]: + ??? root:pi
Feb 20 16:50:46 raspberrypi su[415]: pam_unix(su:session): session opened for user pi by (uid=0)
Feb 20 16:50:46 raspberrypi systemd[1]: Created slice User Slice of pi.
-- Subject: Unit user-1000.slice has finished start-up
-- Defined-By: systemd
-- 
-- Unit user-1000.slice has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[1]: Starting User Manager for UID 1000...
-- Subject: Unit us...@1000.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit us...@1000.service has begun starting up.
Feb 20 16:50:46 raspberrypi systemd-logind[376]: New session c1 of user pi.
-- Subject: A new session c1 has been created for user pi
-- Defined-By: systemd
-- 
-- A new session with the ID c1 has been created for the user pi.
-- 
-- The leading process of the session is 415.
Feb 20 16:50:46 raspberrypi systemd[1]: Started Session c1 of user pi.
-- Subject: Unit session-c1.scope has finished start-up
-- Defined-By: systemd
-- 
-- Unit session-c1.scope has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi kernel: Adding 102396k swap on /var/swap.  Priority:-1 extents:1 across:102396k FS
Feb 20 16:50:46 raspberrypi dphys-swapfile[362]: done.
Feb 20 16:50:46 raspberrypi systemd[1]: Started LSB: Autogenerate and use a swap file.
-- Subject: Unit dphys-swapfile.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit dphys-swapfile.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[446]: pam_unix(systemd-user:session): session opened for user pi by (uid=0)
Feb 20 16:50:46 raspberrypi systemd[446]: Listening on GnuPG cryptographic agent (access for web browsers).
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[446]: Reached target Paths.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[446]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[446]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[446]: Reached target Timers.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[446]: Listening on GnuPG cryptographic agent and passphrase cache.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[446]: Reached target Sockets.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[446]: Reached target Basic System.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[446]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi systemd[446]: Startup finished in 144ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- 
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- 
-- Kernel start-up required KERNEL_USEC microseconds.
-- 
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- 
-- Userspace start-up required 144935 microseconds.
Feb 20 16:50:46 raspberrypi systemd[1]: Started User Manager for UID 1000.
-- Subject: Unit us...@1000.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit us...@1000.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:46 raspberrypi su[415]: pam_unix(su:session): session closed for user pi
Feb 20 16:50:46 raspberrypi pidp8i[359]: PiDP-8/I panel not present.  Booting from 0.script...
Feb 20 16:50:46 raspberrypi systemd-logind[376]: Removed session c1.
-- Subject: Session c1 has been terminated
-- Defined-By: systemd
-- 
-- A session with the ID c1 has been terminated.
Feb 20 16:50:46 raspberrypi systemd[1]: Stopping User Manager for UID 1000...
-- Subject: Unit us...@1000.service has begun shutting down
-- Defined-By: systemd
-- 
-- Unit us...@1000.service has begun shutting down.
Feb 20 16:50:47 raspberrypi systemd[446]: Stopped target Default.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- 
-- Unit UNIT has finished shutting down.
Feb 20 16:50:47 raspberrypi systemd[446]: Stopped target Basic System.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- 
-- Unit UNIT has finished shutting down.
Feb 20 16:50:47 raspberrypi systemd[446]: Stopped target Timers.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- 
-- Unit UNIT has finished shutting down.
Feb 20 16:50:47 raspberrypi systemd[446]: Stopped target Paths.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- 
-- Unit UNIT has finished shutting down.
Feb 20 16:50:47 raspberrypi systemd[446]: Stopped target Sockets.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- 
-- Unit UNIT has finished shutting down.
Feb 20 16:50:47 raspberrypi systemd[446]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- 
-- Unit UNIT has finished shutting down.
Feb 20 16:50:47 raspberrypi systemd[446]: Closed GnuPG cryptographic agent (access for web browsers).
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- 
-- Unit UNIT has finished shutting down.
Feb 20 16:50:47 raspberrypi systemd[446]: Closed GnuPG cryptographic agent (ssh-agent emulation).
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- 
-- Unit UNIT has finished shutting down.
Feb 20 16:50:47 raspberrypi systemd[446]: Closed GnuPG cryptographic agent and passphrase cache.
-- Subject: Unit UNIT has finished shutting down
-- Defined-By: systemd
-- 
-- Unit UNIT has finished shutting down.
Feb 20 16:50:47 raspberrypi systemd[446]: Reached target Shutdown.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi systemd[446]: Starting Exit the Session...
-- Subject: Unit UNIT has begun start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has begun starting up.
Feb 20 16:50:47 raspberrypi su[461]: Successful su for pi by root
Feb 20 16:50:47 raspberrypi su[461]: + ??? root:pi
Feb 20 16:50:47 raspberrypi su[461]: pam_unix(su:session): session opened for user pi by (uid=0)
Feb 20 16:50:47 raspberrypi systemd[446]: Received SIGRTMIN+24 from PID 462 (kill).
Feb 20 16:50:47 raspberrypi systemd[451]: pam_unix(systemd-user:session): session closed for user pi
Feb 20 16:50:47 raspberrypi systemd[1]: Starting User Manager for UID 1000...
-- Subject: Unit us...@1000.service has begun start-up
-- Defined-By: systemd
-- 
-- Unit us...@1000.service has begun starting up.
Feb 20 16:50:47 raspberrypi systemd-logind[376]: New session c2 of user pi.
-- Subject: A new session c2 has been created for user pi
-- Defined-By: systemd
-- 
-- A new session with the ID c2 has been created for the user pi.
-- 
-- The leading process of the session is 461.
Feb 20 16:50:47 raspberrypi systemd[1]: Started Session c2 of user pi.
-- Subject: Unit session-c2.scope has finished start-up
-- Defined-By: systemd
-- 
-- Unit session-c2.scope has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi systemd[472]: pam_unix(systemd-user:session): session opened for user pi by (uid=0)
Feb 20 16:50:47 raspberrypi raspi-config[377]: Checking if shift key is held down: No. Switching to ondemand scaling governor.
Feb 20 16:50:47 raspberrypi systemd[1]: Started LSB: Switch to ondemand cpu governor (unless shift key is pressed).
-- Subject: Unit raspi-config.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit raspi-config.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi kernel: IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Feb 20 16:50:47 raspberrypi systemd[472]: Listening on GnuPG cryptographic agent (ssh-agent emulation).
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi systemd[472]: Listening on GnuPG cryptographic agent and passphrase cache (restricted).
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi systemd[472]: Reached target Paths.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi systemd[472]: Listening on GnuPG cryptographic agent and passphrase cache.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi systemd[472]: Reached target Timers.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi systemd[472]: Listening on GnuPG cryptographic agent (access for web browsers).
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi systemd[472]: Reached target Sockets.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi systemd[472]: Reached target Basic System.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi systemd[472]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- 
-- Unit UNIT has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi systemd[472]: Startup finished in 86ms.
-- Subject: System start-up is now complete
-- Defined-By: systemd
-- 
-- All system services necessary queued for starting at boot have been
-- successfully started. Note that this does not mean that the machine is
-- now idle as services might still be busy with completing start-up.
-- 
-- Kernel start-up required KERNEL_USEC microseconds.
-- 
-- Initial RAM disk start-up required INITRD_USEC microseconds.
-- 
-- Userspace start-up required 86856 microseconds.
Feb 20 16:50:47 raspberrypi systemd[1]: Started User Manager for UID 1000.
-- Subject: Unit us...@1000.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit us...@1000.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi su[461]: pam_unix(su:session): session closed for user pi
Feb 20 16:50:47 raspberrypi pidp8i[359]: Starting PiDP-8/I simulator: pidp8i.
Feb 20 16:50:47 raspberrypi systemd[1]: Started LSB: PiDP-8/I simulator.
-- Subject: Unit pidp8i.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit pidp8i.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:47 raspberrypi dhcpcd[379]: eth0: waiting for carrier
Feb 20 16:50:47 raspberrypi dhcpcd[379]: wlan0: waiting for carrier
Feb 20 16:50:47 raspberrypi kernel: smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup
Feb 20 16:50:47 raspberrypi kernel: IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Feb 20 16:50:48 raspberrypi kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Feb 20 16:50:49 raspberrypi dhcpcd[379]: wlan0: carrier acquired
Feb 20 16:50:49 raspberrypi dhcpcd[379]: DUID 00:01:00:01:21:b0:da:2d:00:13:ef:d0:23:10
Feb 20 16:50:49 raspberrypi dhcpcd[379]: wlan0: IAID ef:d0:23:10
Feb 20 16:50:49 raspberrypi dhcpcd[379]: wlan0: adding address fe80::7f68:1be6:edad:2a33
Feb 20 16:50:49 raspberrypi dhcpcd[379]: wlan0: soliciting an IPv6 router
Feb 20 16:50:49 raspberrypi dhcpcd[379]: wlan0: rebinding lease of 192.168.0.46
Feb 20 16:50:49 raspberrypi dhcpcd[379]: wlan0: probing address 192.168.0.46/24
Feb 20 16:50:50 raspberrypi avahi-daemon[374]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::7f68:1be6:edad:2a33.
Feb 20 16:50:50 raspberrypi avahi-daemon[374]: New relevant interface wlan0.IPv6 for mDNS.
Feb 20 16:50:50 raspberrypi avahi-daemon[374]: Registering new address record for fe80::7f68:1be6:edad:2a33 on wlan0.*.
Feb 20 16:50:54 raspberrypi dhcpcd[379]: wlan0: leased 192.168.0.46 for 86400 seconds
Feb 20 16:50:54 raspberrypi dhcpcd[379]: wlan0: adding route to 192.168.0.0/24
Feb 20 16:50:54 raspberrypi dhcpcd[379]: wlan0: adding default route via 192.168.0.1
Feb 20 16:50:54 raspberrypi avahi-daemon[374]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.46.
Feb 20 16:50:54 raspberrypi avahi-daemon[374]: New relevant interface wlan0.IPv4 for mDNS.
Feb 20 16:50:54 raspberrypi avahi-daemon[374]: Registering new address record for 192.168.0.46 on wlan0.IPv4.
Feb 20 16:50:55 raspberrypi dhcpcd[379]: forked to background, child pid 549
Feb 20 16:50:55 raspberrypi systemd[1]: Started dhcpcd on all interfaces.
-- Subject: Unit dhcpcd.service has finished start-up
-- Defined-By: systemd
-- 
-- Unit dhcpcd.service has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:50:56 raspberrypi login[439]: pam_unix(login:session): session opened for user pi by LOGIN(uid=0)
Feb 20 16:50:56 raspberrypi systemd-logind[376]: New session c3 of user pi.
-- Subject: A new session c3 has been created for user pi
-- Defined-By: systemd
-- 
-- A new session with the ID c3 has been created for the user pi.
-- 
-- The leading process of the session is 439.
Feb 20 16:50:56 raspberrypi systemd[1]: Started Session c3 of user pi.
-- Subject: Unit session-c3.scope has finished start-up
-- Defined-By: systemd
-- 
-- Unit session-c3.scope has finished starting up.
-- 
-- The start-up result is done.
Feb 20 16:51:11 raspberrypi systemd-timesyncd[281]: Synchronized to time server 162.213.35.121:123 (2.debian.pool.ntp.org).
Feb 20 16:51:11 raspberrypi systemd[472]: Time has been changed
-- Subject: Time change
-- Defined-By: systemd
-- 
-- The system clock has been changed to REALTIME microseconds after January 1st, 1970.
Feb 20 16:51:11 raspberrypi systemd[1]: Time has been changed
-- Subject: Time change
-- Defined-By: systemd
-- 
-- The system clock has been changed to REALTIME microseconds after January 1st, 1970.
Feb 20 16:51:11 raspberrypi systemd[1]: apt-daily.timer: Adding 6h 37min 3.626799s random time.
Feb 20 16:51:11 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 20min 51.647973s random time.
Feb 20 16:51:14 raspberrypi dhcpcd[549]: wlan0: no IPv6 Routers available

 

Warren Young

unread,
Feb 20, 2018, 3:36:28 PM2/20/18
to pid...@googlegroups.com
On Tuesday, February 20, 2018 at 9:59:28 AM UTC-7, James Zeun wrote:
So after my last message, I began rebuilding the system using a copy of raspbian lite. All was working fine until I install the pidp8i software and all of a sudden, I'm back in to emergency mode. 

I don't see how your dmesg output correlates with installation of the pidp8i service.  The root device isn't even mounted at that point, so the pidp8i service *can't* be run at that point;

You've got to fix the root device mount failure before you're back on a topic we can reasonably talk about on this list.

Do disrespect intended Warren, as I think your doing a great job supporting the PiDP8. But there is clearly something not right with how this emulator installs on the latest version of Raspbian, somewhere along the lines its messing up.

The only problems I'm aware of in that area are that we're still using an old-style SysV init script to start the PiDP-8/I service rather than a systemd unit file, which is why things like "sudo systemctl restart pidp8i" don't work reliably. Once I get around to changing that over to systemd, those problems will go away.

As a bonus, you'll be able to do without the "sudo", meaning that the only time you'll need sudo is for "sudo make install".

But again, none of that matters while the root device cannot be mounted.

James Zeun

unread,
Feb 22, 2018, 9:59:10 AM2/22/18
to pid...@googlegroups.com
"I don't see how your dmesg output correlates with installation of the pidp8i service.  The root device isn't even mounted at that point, so the pidp8i service *can't* be run at that point;"

Because you ask me to show you the output of systemctl, do you not remember? lol

"But now that you've got a working OS, you could post the output of the systemctl command it prompts you to enter to get more details."

I simply piped it to a text file.

I'm not sure why the mount root failure is happening, but it only appears to happen after following the installation instructions on the website. I'm going to spend some time today testing, see what I can find out.





On Tuesday, 20 February 2018 20:36:28 UTC, Warren Young wrote:
On Tuesday, February 20, 2018 at 9:59:28 AM UTC-7, James Zeun wrote:
So after my last message, I began rebuilding the system using a copy of raspbian lite. All was working fine until I install the pidp8i software and all of a sudden, I'm back in to emergency mode. 



Warren Young

unread,
Feb 22, 2018, 10:37:43 AM2/22/18
to pid...@googlegroups.com
On Thursday, February 22, 2018 at 7:59:10 AM UTC-7, James Zeun wrote:
"I don't see how your dmesg output correlates with installation of the pidp8i service.  The root device isn't even mounted at that point, so the pidp8i service *can't* be run at that point;"

Because you ask me to show you the output of systemctl, do you not remember? lol

I'm not questioning why you posted it, I'm saying that what you show doesn't implicate the pidp8i service as the source of your problems. Your system is failing before the pidp8i service is even available to the OS.
 
However, I've just had an epiphany: I think our new USB auto-mounting feature might be interfering with your nonstandard USB boot setup. I've just added a new configure option, --disable-usb-automount, which prevents this from being installed.

Try the latest trunk version on a freshly-reflashed SD card, being sure to set this option before you call "sudo make install".

See my other post today to the group for more information on the change to the way the pidp8i service is managed.

"But now that you've got a working OS, you could post the output of the systemctl command it prompts you to enter to get more details."

I simply piped it to a text file.

You've misunderstood me. When you get back to a point where you get the "c1" error again, the next line(s) tell you to run some systemctl or journalctl command, the details of which I've forgotten. I'm asking you to run that command and post the results here.

Obviously you need to fix the root device mounting problem before you can get back to diagnosing the c1 error.

EDIT: It is possible that by moving the pidp8i service from system-level to user-level that we'll fix the c1 error as a side effect. It's plausible, since this error has something to do with systemd, and this change moves our service from being a bag-on-the-side of systemd to being properly integrated with systemd.

James Zeun

unread,
Feb 22, 2018, 11:19:11 AM2/22/18
to PiDP-8
Warren I have very important question to ask, because something happened while i was testing.

I just flashed Stretch lite to a brand new 16gb sd card, installed the Pidp8 package and its booting fine. I'm not getting the C1 error or a journalctrl. I'm getting zero, null errors whats so ever.

I came back to report the install worked for some bizarre reason, but seeing what you wrote, I now have to ask would the alterations you mentioned have any bearing on the install process outlined on your site? 

Either the modifications you've made fixed the issue or I must consider that one of the follow has cleared up the problem
A. Using a completely different, brand new SD card
B. Changing the PSU ( credit to AndyB, whose message spurred me to swap it, just in case! lol) 

James Zeun

unread,
Feb 22, 2018, 12:08:27 PM2/22/18
to PiDP-8
Would appear I spoke to soon

After everything appeared alright, I tried to configure the Pi to use USB. I encountered an error half way, for some reason the script had issue writing to the usb pen. However thats unimportant, what occurred next is.

I rebooted and the C1 error returned..I'm going back to format the system and try out the alterations Warren mentioned in his last post. Before I wiped the SD, I did as Warren asked and grabbed the info from the following command

> systemctl status session-c1.scope

I had to grab it using my phone, so will post the text here in a bit.

Warren Young

unread,
Feb 22, 2018, 12:10:18 PM2/22/18
to PiDP-8
On Thursday, February 22, 2018 at 9:19:11 AM UTC-7, James Zeun wrote:

I just flashed Stretch lite to a brand new 16gb sd card, installed the Pidp8 package and its booting fine.

When you pull a new zip file or tarball using the links in the "bleeding edge" paragraph on the project's home page or via the goo.gl link in the README.md file, you get the tip of trunk at the moment you make the request.

When you first enter the PiDP-8/I simulator with a bare "pidp8i" command, the first line you get at the top of the screen includes the Fossil checkin ID for the version you're running. It will look something like this:

    PiDP-8/I trunk:id[xxxxxxxx] [pi3b] [ils] [sermodpcb] [gpio] [rt]
 
You can match the xxxxxxxx bit against the check-in IDs on the timeline page. This will tell you which changes you've got and which ones you don't have yet.

I'm not getting the C1 error or a journalctrl. I'm getting zero, null errors whats so ever.

That was a plausible outcome from moving from SysV init to a systemd user unit.

However, I seem to recall that you had this happen before, then the error came back seemingly on its own, so let's do some more testing before we declare the problem definitively solved.
 
would the alterations you mentioned have any bearing on the install process outlined on your site? 

Several of the documentation files did change. Basically, all of the "sudo systemctl $VERB pidp8i" commands had to be changed. Again, see my other thread.
 
Either the modifications you've made fixed the issue

The change from SysV init to systemd doesn't explain the failure to mount the root filesystem. At least, it doesn't explain it to me.

The feature I just added to disable USB automount would explain it, but it sounds like you didn't set that option, so you're still using our new USB automounter.

When I said above that it's important to set this option before installation, it's because setting it afterward and then re-installing won't remove the USB automounter stuff. Not yet anyway, and maybe not ever. At the moment, you'd have to read through the "install" target in Makefile.in and manually undo the commands that are now enclosed in the USB_AUTOMOUNT conditional. This is a fair bit of work to do by hand, and it would be even more work to write an uninstaller for it, which is why it doesn't do that yet, and might never do so.
 
B. Changing the PSU ( credit to AndyB, whose message spurred me to swap it, just in case! lol) 

That's actually a pretty good possibility, one I considered making. I resisted because it's also possibly just voodoo. I'd have wanted measurements showing that the previous PSU was too weak before I'd have been confident making the recommendation that you change it.

A weak PSU can explain a lot of weirdness with a computer. That's all computers, not just the RPi.

James Zeun

unread,
Feb 22, 2018, 12:12:52 PM2/22/18
to PiDP-8
Not sure if it's pertinent, but here is the output. Apologies for it being an image.
IMG_20180222_163936~2.jpg

Warren Young

unread,
Feb 22, 2018, 12:17:52 PM2/22/18
to PiDP-8
On Thursday, February 22, 2018 at 10:10:18 AM UTC-7, Warren Young wrote:
When you first enter the PiDP-8/I simulator with a bare "pidp8i" command, the first line you get at the top of the screen includes the Fossil checkin ID for the version you're running. It will look something like this:

    PiDP-8/I trunk:id[xxxxxxxx] [pi3b] [ils] [sermodpcb] [gpio] [rt]

Never mind. The checkin ID can only be properly populated when you check out a version from Fossil directly, rather than build the software from a non-release zip file or tarball.

Working around that would be difficult.

You'll have to use timestamps to work out exactly what version you have.

Warren Young

unread,
Feb 22, 2018, 12:20:37 PM2/22/18
to PiDP-8
On Thursday, February 22, 2018 at 10:12:52 AM UTC-7, James Zeun wrote:
Not sure if it's pertinent, but here is the output. Apologies for it being an image.

Okay, thanks.

That then makes it important to know which version you're running.

One easy heuristic is to say "find ~/.local". If you get a list of files, you've got one of the versions after I started moving from SysV to systemd, though not necessarily the final version. If you get an error, then you're still running with the old SysV init script, so you haven't actually tested any of the new code. 

Warren Young

unread,
Feb 22, 2018, 12:34:32 PM2/22/18
to PiDP-8
On Thursday, February 22, 2018 at 10:10:18 AM UTC-7, Warren Young wrote:

When you pull a new...tarball using...the goo.gl link

...you get the latest *release* version, not the tip of trunk. (The goo.gl status page was hiding the URL parameter that changed the meaning of the URL from its default to giving the release version...sigh.) 

So, use the "bleeding edge" links on the home page if you want the tip of trunk.

James Zeun

unread,
Feb 22, 2018, 12:36:44 PM2/22/18
to PiDP-8
Sadly will be away for the next couple of days, so wont be able to work on this further. After taking that photo, I wiped the SD, I figured it would be better to reinstall the PiDP8 software with the alteration to the automount function. 

I've got as far as unpacking the PiDP8 tar files, I've get to ./configure

So when i get back on Sunday, I'll see how I get on. 

In regards to the PSU, I had thought about it and really I should have acted on it. However I guess I was being complacent, believing that having worked for 6 months without issue, there was not reason for it to suddenly become a factor. However from this point forward, I shall be using an official RPI 2.5a PSU, just to be on the safe side.

James Zeun

unread,
Mar 1, 2018, 1:15:28 PM3/1/18
to PiDP-8
Finally back from Wales, the journey ended up making me badly.

At last sat behind the pidp8, Warren looking back at what you wrote. I wasn't entirely sure where I implement the -disable-USB-automount

Message has been deleted

James Zeun

unread,
Mar 1, 2018, 1:28:07 PM3/1/18
to PiDP-8
Alright I've hit a slight bump in the road --disable-usb-automount is not a recognised option.
./configure --help does not list it

Did I fowl up somewhere?

Warren Young

unread,
Mar 1, 2018, 4:03:17 PM3/1/18
to PiDP-8
The option was added while we were in the middle of the last flurry of messages on this topic. Are you still building from a package downloaded from back then? If so, you might just need to update.

Is there a good reason you can't use Fossil, by the way? It would make all of this much easier on the both of us.

The only good reason, IMHO, is that your Pi has no networking.

Warren Young

unread,
Mar 2, 2018, 2:25:04 AM3/2/18
to PiDP-8
On Thursday, March 1, 2018 at 2:03:17 PM UTC-7, Warren Young wrote:

The only good reason, IMHO, is that your Pi has no networking.

Oh, in case the argument against using Fossil is that it's too difficult to bootstrap on a Pi, due to the outdated version still being shipped by Raspbian — due to the upstream Debian stability policy, by the way, not out of anyone's laziness —  I've been making available Pi builds of Fossil for a while now:


Just wget the binary and rename it something more useful, like "fossil" or even "f", then chmod +x it, and you're up and running.

...provided your Pi has networking, of course.

James Zeun

unread,
Mar 2, 2018, 5:54:12 AM3/2/18
to PiDP-8
Hi

I'm working from this binary, as per the online instructions

get -O pidp8i.tar.gz https://goo.gl/JowPoC

Is this not the most recent?

Warren Young

unread,
Mar 2, 2018, 5:59:21 AM3/2/18
to PiDP-8
It's the most recent *release*, but not the tip of trunk, which is what will *become* the next release.

James Zeun

unread,
Mar 2, 2018, 6:00:05 AM3/2/18
to PiDP-8
Sorry Warren

I had seen mention of using fossil get the latest version of the binary, but hadn't thought to use it. I will go give it a try!

Reply all
Reply to author
Forward
0 new messages