Jump to content

Photo

Bodhi Linux 4.2.0 Relased


  • Please log in to reply
33 replies to this topic

#21 graywizardlinux

graywizardlinux

    Bodhi Supporter

  • Members
  • 1012 posts

Posted 01 June 2017 - 09:31 PM

Ok thanks - most appreciative.





A big thank you to everyone who contributes to Bodhi Linux


#22 Jayan Tashi

Jayan Tashi

    Member

  • Members
  • 63 posts
  • LocationSingapore

Posted 02 June 2017 - 04:11 AM

Probably have a look at 4.2.0 after this week, last week of the term hence there are several final assignments in the coursework. Should not be too different from 4.1.0 hence not in a terrible rush. :)


Son. Student. Citizen.


#23 cordx

cordx

    Member

  • Members
  • 15 posts
  • Locationsatx

Posted 03 June 2017 - 04:31 AM

graywizard:

sudo apt-get update
sudo apt-get upgrade

is all you need to update. eepdater should be able to handle it. Mr.J is simply trying to tell you that Jeff added swami-control panel to Bodhi 4.2 as an extra package.

 

If you want it you need to install it if you haven't already. It is not a needed package.

 

clean and easy :) thank you much



#24 birdmun

birdmun

    Member

  • Members
  • 317 posts
  • LocationWabash, IN

Posted 07 July 2017 - 04:56 AM

I have downloaded the 4.2 version and after burning it to a flash drive I tried booting to it. When the system booted it said I was running version 2.2 on e17. Looking at the Sourceforge page says the size is 745MB. When my system downloads it, it shows as 711MB. I am confused.



#25 Charles@Bodhi

Charles@Bodhi

    Old Faithful

  • Moderators
  • 4472 posts
  • LocationZeist, The Netherlands

Posted 07 July 2017 - 09:29 AM

I have downloaded the 4.2 version and after burning it to a flash drive I tried booting to it. When the system booted it said I was running version 2.2 on e17. Looking at the Sourceforge page says the size is 745MB. When my system downloads it, it shows as 711MB. I am confused.

 Confusion caused by vendorbytes (factor 1000) vs binary (factor 1024). 711 x 1024 x 1024 = 745,537,536.

 

From where did you get that info about 2.2 on e17? Never seen that before. Using the menu > About Operating System normally gives 4.2.0 for Bodhi and 0.2.1 for Moksha.

 

Enjoy,

Charles


Medion S4216 Ultrabook, 4GB RAM, 1TB HDD, WIN 10 & Bodhi 4.1.0-64 

Asus eeepc 901, 1GB RAM, 12 GB SSD, Bodhi 3.0.0-32-Legacy & Bodhi 4.1.0-32 Legacy


#26 birdmun

birdmun

    Member

  • Members
  • 317 posts
  • LocationWabash, IN

Posted 08 July 2017 - 04:13 PM

It really is 2.2 and e17. At least, that it's what the about bodhi sand about enlightenment (?) say. I have tried 3 different times to burn the ISO to the flash drive. The drive is either a SanDisk or a PNY. When the love image first boots, I have to choose a desktop style and background.

#27 Charles@Bodhi

Charles@Bodhi

    Old Faithful

  • Moderators
  • 4472 posts
  • LocationZeist, The Netherlands

Posted 08 July 2017 - 05:52 PM

It really is 2.2 and e17. At least, that it's what the about bodhi sand about enlightenment (?) say. I have tried 3 different times to burn the ISO to the flash drive. The drive is either a SanDisk or a PNY. When the love image first boots, I have to choose a desktop style and background.

Very strange behavior. 

From the live session of your flashdrive can you give

uname -pir
lsb_release -a

I just downloaded the 4.2.0-64 ISO (745 MB) from sourceforge and booted it in a virtual machine without those anomalies. 


Medion S4216 Ultrabook, 4GB RAM, 1TB HDD, WIN 10 & Bodhi 4.1.0-64 

Asus eeepc 901, 1GB RAM, 12 GB SSD, Bodhi 3.0.0-32-Legacy & Bodhi 4.1.0-32 Legacy


#28 birdmun

birdmun

    Member

  • Members
  • 317 posts
  • LocationWabash, IN

Posted 09 July 2017 - 01:58 AM

I am going to paraphrase the CLI responses. 4.10.0-2-generic x86_64 and then Ubuntu Bodhi Linux 2.0.0 12.04 precise. I have 4.1 iso files. I just figured I could save myself some updating if I could get the 4.2 iso working properly.



#29 Charles@Bodhi

Charles@Bodhi

    Old Faithful

  • Moderators
  • 4472 posts
  • LocationZeist, The Netherlands

Posted 09 July 2017 - 09:25 AM

Running the same live ISO I get:

bodhi@bodhi:~$ uname -pir

4.10.0-21-generic x86_64 x86_64
bodhi@bodhi:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Bodhi Linux
Release:	16.04
Codename:	xenial
bodhi@bodhi:~$

which is correct.

No idea why you get the 4.10 kernel and the precise lsb outcome.

 

Can you check the md5sum /sha256 of your download against the hashes for the 4.2.0-64 iso from sourceforge?

What method/program are you using to create the flashdrive?

 

And yes, having a 4.2 iso for installation saves you a lot of time in updating and some improvements provided by the updates will be built-in which will give a better first-experience.


Medion S4216 Ultrabook, 4GB RAM, 1TB HDD, WIN 10 & Bodhi 4.1.0-64 

Asus eeepc 901, 1GB RAM, 12 GB SSD, Bodhi 3.0.0-32-Legacy & Bodhi 4.1.0-32 Legacy


#30 birdmun

birdmun

    Member

  • Members
  • 317 posts
  • LocationWabash, IN

Posted 09 July 2017 - 10:06 AM

First up it seems I was a bit lazy in the kernel name it was 4.10.0-21 blah blah blah. I did check the md5sum against the md5 provided via sourceforge and they matched. I typed md5sum bodhi-4.2...iso and compared the md5 with what I downloaded from sourceforge. I have tried etcher(Arch seems to end up making the drive read only after that), I tried unetbootin in Debian and finally I tried dd if of bs4M ; sync.



#31 Charles@Bodhi

Charles@Bodhi

    Old Faithful

  • Moderators
  • 4472 posts
  • LocationZeist, The Netherlands

Posted 09 July 2017 - 10:26 AM

Do you have access to a windows machine? You could try rufus. Seems to be the best usb-creator around nowadays. It's a standalone app, just download and run, remove the download and there's nothing left.

I would format your flashdrive anyway, something faulty going on.

 

BTW, there is an option "check distro integrity" on the iso-boot-screen, have you tested it?


Medion S4216 Ultrabook, 4GB RAM, 1TB HDD, WIN 10 & Bodhi 4.1.0-64 

Asus eeepc 901, 1GB RAM, 12 GB SSD, Bodhi 3.0.0-32-Legacy & Bodhi 4.1.0-32 Legacy


#32 Charles@Bodhi

Charles@Bodhi

    Old Faithful

  • Moderators
  • 4472 posts
  • LocationZeist, The Netherlands

Posted 10 July 2017 - 01:30 PM



First up it seems I was a bit lazy in the kernel name it was 4.10.0-21 blah blah blah. I did check the md5sum against the md5 provided via sourceforge and they matched. I typed md5sum bodhi-4.2...iso and compared the md5 with what I downloaded from sourceforge. I have tried etcher(Arch seems to end up making the drive read only after that), I tried unetbootin in Debian and finally I tried dd if of bs4M ; sync.

 

Hmm, you could retry the dd command , but in a very simple form. The following is from the bodhibuilder program.

 

 

 

How to create a bootable USB from an ISO made by bodhibuilder:

    (you will need to determine which device your USB has been assigned,
    Do not copy & paste this command directly without changing '/dev/sdX',
    it won't work.     dd CAN be dangerous ... now you've been warned.)
sudo dd if=path/to/file.iso of=/dev/sdX

without BS and sync

 

 


Medion S4216 Ultrabook, 4GB RAM, 1TB HDD, WIN 10 & Bodhi 4.1.0-64 

Asus eeepc 901, 1GB RAM, 12 GB SSD, Bodhi 3.0.0-32-Legacy & Bodhi 4.1.0-32 Legacy


#33 birdmun

birdmun

    Member

  • Members
  • 317 posts
  • LocationWabash, IN

Posted 14 July 2017 - 04:57 PM

I am getting the sneaking suspicion that there is something wrong with the flash drive. Even after the simple dd command bodhi still boots and says it is 2.2. I fired up the iso in a VM and it booted as 4.2, so, the iso is just fine. I will grab a different flash drive and see how things go.



#34 birdmun

birdmun

    Member

  • Members
  • 317 posts
  • LocationWabash, IN

Posted 17 July 2017 - 11:32 AM

I finally got to a Windows machine and used Rufus. It required Syslinux 6.02(?) to put the iso on the drive properly. After burning it, I did try it to see if it worked. I was greeted with a 4.2 livecd running. It seems the other burning options fail with the Syslinux bit.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users