Jump to content

sef

Member Since 11 Jan 2012
Offline Last Active Today, 01:28 AM
-----

#104411 installing bodhi on a gpt disk

Posted by sef on 19 May 2017 - 02:46 PM

I'm pretty sure both were the answer. It seems like "the chicken or the egg" question, but it really isn't.

 

If I remember correctly, Yumi doesn't create a UEFI bootable sector on your USB, so you never even had the chance to boot in UEFI with Yumi. (in this case 'dd' did the trick)

Therefore 'dd' created the option to boot to UEFI sector of the USB and enable the UEFI variables in the booted OS when you chose to boot 'UEFI (your usb manufacturer)'.

And as Charles stated earlier ...   :)  without UEFI variables in the OS, the installer (ubiquity) thought that it was a Legacy install, so that's the approach it took while creating partitions and installing.

 

Glad to hear you got it sorted. :)  Welcome to Bodhi!




#104356 installing bodhi on a gpt disk

Posted by sef on 16 May 2017 - 12:12 PM

Sounds good. Let us know how it goes.




#104335 installing bodhi on a gpt disk

Posted by sef on 15 May 2017 - 01:19 PM

If you create your USB using the linux tool 'dd' in the terminal, it will be bootable via either UEFI or Legacy mode. And I will re-iterate what Charles says that your BIOS must be set up to boot in UEFI mode.

 

Then when you boot your USB, if you see one option that says something like 'UEFI (your usb manufacturer)' choose to boot that, not the one that says something like '(your usb manufacturer)'.

 

At this time, the 'dd' method is the most reliable to create your bootable USB media. We can't guarantee any results from using a third party application like Unetbootin or anything else.

sudo dd if=/path/to/your.iso of=/dev/sdX

(where sdX is your USB device allocation)

Make sure you don't over-write your hard drive when using the 'dd' command. If you're not familiar with 'dd' please do some googling to learn more about it.




#103803 enable shutdown from Start menu

Posted by sef on 05 April 2017 - 03:09 PM

great but way beyond me.  i was wondering how to do this... i thought it was built into bodhi.

anyway that could be a part of it automatically????

 

You can add groups to newly created users by editing the following line in the file /etc/adduser.conf

#EXTRA_GROUPS="dialout cdrom floppy audio video plugdev users"

There are other options in that file as well.




#102903 Bodhi Linux 4.1.0 Pre-Release Discs

Posted by sef on 27 January 2017 - 02:21 PM

That sux! Well on the bright side at least the fix for syscongadget will be in! 

I must say though that I'm not noticing any other issues. Looks good.




#102793 Trouble with connecting to wifi network

Posted by sef on 20 January 2017 - 12:19 PM

The way I read it, I don't think he's experiencing droppage, I think the problem is that he can't connect at all. (???)

Basically, if you are having problems with encryption like alex_2017 mentions in his original post, try removing encryption temporarily on the wifi router to make it open. Then try to connect to it. If you can connect then try using WEP encryption. If that works, but WPA encryption does not, your card doesn't support WPA encryption so you'll have to use WEP if you want to continue using that wifi card in your PC. If you can't connect even on an OPEN ssid, I don't think the drivers for the card are working. Many older cards do not have WPA encryption support since it is a newer protocol than WEP.




#102632 Ongoing problem with date and time display

Posted by sef on 10 January 2017 - 03:28 AM

Not quite sure where you're at in the world of linux, but conky might be an option if you know (or are willing to learn) how to configure it.

 

I have created these files:

~/.conkyrc_top-bar-clock.conf

Spoiler

 

~/.conkyrc_top-bar-date.conf

Spoiler

 

I have my taskbar (etc) on the top of the screen rather than the bottom. (so that would explain why these config files would make conky appear toward the top) And I let these conky windows overlay my taskbar.

 

You can configure conky windows in many ways

- position on the screen

- font size

- content

- colors

- and so much more

 

If you were to save these files to your home directory, you could run these conky configuration files like this from the terminal to test them out

conky -c ~/.conkyrc_top-bar-date.conf &
conky -c ~/.conkyrc_top-bar-clock.conf &

It will take some determination if you're not used to conky, but it might be a good resolution for you since the font size is configurable as large as you want it.

Warning though, if you really get into conky, it can be a major black-hole for your time because of how fun it can be fine-tuning your conky windows.




#102244 Boot failure of fresh install after update with Dell mini 1012

Posted by sef on 21 December 2016 - 05:56 PM

To get rid of the boot splash screen you can change the file /etc/default/grub.

Replace this line

GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash"

with this

#GRUB_CMDLINE_LINUX_DEFAULT="quiet nosplash"
GRUB_CMDLINE_LINUX_DEFAULT=""

And then run from the command line

sudo update-grub2

That way, every time you boot, some helpful (or maybe not helpful) text will be displayed on the screen.

 

I have seen linux hang during boot when it couldn't mount a partition that /etc/fstab is looking for. In that case the text (behind the splash screen) will tell you to press some key like S to continue without mounting. (and that S or whatever letter is case sensitive so it might actually be <shift + S>)

 

 

Another thing you could try is to update each package manually one-by-one to see which is the culprit. After you do a 'sudo apt-get dist-upgrade' you will get a list of packages to be installed. Press N to skip upgrading, and instead update those packages one at a time, and reboot after each update. Kinda tedious I know, but it would be very very helpful if you have the time and patience. (this would be a last resort)

 

I would definitely start with removing the splash screen and checking out the messages.




#101467 Bodhi Install Link persist after install, it is intentional?

Posted by sef on 03 November 2016 - 05:30 PM

My intention was for it to be buried deep down in the settings where it wouldn't get any attention but instead it's popping up in the menu flyouts. I'll take care of it soon.


#101236 Old linux eploit still there...

Posted by sef on 24 October 2016 - 05:33 PM

Thanks for the heads-up!

Here's a reported fix:

https://www.digitalo...x-vulnerability


  • Kev likes this


#101164 Beta 3 can't install Broadcom wl driver - asks for Bodhi software disk

Posted by sef on 20 October 2016 - 12:17 PM

I googled a bit and found this (old) thread that mentions to comment out the line containing "cdrom" in file '/etc/apt/sources.list'.

 

EDIT:  removed ignorant / unobservant content.




#101084 Bodhi 4.0.0 AppPack Software Inclusions

Posted by sef on 14 October 2016 - 04:11 PM

Would it be possible or even viable to create a script and present it with a desktop icon that can run the dd command to help users create a live usb for bodhi ?

 

I could create a script that would give a suggestion for a command, but dd is much too dangerous for my liking to create a script that will just plow forward and start outputting 1's & 0's to a location. (Even then, I wouldn't feel right about that either unless I slathered it with disclaimers everywhere stating that I'm not responsible for any loss of data.) I can't see a way to make a script that is completely airtight to the point where no-one will ever lose data using it. That's why it has to be done by somebody who is sitting at the keyboard making their own decisions.




#101051 Installer not working...

Posted by sef on 13 October 2016 - 11:21 AM

I used dd to get the beta after verifying that md5sum matches even from sourceforge. However, I wind up with busybox and/or syslinux. Tried a different USB stick, and used lilli (Linux LiveUSB creator, an old reliable, but since Bodhi 4 beta is not really included in their list of supported ISOs, a warning about "Will use parameters similar to Bodhi 2.1" to burn the ISO and add persistence (while formatting the drive to fat32). When I booted the USB stick grub fails to find a working isolinux.exe

 

I was waiting for more reports about problems with the beta ISO. At this point I will probably donate to get the official Bodhi-USB- stick-on-a -lanyard. But without unetbootin, and dd giving questionable results, my options to get the beta are less than stellar. I was hoping to be the proud owner of a Bodhi 4 laptop, but it looks like it will have to wait (till winter?)

 

What am I missing? Are all the devs running Bodhi in a vm? Should I even brush up on remastersys when the old staples cannot or refuse to work?

I don't want to change this thread from the original topic about the installer, but, a few things quickly, or not so quickly...  (if we want to talk about ISO creation methods or anything else, we should start another topic)

 

Going forward, remastersys won't work in 16.04. Syslinux has changed just enough so that remastersys won't be able to get it right without some tweaks. And we've tweaked bodhibuilder to get syslinux, among other things, right with 16.04.

 

Also, we've worked out how to get ISOs created so that they will be bootable in the majority of UEFI PC's and (I would venture to say) all recent non-UEFI/legacy-BIOS PC's of a standard CPU architecture. And the recommended way to make that ISO bootable on a PC is to simply dd it to a USB. That's not to say that there won't be some hiccups along the way, but most of the problems will be with some "non-standard" UEFI in a PC or an oddball USB stick that does something funky with its first sectors of the drive. Very often too, the problem is in the UEFI (what most people mistakenly call BIOS) settings.

As a side note, when I want to buy a PC, and I can't get good info on the internet about whether Linux will work on it or not, I create a bootable USB and bring it with me to the store -- boot up the USB and play around a bit.

 

Also, importantly, the 32-bit Bodhi will not boot on a UEFI machine at this time when UEFI mode is enabled.

And note that ARM is not supported at this time either.

 

Most simply for dd --

dd if=/path/to/your/flavor/bodhi-4.iso of=/dev/sdX

* (Where sdX is your usb stick. Notice there is no number at the end -- that would be sdXN. And there will not be any persistence with this method of USB creation, it's simply to get Bodhi booting on your PC.)

 

If anybody wants more support about why their ISO won't boot, it would be very helpful to know the machine you're booting to, the bootable media creation method and which ISO you're using.

But like I said already -- in a new topic.  :)




#101049 WIFI

Posted by sef on 13 October 2016 - 10:21 AM

How do I do that line thing? Ispci -nn/grep 0280?

Also, if you have trouble with getting commands to work, you can always copy and paste from the post that is trying to help you out. We try very hard to get commands exactly right when posting to help someone.  :) (As you can see from Charles' and The waiter's posts!)




#100409 Two distros

Posted by sef on 29 August 2016 - 02:45 PM

If you have enough disk space, yes.

I would suggest to create your desired free space and partition on your hard drive before attempting to install Bodhi. Just my personal preference, I'm less likely to screw it up that way.