EmSee-2nd-Edition | Ultra | 2016

For talk and support relating specifically to Puppy derivatives
Message
Author
stemsee

#121 Post by stemsee »

I put mine on a dual partition usb stick partition 1 is fat32 and 2 is ext 4
Works great, I do not copy to ram my boot is

Code: Select all

kernel /vmlinuz pmedia=usbhd pfix=fsck,nocopy
Download is working fine here!

Jwm with rox for icon management custom Nicons software. Openbox is also available. XFCE, KDE .sfs modules easily added.

regards stemsee

toomanyquestions
Posts: 85
Joined: Wed 09 Jan 2013, 01:27

#122 Post by toomanyquestions »

No ram - and it's still pretty quick? Can you place the bootloader in fat32 and then boot to ext4 (the 2nd partition)? I've never tried it,,,
stemsee wrote:I put mine on a dual partition usb stick partition 1 is fat32 and 2 is ext 4
Works great, I do not copy to ram my boot is

Code: Select all

kernel /vmlinuz pmedia=usbhd pfix=fsck,nocopy
Download is working fine here!

Jwm with rox for icon management custom Nicons software. Openbox is also available. XFCE, KDE .sfs modules easily added.

regards stemsee

gcmartin

#123 Post by gcmartin »

Is the current distro a hybrid ISO?

User avatar
ETP
Posts: 1193
Joined: Tue 19 Oct 2010, 19:55
Location: UK

#124 Post by ETP »

Hi stemsee,

I have no wish to give you a persecution complex but must take you to task again. :)
I put mine on a dual partition usb stick partition 1 is fat32 and 2 is ext 4
Works great, I do not copy to ram my boot is
Code:
kernel /vmlinuz pmedia=usbhd pfix=fsck,nocopy
1. Unless it is a cunning ploy of some kind that surely should be pmedia=usbflash

2. If your kernel supports f2fs & you have f2fs-tools installed, f2fs on 2 would give better performance.

3. If f2fs is not an option then non-journaled ext4 is the next best bet.
To disable journaling you can use (where XN points to your partition letter and digit):

Code: Select all

tune2fs -O ^has_journal /dev/sdXN
4. "nocopy" - Unless you are very short of RAM you may as well use it as it will just sit there feeling sorry for itself.

Anyway depending on your age it is either:

A) (Young) - Detention and/or no lashings of extra custard from matron.

B) (Old) - Temporary confiscation of your bus pass.
:lol: :lol: :lol:

EDIT - Footnote:

pmedia=usbhd can come in handy when dealing with full installs to the 2nd partition on a USB stick.
Depending on the kernel something like,

APPEND root=/dev/sdc2 rootwait rw

may suffice but will result in kernel panic "init not found" with other kernels. In which case;

APPEND root=/dev/sdc2 pmedia=usbhd rootwait rw

will boot OK.

With a normal install to a partition on an SSD pmedia=ataflash comes in handy as it allows a load
from the SSD but with PupSaveConfig the option to save or not at the end of the session.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]

stemsee

#125 Post by stemsee »

Hi ETP

usbhd seems to be the selection made by grub4dos when detecting a usb-3.0 256mb/s sand disk extreme (fastest usb 3 stick). For lesser sticks usbflash will sufice.

Nocopy, because copying a 3gb file to ram takes quite a lot of time, especially when, as i do, I often reboot to test things out (new kernels, new main sfs, menu, modules to load, daemons loading at start up). I am sure my usage is not typical, and I am happy you take the time to offer solid advise!

Cheers!
stemsee

cinclus_cinclus
Posts: 68
Joined: Sun 22 Feb 2009, 10:00

#126 Post by cinclus_cinclus »

gcmartin wrote:Is the current distro a hybrid ISO?
I tried it by dd'ing the ISO-file to a an USB flash-drive.
But it was not bootable, so to answer your question it's not a hybrid ISO.

So I copied the content of the ISO-file to the FAT32 formatted USB flash-drive, renamed isolinux.cfg to syslinux.cfg and installed syslinux - worked.

But ... - please see next post.

cinclus_cinclus
Posts: 68
Joined: Sun 22 Feb 2009, 10:00

EmSee Ultra: no support for Intel NIC I218-V?

#127 Post by cinclus_cinclus »

My current hardware uses an Intel NIC I218-V.
I can't find a module suitable for the I218-V, the e1000e:

Code: Select all

> modprobe e1000e
But there is no such module in Ultra.
@stemsee. Could you please provide us with such a module?

Correction: there can't be a ndiswrapper module for the I218-V, because it 's not a wireless-card.

s243a
Posts: 2580
Joined: Tue 02 Sep 2014, 04:48
Contact:

Re: EmSee Ultra: no support for Intel NIC I218-V?

#128 Post by s243a »

cinclus_cinclus wrote:My current hardware uses an Intel NIC I218-V.
I can't find a module suitable for the I218-V, the e1000e:

Code: Select all

> modprobe e1000e
But there is no such module in Ultra.
@stemsee. Could you please provide us with such a module?

Correction: there can't be a ndiswrapper module for the I218-V, because it 's not a wireless-card.
You could try building it. An example of how to build a kernel module can be found in 666philb's post here:

http://murga-linux.com/puppy/viewtopic. ... start=1140

or if you wanted it built-in instead here is an example:
http://web.archive.org/web/201012220433 ... net/?p=184

or download the drivers from one of these sites:
http://www.intel.com/content/www/us/en/ ... 05480.html
https://sourceforge.net/projects/e1000/ ... %20stable/

and follow whatever instructions are given.

cinclus_cinclus
Posts: 68
Joined: Sun 22 Feb 2009, 10:00

#129 Post by cinclus_cinclus »

@s243a Thanks for your comment.
Just didn't expect that stemsee 'hid' all modules in kernel-modules.sfs.
Nevertheless I didn't yet manage to configure the network ...

starhawk
Posts: 4906
Joined: Mon 22 Nov 2010, 06:04
Location: Everybody knows this is nowhere...

#130 Post by starhawk »

Although I refuse to use any Pup too portly for CD-R/RW media, this information suggests that ndiswrapper may be an option --
Although ndiswrapper is intended for wireless network cards, other devices are known to work: e.g., ethernet cards, USB to serial port device, home phone network device etc.
Source.

Good luck!

stemsee

#131 Post by stemsee »

Try installing this new kernel, it definetely has e1000e module
Download this huge kernel package to ~/Downloads
https://drive.google.com/file/d/0B_gaN1 ... sp=sharing

then copy this script to path make executable and run in term

Code: Select all

newkern
That should install it for you.
Attachments
newkern.gz
Fake .gz rename to newkern and copy to /usr/local/bin and make executable
(1.7 KiB) Downloaded 166 times

stemsee

#132 Post by stemsee »

Ok so I found that kdenlive has a problem, and kodi isn't starting, also the theme is old. So, I have fixed these issues and added newer rt kernels. The next iso update will offer quad booting (triple kernels and hdd)

1) 32bit nopae i486 kernel
2) 32bit pae i686
3) 64bit
4) boot local HDD

kdenlive installed from apt-get 400mb download!
audacity 2.1.2 on wine! Too much hassle compiling for linux (wxWidgets)
kodi Isengard 5.2 (update)(couldn't get Jarvis working)
Google Chrome update Version 48.0.2564.109
Sardu back in on wine
Scribus 1.5.1
rmsfsadd rightclick menu (for adding sfs info to installed packages so ppm can uninstall it later if mastered in).
rmsfs-del right-click remove files from system if found in target sfs module.
iso2frugal cli tool.
kia update (Keep Internet Alive, for those of us who use btinternet wifi and the like.)
newkern - download huge kernel package to ~/Downloads/ and this will install it for you and backup previous kernels and modules. More specifically for updating three kernels on EmSee distros! This will require a super huge kernel package at some point for full benefit.
Attachments
capture1198.jpg
(41.74 KiB) Downloaded 535 times

stemsee

#133 Post by stemsee »

boot menu
Attachments
capture12199.jpg
(26.56 KiB) Downloaded 499 times

stemsee

#134 Post by stemsee »

Also updated vlc 2.1.6 to 2.2.1, but on wine. Te only problem having it on wine seems to be using it as defaultmediaplayer the path gets messed up and looks like this

Code: Select all

/root//mnt/sda5/Audio/some.mp3
Which it cannot find. Maybe only a problem when selecting files on other partition but could be resolved through links in root!

I have also tidied up the dead links in right click sendto menus. And a new bug which caused geany to open all *.desktop files in ~/.config/autostart which is supposed to replace Startup.

Also cleaned up some residue.

I found that introducing the i486 kernel does not introduce an additional set of kernel modules (at first I added them as adrv_*.sfs) but of course they use the same modules created by the pae compile!

stemsee

#135 Post by stemsee »

Finally, on startup of X the default style of layout for icons is 'corners' ... however this does not take into account the screen resolution of the machine being booted on, which is likely differnt from the machine that it was original remastered on which has a screen of 1366 X 768 . Solution add 'nicons corners' command to nicons script and Startup/star so corners is re-initialised for given screen! Downside is a few more flickers as startup.

Question "At what point in the boot up process is it possible for the operating system to become aware of the hardware screen resolution?"

stemsee

#136 Post by stemsee »

Actually I revised the code in Nicons and now only one flicker as corners is reconfigured for given screen!

Had to reconfigure alsa for jack-loop and loop-back for alsa devices, which means more inputs 'n' outputs available to system and jack audio interface. Had to install additional packages and reinstall others after too good a clean up.

Cinelerra updated.

rmsfs and iso2frugal reworked and checked for cli and rightclick menu.

cpu-freq set to powersave.

Created and modified several .desktop files (wine stuff mostly)

SARDU ready to go on sdb1

Changed HOST name to METONYM

DogRadio 0.6 modified by Fredx181 for EmSee-Ultra and other non DD pups (many thanx).

I really enjoyed getting this polished these few days. Some may think that wheezy is dated, but very usable! Enjoy it!

There is a bit more kde here than I would have liked, which means adding full kde will be a small step for anyone who wants to add it. Openbox is there too of course.

Il Pazzo ;-)

user=root
passwd=ultrawoof

EmSee-Ultra-2016.iso i486 i686 x64 kernels boots on any machine! (needs confirmation!)

md5
https://drive.google.com/file/d/0B_gaN1 ... 3I2QmRYazg
Attachments
EmSee-Ultra-2016-downloadlink.txt.gz
fake gz
(61 Bytes) Downloaded 268 times

stemsee

#137 Post by stemsee »

I have discovered two errors with this iso.
g
Use ISOmaster to fix the issues as follows

1) The isolinux.cfg append lines need 'pfix=nocopy' otherwise only 64bit boots and sees modules.

2) adrv_EmSee-Ultra.sfs modules fr i486 are necessary after all. Get them from here and add to the iso.

https://drive.google.com/file/d/0B_gaN1 ... 0I5WjliZzA

Sorry!

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#138 Post by step »

stemsee wrote: 2) adrv_EmSee-Ultra.sfs modules fr i486 are necessary after all. Get them from here and add to the iso.

https://drive.google.com/file/d/0B_gaN1 ... 0I5WjliZzA
I'm confused. The link you posted downloads an x86_64 labelled archive, yet you refer to modules for i486. Is it the right link? Can you also elaborate on which archive files are to be added and how? Your reference to adrv_EmSee-Ultra.sfs confused me. Thanks.
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

stemsee

#139 Post by stemsee »

hi
correct link to huge-4.4.1-EmSeei486.tar.bz2
https://drive.google.com/file/d/0B_gaN1 ... HUxUW5PR3c
1) unpack package
2) rename kernel-modules.sfs-4.4.12-EmSeei486 to adrv_EmSee-Ultra.sfs
3) copy to root of iso using isomaster
4) burn iso to optical medium

EDIT: don't forget to edit isolinux.cfg and add pfix=nocopy to 'append' line

step
Posts: 1349
Joined: Fri 04 May 2012, 11:20

#140 Post by step »

Thanks. I was able to edit the ISO and boot it in qemu. I tried all three kernels. Keyboard input is fine, but mouse input in qemu isn't working at all. Specifically, the qemu VM can't grab the mouse pointer. In other words, the mouse pointer inside the VM stays fixed, while the host mouse pointer in blocked access to the VM window. Any ideas what's going on?
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]

Post Reply