Porteus Nemesis v3.5 BUG REPORTS

Arch based Porteus community project
Post Reply
aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#76 by aus9 » 13 Jan 2016, 06:05

possible bug or maybe pacman or maybe I am impatient?

I can't get abs to download let alone run

https://forum.porteus.org/viewtopic.php ... 952#p40952

User avatar
Ed_P
Contributor
Contributor
Posts: 3072
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#77 by Ed_P » 13 Jan 2016, 06:31

aus9 wrote: is this the same hardware where I suggested you needed firmware and that firmware was missing?
If so, did you download and install that firmware from either of my previous links?
Actually I did. iwlwifi-7265D-15.ucode
aus9 wrote:a possible solution is here
https://forum.manjaro.org/index.php?topic=26219.0
I just don't know what to do with it. I boot from the ISO and rebuilding the drivers in it is more than a little beyond me. So I was hoping for...
aus9 wrote:but hopefully brokenman will offer better long term solution?
Ed

aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#78 by aus9 » 13 Jan 2016, 07:21

Ed_P

ok booting up with cd but surely you can insert an USB stick and edit your boot cheat code to say something about
changes=/dev/sdb depending on whether you have one internal drive.

personally I think putting usb on a stick with a number of menu items is the way to go but I am not sure if this is that funny flashmedia PC or not

2) so you have manually injected one firmware into /usr/lib/firmware? did you make a typo?
iwlwifi-7265D-15.ucode

I thought it was

Code: Select all

[    7.478325] iwlwifi 0000:02:00.0: request for firmware file 'iwlwifi-7265D-13.ucode' failed
and my old link is to *-13
https://github.com/OpenELEC/iwlwifi-fir ... 5-13.ucode
but I have clicked on raw to save you one click so download is (hopefully)
https://github.com/OpenELEC/iwlwifi-fir ... 5-13.ucode

tuxfriend
White ninja
White ninja
Posts: 6
Joined: 09 Jan 2016, 01:48
Distribution: Linux Mint
Location: Germany

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#79 by tuxfriend » 13 Jan 2016, 11:09

After visiting GMX, my email provider's website due to them putting your emails in the spam suspicion category (you don't see this in thunderbird), I was able to activate my account here on porteus.

Ok, now to the nerdy stuff: The Nemesis KDE ISO is corrupted because I can't get it going, even after dding the ISO to an USB stick. So I installed KDE5 on top of the LXDE ISO because I wanted brightness to work on my portable devices (not working in LXDE and XFCE). So far KDE5 works (entry in /etc/lxdm/lxdm.conf: /usr/bin/startkde). Localizing is possible when you use the localizing script in /usr/local/bin, unpack the 001-core.xzm first (xzm2dir), then the 4 files created with localizing script and then create a new 001-core module with dir2xzm.
Unfortunately MIME doesn't work: if you click on a file in dolphin, you are asked what program should open that file. Something must be missing there.

Nemesis is still a work in progress but it is quite usable (e.g. with Chromium, LibreOffice).

Here's hoping I can contribute to this project a bit more in future. Sorry for my command of English. It's only a secondary language to my native one.

User avatar
ncmprhnsbl
Full of knowledge
Full of knowledge
Posts: 796
Joined: 20 Mar 2012, 03:42
Distribution: 3.2.2-64bit xfce/openbox
Location: australia
Contact:

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#80 by ncmprhnsbl » 13 Jan 2016, 11:42

aus9 wrote: I can't get abs to download let alone run
i suppose since arch "stable" = manjaro testing, abs (sources) might not always be compatible, therefore not included in the repo...
a workaround might be to temporarily point pacman at an arch mirror...
tuxfriend wrote:Unfortunately MIME doesn't work: if you click on a file in dolphin, you are asked what program should open that file. Something must be missing there.
Welcome tuxfriend!
try running update-cache as root in terminal (/usr/local/sbin/update-cache)
this updates mime and some caches and saves them to a .xzm module in /tmp
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

User avatar
francois
Contributor
Contributor
Posts: 4905
Joined: 28 Dec 2010, 14:25
Distribution: kde xfce porteus manjaro kubun
Location: Enfin l'été, le changement climatique attendu: le soleil.

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#81 by francois » 13 Jan 2016, 12:07

@aus:
abs is not supported with manjaro:
https://forum.manjaro.org/index.php?topic=188.0

In manjaro, there are some additional stock programs that have been adopted from AUR. However, you use loose some functionalities. Personally, I like the gui package manager octopi (instead of pamac) which offers to include yaourt or pacaur.

However, I don't know if octopi could be implemented on top of brokenman's wrapper.
Voltaire: Le mieux est l'ennemi du bien.

aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#82 by aus9 » 13 Jan 2016, 13:57

Hi regarding abs

I posted a link to my abs post....I have posted there how I got a pkgbuild so I agree with Francois its no longer bug as its expected not to have abs on Manjaro servers.

thanks for the heads up.

User avatar
Ed_P
Contributor
Contributor
Posts: 3072
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#83 by Ed_P » 13 Jan 2016, 18:47

aus9 wrote:ok booting up with cd but surely you can insert an USB stick and edit your boot cheat code to say something about
changes=/dev/sdb depending on whether you have one internal drive.
I am not booting from cd I am booting from ISO files, on my USB drive. And to the best of my knowledge the changes= cheatcode is not working in PN 3.5.
personally I think putting usb on a stick with a number of menu items is the way to go but I am not sure if this is that funny flashmedia PC or not
The HP is not a flashmedia PC, it's a 13.3" notebook.
2) so you have manually injected one firmware into /usr/lib/firmware?
No, because I thought I would have to reboot for it to be implemented and with changes= not working....
did you make a typo?
iwlwifi-7265D-15.ucode
No. Your https://forum.manjaro.org/index.php?topic=26219.0 link took me to posting https://forum.manjaro.org/index.php?top ... #msg222796 at the bottom of the thread which linked to the newer version which I thought would be preferred.

So, does the changes= cheatcode work in PN3.5? And if so how do I install the .ucode file? Is there some driver install command?

-edit-

Interesting.

Code: Select all

guest ~ $ ls /usr/lib/firmware/*.ucode
/usr/lib/firmware/iwlwifi-100-5.ucode
/usr/lib/firmware/iwlwifi-1000-5.ucode
/usr/lib/firmware/iwlwifi-105-6.ucode
/usr/lib/firmware/iwlwifi-135-6.ucode
/usr/lib/firmware/iwlwifi-2000-6.ucode
/usr/lib/firmware/iwlwifi-2030-6.ucode
/usr/lib/firmware/iwlwifi-3160-12.ucode
/usr/lib/firmware/iwlwifi-3945-2.ucode
/usr/lib/firmware/iwlwifi-4965-2.ucode
/usr/lib/firmware/iwlwifi-5000-5.ucode
/usr/lib/firmware/iwlwifi-5150-2.ucode
/usr/lib/firmware/iwlwifi-6000-4.ucode
/usr/lib/firmware/iwlwifi-6000g2a-5.ucode
/usr/lib/firmware/iwlwifi-6000g2b-6.ucode
/usr/lib/firmware/iwlwifi-6050-5.ucode
/usr/lib/firmware/iwlwifi-7260-12.ucode
/usr/lib/firmware/iwlwifi-7265-12.ucode
/usr/lib/firmware/iwlwifi-7265D-12.ucode
There are already iwlwifi drivers in PN3.5!! A 7265D one even. So, will the -15 one that I downloaded work or do I indeed need the -13 version??

-edit-

As you noted:
aus9 wrote:I thought it was

Code: Select all

[    7.478325] iwlwifi 0000:02:00.0: request for firmware file 'iwlwifi-7265D-13.ucode' failed
It looks like I need a *D-13 file not a
*-13 file.

Now to checkout out the changes= cheatcode.

-edit-

O M G What a joke. :x

So, I created a save.dat file, formatted as ext4, moved it to the USB flash drive, and changed the grub2 menu to add it to the boot parms. :good:

Code: Select all

guest ~ $ dd if=/dev/zero of=/tmp/newsave.dat bs=1024 count=320000
320000+0 records in
320000+0 records out
327680000 bytes (328 MB) copied, 0.406546 s, 806 MB/s
guest ~ $ mkfs.ext4 /tmp/newsave.dat
mke2fs 1.42.13 (17-May-2015)
Discarding device blocks: done                            
Creating filesystem with 320000 1k blocks and 80000 inodes
Filesystem UUID: 6b82a982-1467-416d-9630-d0d6fea1cd2c
Superblock backups stored on blocks: 
	8193, 24577, 40961, 57345, 73729, 204801, 221185

Allocating group tables: done                            
Writing inode tables: done                            
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done 

guest ~ $ cp /tmp/newsave.dat /mnt/sdb1/porteus3.x/
I booted with the new save.dat file and copied it to the /usr/lib/firmware/ directory. Had some difficulty doing it. cp in terminal mode failed so I used the file manager to copy it. It failed also but the err msg at least told me why. Retired the cp command prefixed with sudo and a ls after words showed it worked. The new D-15 entry was green for some reason whereas the others were the normal white. :unknown: Rebooted.

Code: Select all

guest ~ $ cp /mnt/sdb1/porteus3.x/iwlwifi-7265D-15.ucode /usr/lib/firmware/
cp: cannot create regular file ‘/usr/lib/firmware/iwlwifi-7265D-15.ucode’: File exists
guest ~ $ ls /usr/lib/firmware/iwlwifi*.ucode
/usr/lib/firmware/iwlwifi-100-5.ucode
/usr/lib/firmware/iwlwifi-1000-5.ucode
/usr/lib/firmware/iwlwifi-105-6.ucode
/usr/lib/firmware/iwlwifi-135-6.ucode
/usr/lib/firmware/iwlwifi-2000-6.ucode
/usr/lib/firmware/iwlwifi-2030-6.ucode
/usr/lib/firmware/iwlwifi-3160-12.ucode
/usr/lib/firmware/iwlwifi-3945-2.ucode
/usr/lib/firmware/iwlwifi-4965-2.ucode
/usr/lib/firmware/iwlwifi-5000-5.ucode
/usr/lib/firmware/iwlwifi-5150-2.ucode
/usr/lib/firmware/iwlwifi-6000-4.ucode
/usr/lib/firmware/iwlwifi-6000g2a-5.ucode
/usr/lib/firmware/iwlwifi-6000g2b-6.ucode
/usr/lib/firmware/iwlwifi-6050-5.ucode
/usr/lib/firmware/iwlwifi-7260-12.ucode
/usr/lib/firmware/iwlwifi-7265-12.ucode
/usr/lib/firmware/iwlwifi-7265D-12.ucode
guest ~ $ 
guest ~ $ sudo cp /mnt/sdb1/porteus3.x/iwlwifi-7265D-15.ucode /usr/lib/firmware/ 
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

[sudo] password for guest: 
guest ~ $ ls /usr/lib/firmware/iwlwifi*.ucode/usr/lib/firmware/iwlwifi-100-5.ucode
/usr/lib/firmware/iwlwifi-1000-5.ucode
/usr/lib/firmware/iwlwifi-105-6.ucode
/usr/lib/firmware/iwlwifi-135-6.ucode
/usr/lib/firmware/iwlwifi-2000-6.ucode
/usr/lib/firmware/iwlwifi-2030-6.ucode
/usr/lib/firmware/iwlwifi-3160-12.ucode
/usr/lib/firmware/iwlwifi-3945-2.ucode
/usr/lib/firmware/iwlwifi-4965-2.ucode
/usr/lib/firmware/iwlwifi-5000-5.ucode
/usr/lib/firmware/iwlwifi-5150-2.ucode
/usr/lib/firmware/iwlwifi-6000-4.ucode
/usr/lib/firmware/iwlwifi-6000g2a-5.ucode
/usr/lib/firmware/iwlwifi-6000g2b-6.ucode
/usr/lib/firmware/iwlwifi-6050-5.ucode
/usr/lib/firmware/iwlwifi-7260-12.ucode
/usr/lib/firmware/iwlwifi-7265-12.ucode
/usr/lib/firmware/iwlwifi-7265D-12.ucode
/usr/lib/firmware/iwlwifi-7265D-15.ucode
guest ~ $ 
The reboot showed the new driver in the /usr/lib/firmware/ directory. Saving changes works!! :good:

But no network connection. But right clicking on the network manager applet icon shows Wi-Fi Connections, unfortunately as Disabled. Clicked on the Enable Wi-Fi option but the icon still shows it as being Disabled. repeated this a couple of times and suddenly I see my WiFi connections!! :Yahoo!:

I reboot to see if the WiFi connection would automatically connect. It doesn't. :( Repeat the Enable WiFi, check the icon, many more times than I did the first time. Eventually WiFi connections, again. :good:

Ok, time to update my posting. 8)

Oops!! NO BROWSER. :wall: :wall: :wall:

Maybe I will wait for 3.6. :evil:
Ed

aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#84 by aus9 » 13 Jan 2016, 23:12

Ed_P

good to read you agreee that changes= cheatcode works in 3.5.

I am still confused on why my earlier copy and paste of your output for "request for firmware file 'iwlwifi-7265D-13.ucode' failed" has led you to install a iwlwifi-7265D-15.ucode firmware?

2) if in a terminal it shows as green, normally that means its got exectuable power.
You can confirm that by running

Code: Select all

ls -al /usr/lib/firmware/iwlwifi-7265D*

User avatar
Ed_P
Contributor
Contributor
Posts: 3072
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#85 by Ed_P » 14 Jan 2016, 03:46

aus9 wrote:I am still confused on why my earlier copy and paste of your output for "request for firmware file 'iwlwifi-7265D-13.ucode' failed" has led you to install a iwlwifi-7265D-15.ucode firmware?
Well, for two reasons.

1. I read all the postings in the link you posted to the manjaro forum and toward the bottom there were 2 postings.
and the post that followed.
a whamo-blamo, a...whamo...blamo

Yes sir Captain - there be wales here
which means the driver worked.

2. The name of the iwlwifi driver I used matches the name of one of the iwlwifi error msgs I posted earlier.
http://forum.porteus.org/viewtopic.php?f=137&t=5382&start=60#p40920 wrote:

Code: Select all

guest ~ $ dmesg | grep error
[    6.750443] hp_accel: probe of HPQ6007:00 failed with error -22
[    6.757226] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.8.10-fw-1.10.3.11.e.bseq failed with error -2
[    6.757276] bluetooth hci0: Direct firmware load for intel/ibt-hw-37.8.bseq failed with error -2
[    6.833337] i915 0000:00:02.0: Direct firmware load for i915/skl_dmc_ver1.bin failed with error -2
[    7.000796] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-17.ucode failed with error -2
[    7.000851] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-16.ucode failed with error -2

[    7.000898] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-15.ucode failed with error -2

[    7.000947] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-14.ucode failed with error -2
[    7.000993] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-13.ucode failed with error -2

There is no firmware error msg that matches the driver you keep linking to. All the drivers listed have a 5D- in them, the driver in your links does not.

Clearer now? :roll:
Ed

aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#86 by aus9 » 14 Jan 2016, 06:24

Ed_P

Yes I gave you a link without the D grrrr.

lets reveal your output again and if you don't agree with me, maybe brokenman can review your postings?

Code: Select all

dmesg
(snip)
[    7.478129] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-17.ucode failed with error -2
[    7.478184] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-16.ucode failed with error -2
[    7.478230] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-15.ucode failed with error -2
[    7.478274] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-14.ucode failed with error -2
[    7.478322] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-13.ucode failed with error -2
[    7.478325] iwlwifi 0000:02:00.0: request for firmware file 'iwlwifi-7265D-13.ucode' failed.
[    7.478326] iwlwifi 0000:02:00.0: no suitable firmware found!
I have focussed on this part of the output
request for firmware file 'iwlwifi-7265D-13.ucode' failed
I provided 2 links in the past....the first post that you just alluded to has a posting discussing
iwlwifi-7265D-15.ucode

but I claim your error shows you need
iwlwifi-7265D-13.ucode

My earlier reply sent you a link to the wrong firmware grrrr

but new link is to
https://github.com/OpenELEC/iwlwifi-fir ... D-13.ucode
see I can read ;)

direct download is
https://github.com/OpenELEC/iwlwifi-fir ... D-13.ucode

#######################################
Ed

since we know you still don't have wl working, do a me a favour and try my new download
and see if dmesg improves
if dmesg still shows no suitable firmware found....I will forgo beer for one day

I am crossing my fingers we have it correct

User avatar
Ed_P
Contributor
Contributor
Posts: 3072
Joined: 06 Feb 2013, 22:12
Distribution: Cinnamon 3.2.2 64-bit ISO
Location: Western NY, USA

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#87 by Ed_P » 14 Jan 2016, 18:32

aus9 wrote:Yes I gave you a link without the D grrrr.

Code: Select all

(snip)
[    7.478322] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-7265D-13.ucode failed with error -2
[    7.478325] iwlwifi 0000:02:00.0: request for firmware file 'iwlwifi-7265D-13.ucode' failed.
[    7.478326] iwlwifi 0000:02:00.0: no suitable firmware found!
I have focussed on this part of the output
request for firmware file 'iwlwifi-7265D-13.ucode' failed
:lol: Wow, we both need better glasses. I honestly didn't notice the difference in the wording of that msg from the others.
since we know you still don't have wl working,
It works, not as smoothly as one would expect but functional none the less, and the experience taught me how easy it is to add drivers to the system. So, it's all good.

Now go have a beer. :beer:
Ed

aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#88 by aus9 » 14 Jan 2016, 22:38

Ed_P so that is your new log?
so I was wrong on the "13" firmware?
Beer is sacrificed

Jack
Contributor
Contributor
Posts: 1063
Joined: 09 Aug 2013, 14:25
Distribution: Porteus 3.2.rc5 Mate 64 bit
Location: Marysville, OHIO USA

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#89 by Jack » 14 Jan 2016, 23:14

I wish I could help out but I don't know the first thing what is going on here. All I know is if it works that great but if it don't ask then ask questions. I feel like a dummy here.
I just like Slackware because I think it teach you about Linux to build packages where Ubuntu is like Windows you just install programs you want.

aus9

Re: Porteus Nemesis v3.5 BUG REPORTS

Post#90 by aus9 » 14 Jan 2016, 23:23

Jack

Just using Nemesis is fine, no-one is expecting you to report any bugs unless you think there is one.

Post Reply