Re: kernel reordering and config -e

On Sun, Nov 19, 2017 at 10:19:05PM -0800, Paul B. Henson wrote: > On Mon, Nov 20, 2017 at 06:50:30AM +0100, Sebastien Marie wrote: > > > For me, there is currently no way to ask config(8) to alter the right > > file in /usr/share/relink/kernel to "ship" the modification in all > > future

Sierra Wireless MC7455 LTE cell network card

I'm trying to get the subject card to work under OpenBSD 6.2; it works fine under Linux so I know the card itself and its SIM etc are correctly configured and functional. The card is set to MBIM mode, and I'd like to use the umb driver rather than the umsm driver as not to have to muck with PPP.

Re: kernel reordering and config -e

On Mon, Nov 20, 2017 at 06:50:30AM +0100, Sebastien Marie wrote: > When it did that, it uses the object (I didn't recall the exact name) > with the previous mentioned array, with *default* configuration. So the > previous modification done with config(8) is cleared. Yeah, I figured that out

Re: kernel reordering and config -e

On Sun, Nov 19, 2017 at 07:31:20PM -0800, Paul B. Henson wrote: > I just updated a server to 6.2; unfortunately this box has an oddball > SOL com2 on irq10 so I need to run 'config -e' on the kernel to update > it and make the serial console work. I noticed afterwards in the boot > messages it was

kernel reordering and config -e

I just updated a server to 6.2; unfortunately this box has an oddball SOL com2 on irq10 so I need to run 'config -e' on the kernel to update it and make the serial console work. I noticed afterwards in the boot messages it was complaining about kernel reordering failures, and thinking I was fixing

Re: Not able to copy files to / from Android device

Venu Chakravorty writes: > > I can't see any files in "./mnt". I was expecting to see the files from the > Android device in "./mnt", but it is just empty. Please help. Is there any > other way (other than using "simple-mtpfs") to do this? > > Thanks in advance. If you

Re: The "like" factor

Yes, this may well be the problem: easier to understand if we speak of teddy bear, much harder if we speak of software upgrades! And yet, here we are... Sent from ProtonMail Mobile On Mon, Nov 20, 2017 at 02:17, wrote: > I wrote: > > In that case, I'd interpret the

Re: The "like" factor

LibreOffice has the *old* Microsoft Office GUI, which is what the users wanted. The change was introduced to help them keeping the old workflow with the old GUI while meeting the demands of automated software deployment, relevant ISO 27001/2 policies, and yes, get past the Microsoft licencing

RE: The "like" factor

I wrote: > > In that case, I'd interpret the beancounter's reponse as 'have to make > sacrifices, don't we? *sigh*'. I amend that. Isn't it just loss? We experienced techies try not to allow ourselves to get too attached to an environment, don't we? But hasn't there been a 'first time' this has

Re: The "like" factor

Muscle memory and shortcuts are certainly something we must look after, within reason. Microsoft itself has changed menu one time too many, to the point of having people complain for it and not wanting to use the new versions. As they now have a menu that is close to the original favourite, and

Re: Current #197 Nov 5 umb0 ucom0 umodem0 detached.

Ah right, the bug actually trigs below, so this is the XHCI_DEBUG log for the whole bug/failure sequence. Great. > Thanks for your answer. Sorry for the delay. > > In /cc to mpi@. > >> The first thing I see when looking at your report, is that your USB >> devices were plugged in via USB3

Re: The "like" factor

On Mon, 20 Nov 2017 00:40:38 +0100 wrote: > bytevolc...@safe-mail.net wrote: > > Perhaps it isn't just word/excel, but rather, getting used to the > > operating system changes and its antics. It appears you have changed > > their OS and their software, and this has upset them.

RE: The "like" factor

"Rupert Gallagher" wrote: > Well, people hated Microsoft's new GUIs, and wanted the old windows xp/7 > back, which we delivered. They are happy now, and so do we. > > They also hated the new GUI with the latest Office suite, so they kept using > the older version.

Re: The "like" factor

Well, people hated Microsoft's new GUIs, and wanted the old windows xp/7 back, which we delivered. They are happy now, and so do we. They also hated the new GUI with the latest Office suite, so they kept using the older version. LibreOffice has the Microsoft Office GUI, so they are happy now,

RE: The "like" factor

bytevolc...@safe-mail.net wrote: > > Think about this. You change the toolset they've been used to for > years, with something radically different. Whether or not you like it, > OpenOffice/Libreoffice/OpenBSD/Linux is radically different from a MS > Office/Windows setup. Now instead of coming to

RE: The "like" factor

"Daniel Wilkins" wrote: > Something to consider is that there *are* areas where libreoffice is > deficient. Yup. > > It's not uncommon for businesses to have a terrifying amount of embedded > visual > basic and incredibly elaborate excel macros, I wouldn't be surprised

Re: The "like" factor

Something to consider is that there *are* areas where libreoffice is deficient. It's not uncommon for businesses to have a terrifying amount of embedded visual basic and incredibly elaborate excel macros, I wouldn't be surprised if the (possibly theoretical) suit literally can't get their work

RE: The "like" factor

"Noah" wrote: > The software does mostly the same things, but you moved the menus and > buttons around. The pictures they recognize aren't there. Things work just > a little differently now. For some, it takes longer to do the things they > need to do. They have muscle

Re: SPOOFED: Re: The "like" factor

Perhaps it isn't just word/excel, but rather, getting used to the operating system changes and its antics. It appears you have changed their OS and their software, and this has upset them. No training was provided explaining to them the nooks and crannies of the new software, so they are

FU: RE: The "like" factor

I wrote: > windoze nt 5.2. I meant 6.0. Sorry, haven't been keeping track and M$ is, true to form, not making it easy by having obscured the number (and since having switched to outright *lying* about it). --schaafuit.

RE: The "like" factor

bytevolc...@safe-mail.net wrote: > Perhaps it isn't just word/excel, but rather, getting used to the > operating system changes and its antics. It appears you have changed > their OS and their software, and this has upset them. No training was > provided explaining to them the nooks and crannies

RE: The "like" factor

"Rupert Gallagher" rote: > We nerds are the other side of the problem, because we are apparently unable > to understand their problem. And even if we understand it, we often cannot offer a solution that satisfies them. > We have little simpathy for those who frown without

Re: The "like" factor

We nerds are the other side of the problem, because we are apparently unable to understand their problem. We have little simpathy for those who frown without evidence of an actual problem. Perhaps this is an example that humans still find it comfortable to "follow and go along together", like a

RE: The "like" factor

Hi, "Rupert Gallagher" wrote: > How did you solve the "like" factor? As I have no experience in office situations, I cannot answer that. However, it would've been an interesting experiment to just swap the logos and see how long it'd take for them to notice. #include

Re: Current #197 Nov 5 umb0 ucom0 umodem0 detached.

Thanks for your answer. Sorry for the delay. In /cc to mpi@. > The first thing I see when looking at your report, is that your USB > devices were plugged in via USB3 (XHCI). It is a m.2 card in a ThinkPad. Yes, as it looks, they use USB3 internal. > Please recompile your kernel with

Re: Not able to copy files to / from Android device

Le 11/19/17 à 22:21, Stuart Henderson a écrit : > On 2017-11-19, Venu Chakravorty wrote: >> Hello there, >> I am trying to copy files to / form my android device using "simple-mtpfs". >> However, I am not able to mount the file system of the Android device. On >> the phone,

Re: Not able to copy files to / from Android device

On 2017-11-19, Venu Chakravorty wrote: > Hello there, > I am trying to copy files to / form my android device using "simple-mtpfs". > However, I am not able to mount the file system of the Android device. On the > phone, the "Media Device (MTP)" check-box is checked. The

The "like" factor

I bet none of you dared this much in "change management". The accountant walks in to a new work-station. The initial excitement is followed by a quiet "no windows 10/7/xp? and a less quiet "no windows office?". That's right: new office politics, we are through with Microsoft, move on with your

Re: Not able to copy files to / from Android device

Hi, Venu First, see into this page, if your android device is recognized: http://cvsweb.openbsd.org/cgi-bin/cvsweb/~checkout~/src/sys/dev/usb/usbdevs If yes, after, you can attempt to use directly adb tool ;) => install adb Check if your device is really recognized: => adb devices If adb

Not able to copy files to / from Android device

Hello there, I am trying to copy files to / form my android device using "simple-mtpfs". However, I am not able to mount the file system of the Android device. On the phone, the "Media Device (MTP)" check-box is checked. The following is what I have tried: $ mkdir mnt $ simple-mtpfs -l

Re: Radeon discrete graphics issues

I knew the solution would be something simple, more than likely related to my inability to read properly :D Thanks for the pointers Jonathan, sorry it took a while for the point to stick. I guess the next natural question is, can I put my hardware to use helping develop support for this? I'm no

Re: Transition from machdep.lidsuspend to machdep.lidaction?

Thank you! :) So, the 6.0 -> 6.1 guide incorrectly refers to the sysctl setting as renamed, but at that point they actually do co-exist, and therefore both work until upgrade to 6.2. Maybe the 6.2 announcement/upgrade guide should have a list of settings that has actually been

Re: Radeon discrete graphics issues

There is kernel support for the initial GCN parts (CAPE VERDE, PITCAIRN, TAHITI) acceleration for those requires userland changes. The last generation with full acceleration is Northern Islands. On Sun, Nov 19, 2017 at 09:04:40AM +, Timothy Legge wrote: > So after re-reading man pages and a

mpd not opening port 8000 for streaming

Hi misc I have been trying to stream audio via mpd to my smartphone (with mpdroid) without success. I can't see the port 8000 open on netstat, port 6600 for remote control is working fine. I don't know if its related but vorbis encoder isn't working for me. mpd.log and mpd.conf

Re: Radeon discrete graphics issues

So after re-reading man pages and a quick consultation of some Wikipedia pages, kernel support for most Radeon cards upto those in the Northern Islands family are supported. That ties in nicely with what you've outlined as thats the family that came before they made the change to the GCN