Jump to content

TJMcK

Members
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About TJMcK

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Canada
  1. TJMcK

    Moksha problems on Bodhi 3.2.1

    I've tried a few things in the past few hours... if these changes don't solve the problem, I will do as you suggest and reconfigure .e settings. Thanks.
  2. TJMcK

    Moksha problems on Bodhi 3.2.1

    I perform a short-test and extended-test with smartctl -- both didn't show any errors. And there should be plenty in the /home folder (found in /) -- I checked trash and there was <1Gb.
  3. TJMcK

    Moksha problems on Bodhi 3.2.1

    Filesystem Size Used Avail Use% Mounted on udev 2.7G 4.0K 2.7G 1% /dev tmpfs 554M 1.5M 553M 1% /run /dev/sdb2 112G 12G 94G 12% / none 4.0K 0 4.0K 0% /sys/fs/cgroup none 5.0M 0 5.0M 0% /run/lock none 2.8G 12M 2.7G 1% /run/shm none 100M 8.0K 100M 1% /run/user /dev/sdb1 511M 6.9M 505M 2% /boot/efi
  4. TJMcK

    Moksha problems on Bodhi 3.2.1

    The past few weeks I've had problems with Bodhi, most likely caused by Moksha. This occurs almost every day (normally I like to leave my laptop on 24/7). I've not reported the problem sooner because I wanted to associate it with an event or app, but I can't make any correlation. I realize that there is a problem when starting an app and I get a Moksha error dialog: "Miksha settings write problem". From that point on I can't logout or poweroff in any way (with keystrokes or via terminal). As well, no apps will open/start. The Moksha dialog box does not show any details and after doing a hard-reboot I cannot find any file reporting the failure. I have read as much as I could find regarding this issue: for instance, my drive has enough space (although it is an external SSD) - but this has not been a problem earlier. I also read that the network manager has been associated with Moksha problems... I installed the Private Internet Access deb package around the time that the issues started -- but I also installed Wine and the NVidia/Radeon proprietary driver with Catalyst at this time. Do you have suggestions on what I could try/do to fix this? I noticed there has been a Moksha v.0.2.1 released -- should I try installing this? (it appears that I'm using 0.2.0) - Tim
  5. TJMcK

    Bodhi 4 Software Requests

    Software Name: FlashPeak Slimjet Software Homepage: http://www.slimjet.com/ Requested Version Number: current http://www.slimjet.com/en/dlpage.php Link to Source Code: same as above Link to Debian packages/PPA: unaware of PPA; Deb pkg http://www.slimjet.com/en/dlpage.php Extra Notes: I have tested Midori and Firefox in Bodhi3, and found Slimjet to be much faster (especially when opening/starting in older/slower machines). If I recall correctly, when I first installed it, there were some issues -- but then I uninstalled Slimjet, installed Chromium from the Bodhi repository, and reinstalled Slimjet -- since then it has been working perfectly. (I suggest that you consider having a Bodhi edition available in the Bodhi repository, with the Chromium tweaks) Thx
  6. TJMcK

    fixing Bodhi boot

    Thank you gohlip!! Your instruction were perfect. Bodhi is working again, just as before. (I only need to us F12 when I am booting with cold/hard boot -- I think that CMOS doesn't catch the USB drive in time.) This problem has shown how little I know about UEFI booting... and without your support I couldn't have fixed this.
  7. TJMcK

    fixing Bodhi boot

    I was just thinking that it would save space (and time) if I didn't include the hd info. As for OS... I only use Linux -- no Windows anywhere -- I only have one useable Linux distro on the hd (haven't used in months), the other partitions are previous version of /home and /, plus the big partition is for /media/Data. And yes, my computer is uefi capable (Bodhi was booting from uefi before it broke) Here's the complete terminal output for "sudo parted -l": Model: ATA WDC WD7500BPVT-2 (scsi) Disk /dev/sda: 750GB Sector size (logical/physical): 512B/4096B Partition Table: msdos Number Start End Size Type File system Flags 1 1049kB 5000MB 4999MB primary ext4 boot 2 5001MB 750GB 745GB extended 5 5001MB 80.0GB 75.0GB logical ext4 6 80.0GB 330GB 250GB logical ext4 8 330GB 333GB 2690MB logical ext4 9 333GB 372GB 39.3GB logical ext4 10 372GB 477GB 105GB logical ext4 11 477GB 747GB 270GB logical ext2 7 747GB 750GB 2999MB logical linux-swap(v1) Model: Kingston SNA-DC/U (scsi) Disk /dev/sdb: 128GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start End Size File system Name Flags 1 1049kB 538MB 537MB fat32 boot 2 538MB 122GB 122GB ext4 3 122GB 128GB 5983MB linux-swap(v1)
  8. TJMcK

    fixing Bodhi boot

    Thanks for the quick response gohlip. Here's the terminal output of the commands you posted (less the lengthly internal hd details): tim@bodhi3-64-laptop:~$ findmnt / TARGET SOURCE FSTYPE OPTIONS / /dev/disk/by-uuid/f47ae7c0-6d70-4d3f-95f4-a0658a8a2267 ext4 rw,relatime tim@bodhi3-64-laptop:~$ findmnt /boot/efi TARGET SOURCE FSTYPE OPTIONS /boot/efi /dev/sdb1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro tim@bodhi3-64-laptop:~$ test -d /sys/firmware/efi && echo UEFI || echo BIOS BIOS tim@bodhi3-64-laptop:~$ sudo fdisk -l [sudo] password for tim: Disk /dev/sda: 750.2 GB, 750156374016 bytes ... other hd details omitted... Partition table entries are not in disk order WARNING: GPT (GUID Partition Table) detected on '/dev/sdb'! The util fdisk doesn't support GPT. Use GNU Parted. Disk /dev/sdb: 128.0 GB, 128035675648 bytes 255 heads, 63 sectors/track, 15566 cylinders, total 250069679 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdb1 1 250069678 125034839 ee GPT tim@bodhi3-64-laptop:~$ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic root=UUID=f47ae7c0-6d70-4d3f-95f4-a0658a8a2267 ro tim@bodhi3-64-laptop:~$ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sdb2 during installation UUID=f47ae7c0-6d70-4d3f-95f4-a0658a8a2267 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/sdb1 during installation #UUID=C0D5-870D /boot/efi vfat defaults 0 1 # swap was on /dev/sdb3 during installation UUID=650d5021-37f6-4305-aed6-4a7976ff804f none swap sw 0 0 UUID=C0D5-870D /boot/efi vfat defaults 0 1 tim@bodhi3-64-laptop:~$ sudo blkid ... hard drive details omitted... /dev/sr0: LABEL="UBCD50RC1" TYPE="iso9660" /dev/sdb1: UUID="C0D5-870D" TYPE="vfat" /dev/sdb2: UUID="f47ae7c0-6d70-4d3f-95f4-a0658a8a2267" TYPE="ext4" /dev/sdb3: UUID="650d5021-37f6-4305-aed6-4a7976ff804f" TYPE="swap" ------------------------------------------- EDIT: I thought I should mention that I am currently running with a BIOS grub boot, however the original / installation of Bodhi did use EFI. (Personally don't care how Bodhi boots, BIOS or EFI, doesn't matter to me.)
  9. TJMcK

    fixing Bodhi boot

    Bodhi3 was working fine on my ext usb3 ssd. A couple times over the few weeks (couple months) it had frozen -- Moksha would give me a few error messages. Then, I'd have to do a hard reset to shut down, but it would always start right up again... except not this last time! I had a suspicion that it was the bootloader (grub2), so I boot an old Ubuntu CD, downloaded boot-repair and ran it. It complained of GPT errors and would not fix the problem. (I tried a few different options, but no luck). However today, I was flipping through some old CD/DVDs and came across a copy of "The Ultimate Boot CD". Started it up, found the section for boot-loaders, scrolled down and clicked on Grub2, then clicked on AUTOGRUB -- and it gave me a list of all possible kernal boots (ie. generic, multiuser, efi, efi + multiuser, etc). I chose the generic option for the Bodhi kernal and within a few seconds, up popped my logon screen!! Everything appears to be working fine, but... I can't get Grub to install. I thought there would be a way to rebuilt grub from within Bodhi. I've been looking for a couple hours and found no command (which I'm pretty sure exists). Can someone help -- I thought this would be an easy fix (or I just have to keep booting Bodhi with UBCD).
  10. TJMcK

    Installer not working...

    That was a quick release (fix) of v.4 beta2! Unfortunately, I still have the same problem -- ubiquity does not start and gives an error message. I also tried v.4x 32-bit, and the installer works until near the end, then it says that it can't install grub. I haven't taken the time to try and install grub manually, partly because I suspect that I may need the efi grub and there are a lot of unknowns for me (ie do I install the efi grub/ do I need the signed version, etc). It's unfortunate that it doesn't work out of the box, but this may be because of my laptop hardware -- older Acer with x2 AMD. I may just keep using v3 as I had no problems installing that on my USB3 SSD. BTW, I did try both dd and unetbootin to the usb stick. Unetbootin now works for both the 32 & 64 bit version of Bodhi v.4, but using the dd command, as suggested in the prior post on this thread, did not work for me.
  11. TJMcK

    Installer not working...

    I appreciate all the feedback regarding this problem. Even though I have used Linux for about 10 years, I still only know the basic "need to know" commands -- dd isn't one of those. So it would be really helpful if a gui like unetbootin was supported. But, with that said, a detailed "howto install" with dd, in the Bodhi help, would go a long way for someone like me. With that said, thanks <-sef> for the "simple" dd command -- I will give it a try. And if that doesn't work, I'll either wait for v.4 beta2 or try installing the 32-bit v.4.
  12. TJMcK

    Installer not working...

    I briefly tried Bodhi v.3x and found it perfectly suitable for my needs. But I thought I would check out the newly released v.4x beta to see if it was stable enough to use regularly -- instead of having to reinstall/upgrade from v.3 later. I made the decision to install Bodhi on my USB stick using unetbootin. (My understanding is that Bodhi will no longer support unetbootin, but I had no problems... and it worked just as well as v.3) Bodhi v.4 beta worked fine using this live installation, so I made the decision to permanently install it on my USB3 SSD. BUT when I started the Bodhi installer, all I got was a dialog box saying that there was "no error message" and it gave me the path/filename of the instillation log -- however the log file does not exist. I have tried downloading todays version of v.4 beta and installing it again on my USB stick, but the installer has the same error message. Has anyone else had this problem?
  13. TJMcK

    Request: port of old E16 themes (like blue steel)

    Okay. Thanks. I will wait.
  14. TJMcK

    Request: port of old E16 themes (like blue steel)

    You could say that I'm a new user to Bodhi, although I think I used it for a while years ago (when it was e16)... But now that I'm planning to use Bodhi as a permanent distro for my laptop, one of the things that I would really like to do is, change it's theme. I have tried the two themes supplied with the v3x install... the "default" theme is too dark for my liking (and lacks contrast), while the MokshaRadiance is, in my opinion, too "normal" and lacks excitement. I have looked for different themes in the Bodhi repository, but there are none. Can I find themes anywhere else? Or will the themes that are being ported (as per this thread) be available soon?
  15. TJMcK

    installing Bodhi as an additional desktop

    Well I deleted all the files that were on my system to install enlightenment. Then I started over making sure there were no terminal errors in the process. I also installed the following file: 10.04: Add the package libxml2-dev -- which I thought might be the reason for my problem. Then I ran the script... with the same result: ERROR! The log for each of the packages is the same: ---------------------------- Running aclocal... Running autoheader... Running libtoolize... Running automake... configure.ac:131: installing `./compile' configure.ac:39: installing `./config.guess' configure.ac:39: installing `./config.sub' configure.ac:36: installing `./install-sh' configure.ac:42: required file `./ltmain.sh' not found configure.ac:36: installing `./missing' doc/Makefile.am:32: wildcard images/*.*: non-POSIX variable name doc/Makefile.am:32: (probably a GNU make extension) src/bin/Makefile.am: installing `./depcomp'
×