>The OpenBSD process is quite well understood. Use the best methods,
>doubt what you do, refractor. Simple in concept, but it takes a lot
>of time.
>Therefore I am looking forward to seeing what you and James can do.
>How long do you think it will take you? Can we expect to see working
>code
>> a security consideration, as far as I can see the bootloader loads using
INT
>> 13h calls. How can the kernel be sure it is really operating in ring 0 and
not
>> in some VM given that this is the case?
>Hey, it looks like you are just trying to be a dick.
On the assumption that you are not
>I guess in the absence of a seriously thought out wish list such a project
could be open ended. >The more care spent in hardware design choices I guess
the more likely we could avoid the mess >that various legacies have caused.
Here's a suggestion for a community that is base around the claim of
Hi,
a security consideration, as far as I can see the bootloader loads using INT
13h calls. How can the kernel be sure it is really operating in ring 0 and not
in some VM given that this is the case?
> Well there you go. Get to it. See you in 10 years.
Seriously, though. The thought must have crossed your mind at least once
during all these years of mopping up the mess that MS/Intel seem to have
concocted over the years.
I wonder what a hardware system designed by BSD bootloader, kernel
>Because the kernel cannot know what memory it should leave untouched,
>to use such BIOS functions.
Why not? I understand that there is some degree of variance amongst BIOS usage
of memory but the upper bounds seem to be clearly defined (if I am not
misinformed). And surely it would be possible
Hi,
forgive my ignorance and lack of knowledge on OS fundamentals. As my signature
suggests I am a complete beginner with 0x00 knowledge of the subject.
Regardless of that fact here comes my rather naive question:
Given that most OS mailing lists/forums seem to be dominated with hardware
>Please send dmesg and the output of:
>usbdevs -dv
>Both while the Huawei dongle is plugged into your machine, of course...
Would love to be able to do that. Anybody had any success mounting an OpenBSD
file system in linux?
0x00
and running? I need to
connect to the internet to do work on and I've had it with just about every
other OS there.
Daer Samej
From: Michael McConville <mm...@mykolab.com>
Sent: Saturday, December 19, 2015 6:43 PM
To: Read, James C
Cc: misc@openbsd.org
Subje
Hi,
I just installed 5.8, I know my dongle is detected and correctly switched to
the right mode because
a) I can see in dmesg output that the device is detected and labelled ugen0
b) I can see the led light continuously on the dongle, this only happens in
other environments I've used the dongle
>Unfortunately, without more information on YOUR dongle, (which would come
>from a dmesg, and/or usbdevs output), I can't give you any specific advice.
I'm having trouble mounting my OpenBSD file system under linux so can't get
the dmesg for you right now. But I remember the line started with
Hi,
my dmesg gives:
umsm0 at uhub0 port 1 configuration 1 interface 0 @HUAWEI HUAWEI Mobile@ rev
2.00/1.02 addr 2
my usbdevs -dv
uhub0
port 1 addr 2 : high speed, power 500 mA, config 1, HUAWEI Mobile
E303(0x1f01), HUAWEI Technologies(0x12d1), rev 1.02
cu /dev/cua00 gives
Connected to
>There was recently a good discussion about which WiFi dongles are
>reliably supported. I'd suggest finding cheap well-reviewed options
>online and searching their names on the list archives.
my dmesg gives:
umsm0 at uhub0 port 1 configuration 1 interface 0 @HUAWEI HUAWEI Mobile@ rev
2.00/1.02
>A full dmesg output, or at least an indication of what model the dongle is
>would be useful here.
Would love to be able to do that. Anybody had success mounting an OpenBSD
filesystem in linux?
0x00
Never seen this one before.
Just done a clean base install of 5.8
Got white lines of
-
-
flashing across my screen at urandom places.
Is this some kind of buffering problem?
0x00
>You've said that it connects as ugen, and also as umsm. Often the older
dongles provided >several serial interfaces, only one of which actually
worked. Again, nobody will be able to help >you without the log messages.
my dmesg gives:
umsm0 at uhub0 port 1 configuration 1 interface 0 @HUAWEI
>Please send dmesg and the output of:
>usbdevs -dv
>Both while the Huawei dongle is plugged into your machine, of course...
my dmesg gives:
umsm0 at uhub0 port 1 configuration 1 interface 0 @HUAWEI HUAWEI Mobile@ rev
2.00/1.02 addr 2
my usbdevs -dv
uhub0
port 1 addr 2 : high speed, power
Hi,
my device Huawei Mobile E353 is listed as known to be supported in the umsm
man 4 page
http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man4/umsm.4?query=umsm
=4
Does anybody know what the steps are to get a umsm supported device up and
running. We are talking basics here. I really
>> Read, James C wrote:
>> > I just installed 5.8, I know my dongle is detected and correctly
>> > switched to the right mode because
>> >
>> > a) I can see in dmesg output that the device is detected and
>> > labelled ugen0
>&
19 matches
Mail list logo
