Re: [DNG] installer woe

[d_pridge]

 Original message From: KatolaZ  Date: 
6/26/18  8:03 AM  (GMT-06:00) To: dng@lists.dyne.org Subject: Re: [DNG] 
installer woe 
On Tue, Jun 26, 2018 at 02:47:17PM +0200, Alessandro Selli wrote:

[cut]

> >
> > It will boot the Purism installer from a USB stick if I use the same 
> > steps, starting wth the Purism ISO file, of course. 
> > 
> > So there is something else going on.
> 
>   If you didn't do it already, try to boot Purism from the same USB stick.
> 
>

guys, according to a previous email it seems it was just a broken usb
stick :)

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux 


The Chinese versions don't work well for supplying executable code, even though 
the check sum verifies correctly.  Dan.___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Fwd: Re: Unable to "Load missing firmware from removable media"

[d_pridge]

Sent from my MetroPCS 4G LTE Android Device
 Original message From: goli...@dyne.org Date: 5/11/18  5:53 PM 
 (GMT-06:00) To: dng@lists.dyne.org Subject: Re: [DNG] Fwd: Re: Unable to "Load 
missing firmware from removable
  media" 
>  From: fsmithred 
>  To: dng@lists.dyne.org
>  Sent: Friday, May 11, 2018 6:52 AM
>  Subject: Re: [DNG] Unable to "Load missing firmware from removable 
> media"
> 
> Which iso are you using, 
> 
> The firmware is in the installer isos, in /firmware. If you choose 
> expert
> install (graphical or not) and use a mirror, you will be asked if you 
> want
> non-free firmware or not. With a regular install or without a mirror, 
> the
> firmware will be installed automatically.
> 
> In the live isos, the firmware is already installed, and there's a 
> script
> to remove it if you don't want it. (Look in /root or /usr/local/bin/)
> 
> fsmithred
> ___
> 
> I'm using the netinst.iso for ASCII. (downloaded about 2-3 weeks ago)
> 

Hi Dan,

New isos with many improvements were uploaded just a few days ago for 
the release of the RC.  Try one of those to see if it's still happening.

golinux

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/minailman/listinfo/dng

__I will. However, it installs fine on my Lenovo.  Since 
the code cannot be distributed w/o legal repercussions from Broadcom, I doubt 
the fw is in the install pkg. But the install pkg has been made smart enough to 
tell the file names and where to get them and how to feed them to itself. What 
else can be done?   It's been a busy week. Learned a lot.___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

[DNG] Fwd: Re: Unable to "Load missing firmware from removable media"

[d_pridge]

 Original message Edited for size   From: fsmithred 

 To: dng@lists.dyne.org 
 Sent: Friday, May 11, 2018 6:52 AM
 Subject: Re: [DNG] Unable to "Load missing firmware from removable media"
   
On 05/10/2018 10:05 PM, dan pridgeon wrote:
> I'm trying to install ASCII on a Compaq presaria C700.According to the live 
> boot USB lspci, it has a Broadcom BCM4311 802.11 b/g WLAN [14e4"4311] rev 02 
> for the wireless adapter.  The install complains and ask for two files, the 
> names of which are duplicated for some reason: b43/ucode13.fw and 
> b43-open/ucode13.fw.  Using Gparted on this Refracta laptop, I recreated a 
> partition from scratch using all of the drive and formatting it to ext4 
> format. I then creatd the following structure in hopes of covering all the 
> bases:It contains:
> /ucode13.fw>/b43/ucode13.fw>/b43-open/ucode13.fw
> The installer message: "The missing files are:  b43/ucode13.fw and  
> b43-open/ucode13.fw"
> The permissions are set to 755 at all levels. 
> They are owned by root.


Dan,

Which iso are you using, 

The firmware is in the installer isos, in /firmware. If you choose expert
install (graphical or not) and use a mirror, you will be asked if you want
non-free firmware or not. With a regular install or without a mirror, the
firmware will be installed automatically.

In the live isos, the firmware is already installed, and there's a script
to remove it if you don't want it. (Look in /root or /usr/local/bin/)

fsmithred
___

I'm using the netinst.iso for ASCII. (downloaded about 2-3 weeks ago)  The 
lspci on tty2 allows me to see the hardware as noted above.  Due to licencing, 
the firmware file ( b43/ucode13.fw) cannot be freely distributed. The install 
software detects the correct hardware and presents the user with the correct 
filename(s?) which need to be placed on a removable media. A usb stick in my 
case.
 The 'tree' for the usb follows:
zenos@1stlinux:/media/mnt$ tree /media/mnt
/media/mnt
├── b43
│   └── ucode13.fw
├── b43-open
│   └── ucode13.fw
├── firmware
│   └── ucode13.fw
├── lib
│   ├── firmware
│   │   ├── b43
│   │   │   ├── a0g0bsinitvals5.fw
│   │   │   ├── a0g0bsinitvals9.fw
│   │   │   ├── a0g0initvals5.fw
│   │   │   ├── a0g0initvals9.fw
│   │   │   ├── a0g1bsinitvals13.fw
│   │   │   ├── a0g1bsinitvals5.fw
│   │   │   ├── a0g1bsinitvals9.fw
│   │   │   ├── a0g1initvals13.fw
│   │   │   ├── a0g1initvals5.fw
│   │   │   ├── a0g1initvals9.fw

│   │   │   ├── sslpn3initvals21.fw
│   │   │   ├── sslpn4bsinitvals22.fw
│   │   │   ├── sslpn4initvals22.fw
│   │   │   ├── ucode11.fw
│   │   │   ├── ucode13.fw
│   │   │   ├── ucode14.fw
│   │   │   ├── ucode15.fw
│   │   │   ├── ucode16_lp.fw
│   │   │   ├── ucode16_mimo.fw
│   │   │   ├── ucode16_sslpn.fw
│   │   │   ├── ucode16_sslpn_nobt.fw
│   │   │   ├── ucode17_mimo.fw
│   │   │   ├── ucode19_sslpn.fw
│   │   │   ├── ucode19_sslpn_nobt.fw
│   │   │   ├── ucode20_sslpn.fw
│   │   │   ├── ucode20_sslpn_nobt.fw
│   │   │   ├── ucode21_sslpn.fw
│   │   │   ├── ucode21_sslpn_nobt.fw
│   │   │   ├── ucode22_mimo.fw
│   │   │   ├── ucode22_sslpn.fw
│   │   │   ├── ucode24_lcn.fw
│   │   │   ├── ucode24_mimo.fw
│   │   │   ├── ucode25_lcn.fw
│   │   │   ├── ucode25_mimo.fw
│   │   │   ├── ucode26_mimo.fw
│   │   │   ├── ucode27_sslpn.fw
│   │   │   ├── ucode29_mimo.fw
│   │   │   ├── ucode30_mimo.fw
│   │   │   ├── ucode32_mimo.fw
│   │   │   ├── ucode33_lcn40.fw
│   │   │   ├── ucode5.fw
│   │   │   └── ucode9.fw
│   │   ├── b43-open
│   │   │   └── ucode13.fw
│   │   └── ucode13.fw
│   └── ucode13.fw
├── lost+found [error opening dir]
└── ucode13.fw

It still can't find it.
The error message reads as follows:"Direct firmware load for b43/ucode13.fw 
failed with error -2"and"Direct firmware load for b43-open/ucode13.fw failed 
with error -2"It then states: "Broadcom 43xx driver loaded [Features: PNLS]"
What would be the next move?Thank you.
P.S. -  I bought a d-link usb wireless adapter as a possible workaround for a 
situation like this. When plugged, it's vendor data can be seen in the dmesg 
output at the point of install failure, but the lspci does not see it. (I 
suspect a device driver problem.(?)   It was advertised as being supported by 
most Linux distros. (I had hoped the dd would be in the kernel, or included in 
the install).  I can't find a bios option to disable the builtin Broadcom 
adapter, so I think the install does not look any further for a wireless 
adapter beyond the first one it finds.  The livecd boots just fine and the 
lspci allows me to see the Broadcom hardware ok. But not the d-link usb 
adapter.  When plugged, dmesg shows the d-link data ok.


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Protect laptop from power supply voltage transients

[d_pridge]

Search for snap on ferrite beads.  You can add one at the computer end, or the 
brick end, or both.  You could also put one on the A.C. cord next to the brick 
to keep the noise from using the A.C. cord as an antenna.


Sent from my MetroPCS 4G LTE Android Device
 Original message From: Edward Bartolo  Date: 
3/25/18  1:03 PM  (GMT-06:00) To: dng  Subject: [DNG] 
Protect laptop from power supply voltage transients 
Dear All,

Sorry if this question is not related to software.

DNG is frequented by many people who manage computer as their bread
winning job. So, I am asking here.

Lately, I have experienced an amplifier input failure that was
supplied audio signals from a laptop powered with an AC mains power
supply. As you know, these AC power supplies are of the switching type
that use an inductance to transform voltage. The problem with these
power supplies is the fact that energising an inductance, also
energises parasitic inductances and capacitances that give rise to
transient interferences that may cause an external circuit to fail.

Has anyone used some sort of filtering circuit to protect their
laptop/s or computer/s?
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Does devuan install from USB really need a CDROM?

[d_pridge]

I'm having difficulty with ascot usb install. Retry has always found the cdrom. 
Because of other intermittent problems, I've switched to a better usb 3.0. (In 
a 2.0 port). Still seeing error scanning the first Mirrow. Will continue 
testing today.It works sometimes...  sorry for top posring.

Sent from my MetroPCS 4G LTE Android Device
 Original message From: KatolaZ  Date: 
3/19/18  4:59 AM  (GMT-06:00) To: dng@lists.dyne.org Subject: Re: [DNG] Does 
devuan install from USB really need a CDROM? 
On Mon, Mar 19, 2018 at 08:47:25PM +1100, Erik Christiansen wrote:

[cut]

> 
> Sounds like I should download ascii for a devuan which can find the
> CDROM on the USB. Just not tonight, as it's a bit late to start that
> now.
> 

Erik that's pretty strange. I did several Jessie installations from
USB sticks, and I don't remember of having had those issues. Anybody
else could confirm that?

HND

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[ "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[   @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[ @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]

___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] Happy New Year!

[d_pridge]

Sent from my MetroPCS 4G LTE Android Device
 Original message From: "Renaud (Ron) OLGIATI" 
 Date: 1/1/18  6:57 AM  (GMT-06:00) To: 
dng@lists.dyne.org Subject: Re: [DNG] Happy New Year! 
On Mon, 1 Jan 2018 13:50:51 +0100
aitor_czr  wrote:

> Without being too pedantic [*], *devuanita* is the right term. A 
> debianita is to debian, like a devuanita to devuan.

With due respect, your Worship, "Devuanita" would be a term of endearment for a 
young (female) Devuana...
 
Cheers,
 
Ron.

Me thinks Devuaneers is gender neutral...
-- 
    Hearts will never be practical
 until they can be made unbreakable.
 -- The Wizard of Oz
    
   -- http://www.olgiati-in-paraguay.org --
 
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] systemd-udevd: renamed network interface eth0 to eth1

[d_pridge]

Can you rename the files, instead, by adding _removed_by_rc.local.


Sent from my MetroPCS 4G LTE Android Device
 Original message From: Didier Kryn  Date: 
10/11/17  2:03 AM  (GMT-06:00) To: dng@lists.dyne.org Subject: Re: [DNG] 
systemd-udevd: renamed network interface eth0 to eth1 
Le 11/10/2017 à 08:10, Dr. Nikolaus Klepp a écrit :
> Am Mittwoch, 11. Oktober 2017 schrieb John Morris:
>> On Tue, 2017-10-10 at 01:49 +0200, Alessandro Selli wrote:
>>
>>>    By the manual, the correct solution in configuring Grub as to pass the
>>> kernel these parameters:
>>>
>>> biosdevname=0 net.ifnames=0
>> Those fix similar problems but not exactly the same ones.  The udev
>> persistent rules get you when you move an image from one machine to
>> another or swap out failed hardware and suddenly you have no network
>> because eth0 suddenly became eth1.  And as I noted, not only network
>> device names but CD drives as well are impacted.  The fixes you suggest
>> solve the equally annoying problem of eth0 or wlan0 unexpectedly turning
>> into a string of gibberish after an upgrade.
>>
>> They are turning everything into a UUID or similar string of untypable
>> gibberish.  It is almost like they don't want you to use the command
>> line directly anymore.  Nah, that couldn't be it, right?
>>
> My rc.local contains this line:
>
> rm /etc/udevd/rules/*persist*

 With this, Udev starts from scratch at every boot :-)

 Looks like a very nice approach, but it's too hidden: if you 
inherit a machine which is doing that, it can take you pretty long 
before you find out who the hell is deleting the udev rules. Maybe 
rewrite the files with only a comment like

# This file has been wiped out by /etc/rc.local because I don't want 
udev to rename my devices.

 Didier


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] noatime by default

[d_pridge]

Doesn't this affect the expected lifetime for an SSD?


Sent from my MetroPCS 4G LTE Android Device
 Original message From: John Franklin  Date: 
8/27/17  1:53 PM  (GMT-06:00) To: Alessandro Selli , 
dng@lists.dyne.org Subject: Re: [DNG] noatime by default 
On Sat, 2017-08-26 at 16:14 +0200, Alessandro Selli wrote:
> On Thu, 24 Aug 2017 at 01:03:10 +0200
> Adam Borowski  wrote:
> 
> > Hi!
> > I'd like to recommend another improvement: let's make the installer
> > default
> > to noatime for fstab it creates.
> 
> 
>  I agree.

I don't.  Adding noatime by default will break some software that
relies on atime, in particular mutt and popcon.  Keeping relatime is
sufficient.

https://blog.valerieaurora.org/2009/03/27/relatime-recap/

jf
-- 
John Franklin
frank...@tux.org
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] serial and ps2 ports.

[d_pridge]

The PC/XT used a clock/data protocol directly into an interrupt driven shift 
register which could handle 300 Kb+. The AT is microcoded and uses 
pseudo-RS-232 format  but with the bit windows timing relaxed to allow for for 
microcoding. The keyboard is dominate but the  buss direction can be reversed 
when the adapter pulls the clock line low and holds it.


Sent from my MetroPCS 4G LTE Android Device
 Original message From: k...@aspodata.se Date: 8/27/17  2:04 PM 
 (GMT-06:00) To: dng@lists.dyne.org Subject: Re: [DNG] serial and ps2 ports. 
Alessandro:
> On Sun, 27 Aug 2017 at 18:03:08 +0100
> Simon Hobson  wrote:
> [...]
> > AFAIK the underlying protocol for the keyboard is the same (or near enough
> > for simple conversion) between the two connector formats to allow for easy
> > conversion between plugs.
> 
>   They are, adaptors are purely mechanical.

PC/AT and PS/2 have the same protocol and electrical spec. except they 
have different connectors. The protocol is bidirectional.

PC/XT has the same pinout and connector as PC/AT but not the 
same protocol and they won't work together.
The protocol is keyboard -> pc only.

See page 16 of 
  http://kbdbabel.sourceforge.net/doc/kbdbabel-vortrag-vcfe80-20070429.pdf
and
 https://en.wikipedia.org/wiki/IBM_PC_keyboard
for details.

Regards,
/Karl Hammar

---
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57


___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Re: [DNG] systemd allows elevated access from unit files?

[d_pridge]

When was that option added?


Sent from my MetroPCS 4G LTE Android Device
 Original message From: Evilham  Date: 
7/3/17  11:03 AM  (GMT-06:00) To: dng@lists.dyne.org Subject: Re: [DNG] systemd 
allows elevated access from unit files? 
Am 03/07/2017 um 17:57 schrieb KatolaZ:
> On Mon, Jul 03, 2017 at 10:45:29AM -0500, dev wrote:
>> On 07/03/2017 10:40 AM, Evilham wrote:
>> 
>>
>>> That's the thing, we can do that :-) probably should, but the "right
>>> way" (from a standards point of view) would be to actually allow those
>>> names ^^ not to disallow them. So instead of modifying the way useradd
>>> works, the way adduser works should be fixed (so, shadow).
>>
>> That was easy ;) Seems to be a flag for that.
>>
>> # adduser 0day --force-badname
>> Allowing use of questionable username.
>> Adding user `0day' ...
>> Adding new group `0day' (1000) ...
>> Adding new user `0day' (1000) with group `0day' ...
>> Creating home directory `/home/0day' ...
>> Copying files from `/etc/skel' ...
>> Enter new UNIX password:
> 
> When you think to have found something totally wrong in unix, you most
> probably have not looked deep enough :)

Yeah, there's also some env var that can be set. My point was taht the
names are not allowed by default with some tools but with others they
are and they are OK according to the standard, and that makes it quirky.

Although I think it'd be better if they were allowed by default
(consistency + standard compliance), TBH I'd be totally ok with not
touching either adduser nor useradd; it's only an issue with disastrous
decisions somewhere else.
-- 
Evilham
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng