Dan McManus

I appreciate the help but this seems above my current skill set. I did download a new iso, format the USB and reload. There was a slightly different error saying something about not finding a file. Is loading PeppermintOS somehow different than other distros? After my PeppermintOS attempts, I loaded Linux Lite and it worked fine. Previously, I had Lubuntu, Xubuntu, Bunsen labs and probably something else with no issues.

The Chromebook was not originally a UEFI device but UEFI firmware was added by the process in the link below. I do not know if this is different from a system that was originally UEFI. I have never fooled with partitions before. Do I have to be careful of somthing particular so I don't permanantly kill the system? When I open GParted, the partitions have odd names, /dev/mmcblk0p1, 2 and 3. The first has and exclamation mark after the name , is 300 MiB with 0 used and is flagged boot, esp. It is a...

The Chromebook was not originally a UEFI device but UEFI firmware was added by the process in the link below. I do not know if this is different from a system that was originally UEFI. I have never fooled with partitions before. Do I have to be careful of somthing particular so I don't permanantly kill the system? When I open GParted, the partitions have odd names, /dev/mmcblk0p1, 2 and 3. The first has and exclamation mark after the name , is 300 MiB with 0 used and is flagged boot, esp. It is a...

The Chromebook was not originally a UEFI device but UEFI firmware was added by the process in the link below. I do not know if this is different from a system that was originally UEFI. I have never fooled with partitions before. Do I have to be careful of somthing particular so I don't permanantly kill the system? https://mrchromebox.tech/#fwscript

I have an install failure on a Chromebook with - Braswell Dual Core 1.6 GHz, 2 GB memory, 16 GB eMMC storage. This was an "erase the disc" type install so I have no other OS. Although the previous OS, ubuntu, shows in the boot menu, it fails. The install was very slow and hung for a while around 73%. I repeated the install a couple of times but it never worked. This is what I get on reboot after installation. ---[ end Kernel panic – not syncing: UFS: Unable to mount root fs on unknown-block(0,0)...

After trying everything I could find on line, I reloaded pulse audio and ran "padsp xoscope". After slowing down the time scale several steps, the signals were there. This seems linked to the lack of /dev/dsp. I'm just not sure if it was the reload or something else I tried. Things tried: sudo apt-get update sudo apt-get install pulseaudio sudo apt-get install pavucontrol sudo apt-get install osspd sudo apt-get install osspd-alsa osspd xoscope sudo apt-get install alsa-oss then type: aoss xoscope...

After trying everything I could find on line, I reloaded pulse audio and ran "padsp xoscope". After slowing down the time scale several steps, the signals were there. This seems linked to the lack of /dev/dsp. I'm just not sure if it was the reload or something else I tried. Things tried: sudo apt-get update sudo apt-get install pulseaudio sudo apt-get install pavucontrol sudo apt-get install osspd sudo apt-get install osspd-alsa osspd xoscope sudo apt-get install alsa-oss then type: aoss xoscope...

I posted this in general discussion first by accident so I'll repost here. I have Xoscope loaded with 16.04 on a Gateway NE71B. It loads and seems to recognize the right and left stereo sides of my sound card. It does not recognize a USB sound card I tried. I built a probe adapter and when connected to an approximately 10 hz source, I see nothing on the screen except some random noise. The noise stays when I unplug the adapter. I tried randomly varying the scale, time base and sample rate with no...