On 25 May 17:22 Marco van Hulten wrote:
> On 25 May 13:50 Marco van Hulten wrote:
> > I have a Dell Latitude E7470 with the latest OpenBSD snapshot. It
> > boots fine when not connected to a docking station. When I connect
> > it to a DELL E-Port II (Model No: PR03X) docking station, it
> > crash
Hello, responding to my own post,
On 25 May 13:50 Marco van Hulten wrote:
> I have a Dell Latitude E7470 with the latest OpenBSD snapshot. It
> boots fine when not connected to a docking station. When I connect it
> to a DELL E-Port II (Model No: PR03X) docking station, it crashes with
> the fol
Hello—
I have a Dell Latitude E7470 with the latest OpenBSD snapshot. It
boots fine when not connected to a docking station. When I connect it
to a DELL E-Port II (Model No: PR03X) docking station, it crashes with
the following kernel error:
error: [drm:pid8048:i915_gem_init_hw] *ERROR* Failed
I now have an XVR-100 and have set it up as the output device in
OpenBoot, but I have another problem. I have compiled a kernel from
current source with DEBUG and DRMDEBUG for some more info, maybe
someone knows how to fix this.
Without the debug options, the last thing I see is "BIOS signature
in
On Sun, Mar 11, 2018 at 11:46:54AM +1100, Jonathan Gray wrote:
>
> radeon cards from sun with fcode
>
> xvr-100 (0x1002:0x5159 pci rv100)
> xvr-300 (0x1002:0x5b64 pcie rv380)
>
I have heard of people changing the PCI option ROM in their Radeon
cards to work on Suns, but only for e.g. the Radeon
s, etc.
>
> My problem is that with the GPU connected, the system hangs completely
> and is unresponsive to breaks in the serial line or any form of
> input. I do not have a Sun keyboard, only a USB keyboard connected to
> a PCI USB card (which works with no problem).
>
> Th
Hello
I have a sparc64 machine with no real graphics card, only the onboard
Mach64 framebuffer. I found an ATI Radeon 9200 and decided to see if
it works, then I could run X, test some graphical ports, etc.
My problem is that with the GPU connected, the system hangs completely
and is
Hello,
I might have found the problem from my previous post.
In the dmesg I had thisinteldrm0 at vga1
drm0 at inteldrm0
error: [drm:pid0:i915_write32] *ERROR* Unknown unclaimed register before
writing to 10
inteldrm0: 1280x720
I could hardly boot my system before but since I have disabled drm
Hello,
I just did a fresh install with OpenBSD 5.8 and an ASUS motherboard Z97-P
The installation went fine but then from the first boot it hangs at "setting
tty flags" this is just after the partitions are fsck'edI searched on search
engines and found that people running Openbsd as a VM disable
Von: joshua stein -- Gesendet: 2015.05.29 - 19:00
> It is probably not the whole system hanging, but X with the VESA
> driver seems to have some trouble exiting cleanly so you just get a
> hung X server that won't respond to switching back to the console
> (or allow XDM to respawn X).
>
Hi, I am experiencing regular hangups (display freezes, switching to console
not possible, does not respond to power button) when exiting X on a brandnew
Lenovo X1 Carbon Gen. 3 (Type 20BB).
I can reproduce this behaviour on freshly installed systems (5.7 and
-snapshot): Start fvwm (XDM or star
Sender: owner-m...@openbsd.org
On-Behalf-Of: s...@spacehopper.org
Subject: Re: System Hangs with Intel i7 3920XM
Message-Id:
Recipient: adam.atkin...@damovo.com
Received: from Mail2.damovo.com (109.204.121.44)
by UK001B237.d.grp (10.8.1.9) with Microsoft SMTP Server (TLS) id
14.2.318.4
On 2014-06-21, Gustav Fransson Nyvell wrote:
> Well, I've had 3 total freezes since I installed OpenBSD recently. This
> is on a laptop and I can't suspend by closing the screen even, that it
> will just black the screen. Everything is frozen, sound is stuck at
Do you use apmd? If so, try with
On 06/21/14 20:02, Dimitris Papastamos wrote:
If you have any means of hooking up a serial cable (docking station?)
you might be able to see the ddb prompt and go from there.
Does the freeze happen instantly or does it slowly become unresponsive?
For the latter you might have time to switch to a
Dimitris Papastamos [s...@2f30.org] wrote:
> If you have any means of hooking up a serial cable (docking station?)
> you might be able to see the ddb prompt and go from there.
>
He should be getting a ddb prompt even within X with inteldrm.
> Does the freeze happen instantly or does it slowly be
If you have any means of hooking up a serial cable (docking station?)
you might be able to see the ddb prompt and go from there.
Does the freeze happen instantly or does it slowly become unresponsive?
For the latter you might have time to switch to a VT and wait for ddb.
You can force a crash dump
On 06/21/14 19:55, Dimitris Papastamos wrote:
On Sat, Jun 21, 2014 at 07:35:22PM +0200, Gustav Fransson Nyvell wrote:
I want to ask 1) Is there something I can do? 2) Is there some logging I can
enable that will dump stuff useful for reading after a hang? 3) Is this a
kernel driver/module/someth
On Sat, Jun 21, 2014 at 07:35:22PM +0200, Gustav Fransson Nyvell wrote:
> I want to ask 1) Is there something I can do? 2) Is there some logging I can
> enable that will dump stuff useful for reading after a hang? 3) Is this a
> kernel driver/module/something problem or caused by an application?
>
Hi,
I found something about this before, something old, would like to hear
if there's some update.
Well, I've had 3 total freezes since I installed OpenBSD recently. This
is on a laptop and I can't suspend by closing the screen even, that it
will just black the screen. Everything is frozen,
Em 21-12-2013 21:52, Adam Jensen escreveu:
> On 12/20/2013 09:05 AM, Giancarlo Razzolini wrote:
>> Em 19-12-2013 17:56, Adam Jensen escreveu:
>>> I've been using a KVM switch (USB keyboard and mouse) on a couple of
>>> machines recently and I noticed that when the Keyboard, Video, and
>>> Mouse con
On 12/20/2013 09:05 AM, Giancarlo Razzolini wrote:
Em 19-12-2013 17:56, Adam Jensen escreveu:
I've been using a KVM switch (USB keyboard and mouse) on a couple of
machines recently and I noticed that when the Keyboard, Video, and
Mouse connections are switched away from the OpenBSD machine, a US
Em 19-12-2013 17:56, Adam Jensen escreveu:
> I've been using a KVM switch (USB keyboard and mouse) on a couple of
> machines recently and I noticed that when the Keyboard, Video, and
> Mouse connections are switched away from the OpenBSD machine, a USB
> disconnect is reported (as expected). When s
I've been using a KVM switch (USB keyboard and mouse) on a couple of
machines recently and I noticed that when the Keyboard, Video, and Mouse
connections are switched away from the OpenBSD machine, a USB disconnect
is reported (as expected). When switched back, the keyboard and mouse
are not re
On 2012-05-09, [B&G-Consulting] Elmar Bschorer
wrote:
> Hi list,
>
> I do a backup of a remote system by running rsync over ssh. The backup is
> stored as tgz. Both systems running OBSD 5.0. For convinience I rsync the
> whole system to keep the backup script very simple in crontab. The remote
>
Hi list,
I do a backup of a remote system by running rsync over ssh. The backup is
stored as tgz. Both systems running OBSD 5.0. For convinience I rsync the
whole system to keep the backup script very simple in crontab. The remote
system uses about 17.8G.
Once in a while the remote systems hangs
On Sat, Sep 04, 2010 at 09:40:30AM +0200, Guillermo Bernaldo de Quiros Maraver
wrote:
> I've been seeing in these last days as OpenBSD hangs (I can not use the
> mouse or the keyboard and I can not return to the console) I ask here
> because I want to know if anyone has had a similar problem and i
I've been seeing in these last days as OpenBSD hangs (I can not use the
mouse or the keyboard and I can not return to the console) I ask here
because I want to know if anyone has had a similar problem and if so, as it
has resolved.
Thanks for all.
Greetings.
Guillermo Bernaldo e Quirss Maraver
Th
On Mon, 26 Jul 2010 12:23:36 +0200
Paul de Weerd wrote:
> On Mon, Jul 26, 2010 at 12:04:04PM +0200, frantisek holop wrote:
> | but regardless of that, i think leaving old garbage
> | after newfs-ing a partition is not a good idea in
> | any case and it's one of those things i wouldn't
> | except
I'm top posting because I think people have read enough.
My sudo policy only allows me to test this;
$ /usr/bin/sudo /sbin/mount_msdos -o
nodev,nosuid,noexec /dev/sd0c /mnt/usb0
and I get
mount_msdos: /dev/sd0c on /mnt/usb0: Inappropriate file type or format
So I see no problem and Being abl
> On Mon, Jul 26, 2010 at 12:21:53PM -0600, Theo de Raadt wrote:
> > There is no readlabelfs() for NFS filesystems. You are being too
> > specific in saying how it works.
>
> In the case of an NFS filesystem, mount(8) just checks whether the
> "special" string contains a ":" or "@" character. So
On Mon, Jul 26, 2010 at 12:21:53PM -0600, Theo de Raadt wrote:
> There is no readlabelfs() for NFS filesystems. You are being too
> specific in saying how it works.
In the case of an NFS filesystem, mount(8) just checks whether the
"special" string contains a ":" or "@" character. So, the diff i
On Mon, Jul 26, 2010 at 10:07:37AM -0600, Theo de Raadt wrote:
> This diff isn't quite right. There are no disklabels on NFS
> partitions; heck, there's no true disklabel on a MSDOS-only memory
> stick. The language you've written is too specific.
How about the following?
--- sbin/mount/mount.
> On Mon, Jul 26, 2010 at 10:07:37AM -0600, Theo de Raadt wrote:
> > This diff isn't quite right. There are no disklabels on NFS
> > partitions; heck, there's no true disklabel on a MSDOS-only memory
> > stick. The language you've written is too specific.
>
> How about the following?
>
>
> ---
> On Sun, Jul 25, 2010 at 09:48:23PM -0400, Kenneth R Westerback wrote:
> > If you wanted to mount according to the partition type number, DON'T
> > USE '-t '. We give you the option to OVERRIDE the partition
> > type number and you made use of that override. You have taken command
>
> I believe t
On Sun, Jul 25, 2010 at 09:48:23PM -0400, Kenneth R Westerback wrote:
> If you wanted to mount according to the partition type number, DON'T
> USE '-t '. We give you the option to OVERRIDE the partition
> type number and you made use of that override. You have taken command
I believe that this thr
From: "STeve Andre'"
> Date: 2010-07-25 23:22:39
>
> I think that is a fundamentally flawed assumption. Root can do
> *ANYTHING*. Anything at all. Sure, preventing crashes is good,
> but you can't get around the fact that root is omniscient.
frantisek holop wrote:
hi there,
i have just managed to "mount" an ffs partition
as msdos. the the system promptly dies.
$ sudo fdisk sd0
Disk: sd0 geometry: 120/255/63 [1935360 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C
On Mon, Jul 26, 2010 at 3:50 AM, frantisek holop wrote:
> so sending half-baked crappy diffs will estabilish one
> as a useful, non-whining member of the community, right?
>
>
Oh...you're on the paid support plan? My bad.
You get OpenBSD for free. That's pretty amazing, isn't it? Why is it ha
frantisek holop wrote:
> my "whining", is a comparison of experiences with others,
> questions if someone can reproduce a particular problem
> i am having, whether it is considered a problem at all,
> and so on. a practice i thought about as the first step
> of bug reporting and as such a perfectl
On Mon, 26 Jul 2010, frantisek holop wrote:
since my first email, i see what i did wrong...
that was the point of writing to the mail list
in the first place, to see if i was doing something
silly. turns out i was. does that warrant abuse?
of course it does, i am not new here.
i also see, th
On Mon, Jul 26, 2010 at 12:04:04PM +0200, frantisek holop wrote:
| but regardless of that, i think leaving old garbage
| after newfs-ing a partition is not a good idea in
| any case and it's one of those things i wouldn't
| except either. my mistake again.
Different filesystems use different part
since my first email, i see what i did wrong...
that was the point of writing to the mail list
in the first place, to see if i was doing something
silly. turns out i was. does that warrant abuse?
of course it does, i am not new here.
i also see, that now this problem became simply
a "should we
On Mon, 26 Jul 2010, frantisek holop wrote:
hmm, on Mon, Jul 26, 2010 at 12:12:32AM +0200, David Vasek said that
It is not what happened. The -t msdos was forced by you. But you
ah shit. you are right :]
and it worked because ffs does not overwrite the beginning
of the partition.
i misinte
hmm, on Sun, Jul 25, 2010 at 09:41:15PM -0500, J Sisson said that
> On Sun, Jul 25, 2010 at 8:01 PM, frantisek holop wrote:
>
> > well done misc@, living up to your name.
> > the bootcamp of the internet.
> >
> >
> It's better to create a crappy diff that gets rejected than whine
> incessantly on
bofh wrote:
> Ok, when I first learnt how to use unix nearly 20 years ago, one of
> the things I learnt was that a privileged user can break shit, but
> should not cause kernels to hang or crash. That would be considered a
> bug. Only DOS and windows 3.1 do that :)
Unfortunately it's not that bl
frantisek holop wrote:
> to know the road ahead, ask those coming back.
You mean the ones who like it so much they travel it twice?
On Sun, Jul 25, 2010 at 8:01 PM, frantisek holop wrote:
> well done misc@, living up to your name.
> the bootcamp of the internet.
>
>
It's better to create a crappy diff that gets rejected than whine
incessantly on a mailing
list that by your own admission has a reputation for being like boot ca
On Sun, Jul 25, 2010 at 10:46:50PM +0200, frantisek holop wrote:
> hmm, on Sun, Jul 25, 2010 at 02:29:25PM -0600, Theo de Raadt said that
> > > i think it doesnt matter what the user is, this shouldnt
> > > be happening.
> >
> > We make the source code available, and yet noone here has even sat do
> hmm, on Sun, Jul 25, 2010 at 08:10:32PM -0400, Tony Abernethy said that
> > Foreign file systems NEVER get prime attention.
>
> that's the kind of thinking that comes from redmond.
You have no right to speak.
> > When you do stupid things the results are rather predictable
> > and you compound
hmm, on Sun, Jul 25, 2010 at 08:10:32PM -0400, Tony Abernethy said that
> Foreign file systems NEVER get prime attention.
that's the kind of thinking that comes from redmond.
> When you do stupid things the results are rather predictable
> and you compound your error by trying to blame everybody
STeve Andre' [and...@msu.edu] wrote:
> I think that is a fundamentally flawed assumption. Root can do
> *ANYTHING*. Anything at all. Sure, preventing crashes is good,
> but you can't get around the fact that root is omniscient.
>
Had this 'root' been *omniscient*, the incident wouldn't have
ha
I think that is a fundamentally flawed assumption. Root can do
*ANYTHING*. Anything at all. Sure, preventing crashes is good,
but you can't get around the fact that root is omniscient.
On Sunday 25 July 2010 19:16:05 bofh wrote:
> Ok, when I first learnt how to use unix nearly 20 years ago, one
frantisek holop wrote:
> the borderline between the useful and useless error checking
> is sometimes a bit fuzzy i think.
Not THAT fuzzy.
Foreign file systems NEVER get prime attention.
When you do stupid things the results are rather predictable
and you compound your error by trying to blame eve
On Sun, Jul 25, 2010 at 11:29 AM, Robert wrote:
> I haven't tried this mount, but IMHO if you mount some garbage as a
> specific file system type, then the OS should give you an error and
> deny the mount. It should not crash.
> Maybe you are mounting through a script, for automated backups, or
>
hmm, on Sun, Jul 25, 2010 at 04:33:27PM -0700, Philip Guenther said that
> What does that get us? They can still fuck up ld.so or libc, and
> poof, most the programs on the system will crash when started!
> Overwrite /etc/passwd with /dev/random and rename /bin and your system
> will stop being us
On Sun, Jul 25, 2010 at 4:16 PM, bofh wrote:
> Ok, when I first learnt how to use unix nearly 20 years ago, one of
> the things I learnt was that a privileged user can break shit, but
> should not cause kernels to hang or crash. That would be considered a
> bug. Only DOS and windows 3.1 do that
Ok, when I first learnt how to use unix nearly 20 years ago, one of
the things I learnt was that a privileged user can break shit, but
should not cause kernels to hang or crash. That would be considered a
bug. Only DOS and windows 3.1 do that :)
On 7/25/10, STeve Andre' wrote:
> On Sunday 25 Ju
On Sunday 25 July 2010 18:40:19 frantisek holop wrote:
> hmm, on Mon, Jul 26, 2010 at 12:12:32AM +0200, David Vasek said that
>
> > It is not what happened. The -t msdos was forced by you. But you
>
> ah shit. you are right :]
>
> and it worked because ffs does not overwrite the beginning
> of the
hmm, on Mon, Jul 26, 2010 at 12:12:32AM +0200, David Vasek said that
> It is not what happened. The -t msdos was forced by you. But you
ah shit. you are right :]
and it worked because ffs does not overwrite the beginning
of the partition.
i misinterpreted what happened,
but this is still a prob
Theo de Raadt wrote:
Thanks for telling me do so some reading, but a google of your name
on these mailing lists will show a 10 year pattern of you not being
able to self-help. Something to do with your parents, probably.
'this hammer *sucks* for putting screws in the wall! what's the deal
On Sun, 25 Jul 2010, frantisek holop wrote:
hmm, on Sun, Jul 25, 2010 at 02:29:25PM -0600, Theo de Raadt said that
i think it doesnt matter what the user is, this shouldnt
be happening.
We make the source code available, and yet noone here has even sat down
for 30 seconds and gone and checked
> hmm, on Sun, Jul 25, 2010 at 03:17:53PM -0600, Theo de Raadt said that
> > ffs does not use the first 8K of a partition.
> >
> > You used to have MSDOS on there.
>
> yes, that is the correct answer.
>
>
> it's a pitty the kernel is ignoring the partition type id.
>
> it's also a pitty that f
hmm, on Sun, Jul 25, 2010 at 03:17:53PM -0600, Theo de Raadt said that
> ffs does not use the first 8K of a partition.
>
> You used to have MSDOS on there.
yes, that is the correct answer.
it's a pitty the kernel is ignoring the partition type id.
it's also a pitty that ffs apparently leaves t
On Sun, Jul 25, 2010 at 4:46 PM, frantisek holop wrote:
> does that almost nothing include the partition type number?
> because i dont see why would the kernel msdos mount code
> even try to start mounting an msdos filesystem with type of A6.
You are more likely to see things if you look for them
>hmm, on Sun, Jul 25, 2010 at 02:29:25PM -0600, Theo de Raadt said that
>> > i think it doesnt matter what the user is, this shouldnt
>> > be happening.
>>
>> We make the source code available, and yet noone here has even sat down
>> for 30 seconds and gone and checked the kernel msdos mount code
hmm, on Sun, Jul 25, 2010 at 02:29:25PM -0600, Theo de Raadt said that
> > i think it doesnt matter what the user is, this shouldnt
> > be happening.
>
> We make the source code available, and yet noone here has even sat down
> for 30 seconds and gone and checked the kernel msdos mount code and re
> hmm, on Sun, Jul 25, 2010 at 01:08:45PM -0600, Theo de Raadt said that
> > > >
> > > >
> > >
> > > That's no excuse. The point here is that any unprivileged user can hang
> > > the system at will.
> >
> > I don't see an unprivleged user.
> >
> > I see root performing the mount, since only roo
hmm, on Sun, Jul 25, 2010 at 01:08:45PM -0600, Theo de Raadt said that
> > >
> > >
> >
> > That's no excuse. The point here is that any unprivileged user can hang
> > the system at will.
>
> I don't see an unprivleged user.
>
> I see root performing the mount, since only root can perform mounts
hmm, on Sun, Jul 25, 2010 at 12:02:25PM -0500, Chris Bennett said that
> If I plug my 110volt computer into a 220volt socket, it will
> promptly die too!
>
> Why on earth would you even try to do this?
actually, it was a typo... nothing dramatic,
no fuzzy testing of mount, a simple typo.
and i
> >> i have just managed to "mount" an ffs partition
> >> as msdos. the the system promptly dies.
> >>
> >> $ sudo fdisk sd0
> >> Disk: sd0 geometry: 120/255/63 [1935360 Sectors]
> >> Offset: 0 Signature: 0xAA55
> >> Starting Ending LBA Info:
> >> #: id
Chris Bennett escribis:
frantisek holop wrote:
hi there,
i have just managed to "mount" an ffs partition
as msdos. the the system promptly dies.
$ sudo fdisk sd0
Disk: sd0 geometry: 120/255/63 [1935360 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending
> I haven't tried this mount, but IMHO
I don't see any humility.
On Sun, 25 Jul 2010 12:02:25 -0500
Chris Bennett wrote:
> frantisek holop wrote:
> > i have just managed to "mount" an ffs partition
> > as msdos. the the system promptly dies.
> If I plug my 110volt computer into a 220volt socket, it will promptly
> die too!
Well, hopefully it will only blow
frantisek holop wrote:
hi there,
i have just managed to "mount" an ffs partition
as msdos. the the system promptly dies.
$ sudo fdisk sd0
Disk: sd0 geometry: 120/255/63 [1935360 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C
hi there,
i have just managed to "mount" an ffs partition
as msdos. the the system promptly dies.
$ sudo fdisk sd0
Disk: sd0 geometry: 120/255/63 [1935360 Sectors]
Offset: 0 Signature: 0xAA55
Starting Ending LBA Info:
#: id C H S - C H S
Dirk Mast wrote:
> Matthew Szudzik wrote:
>
>>> ath0 at pci0 dev 12 function 0 "Atheros AR2413" rev 0x01: irq 9
>>> ath0: AR2413 7.8 phy 4.5 rf 5.6, FCC2A*, address 00:1d:0f:af:98:88
>>
>> According to the CVS log at
>> http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/ic/ath.c#rev1.56
>> "supp
On Tue, Apr 15, 2008 at 11:52 AM, Dirk Mast <[EMAIL PROTECTED]> wrote:
>
> Matthew Szudzik wrote:
>
> >> ath0 at pci0 dev 12 function 0 "Atheros AR2413" rev 0x01: irq 9
> >> ath0: AR2413 7.8 phy 4.5 rf 5.6, FCC2A*, address 00:1d:0f:af:98:88
> >
> > According to the CVS log at
> > http://www.o
Matthew Szudzik wrote:
>> ath0 at pci0 dev 12 function 0 "Atheros AR2413" rev 0x01: irq 9
>> ath0: AR2413 7.8 phy 4.5 rf 5.6, FCC2A*, address 00:1d:0f:af:98:88
>
> According to the CVS log at
> http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/ic/ath.c#rev1.56
> "support is still incomplete" for
On Mon, Mar 10, 2008 at 5:37 PM, Richard Daemon
<[EMAIL PROTECTED]> wrote:
>
>
> BTW, I forgot to mention that I'm running 4.2-stable (February) and
> using GENERIC.
I am having the same issues running 4.3-current (snapshot from around
the march 20th) and GENERIC.
On Tue, Mar 11, 2008 at 7:32 AM, Dirk Mast <[EMAIL PROTECTED]> wrote:
>
> Matthew Szudzik wrote:
>
> >> ath0 at pci0 dev 12 function 0 "Atheros AR2413" rev 0x01: irq 9
> >> ath0: AR2413 7.8 phy 4.5 rf 5.6, FCC2A*, address 00:1d:0f:af:98:88
> >
> > According to the CVS log at
> > http://www.op
Matthew Szudzik wrote:
>> ath0 at pci0 dev 12 function 0 "Atheros AR2413" rev 0x01: irq 9
>> ath0: AR2413 7.8 phy 4.5 rf 5.6, FCC2A*, address 00:1d:0f:af:98:88
>
> According to the CVS log at
> http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/ic/ath.c#rev1.56
> "support is still incomplete" for
> ath0 at pci0 dev 12 function 0 "Atheros AR2413" rev 0x01: irq 9
> ath0: AR2413 7.8 phy 4.5 rf 5.6, FCC2A*, address 00:1d:0f:af:98:88
According to the CVS log at
http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/ic/ath.c#rev1.56
"support is still incomplete" for the AR2413 chipset.
On Mon, Mar 10, 2008 at 6:18 PM, Richard Daemon
<[EMAIL PROTECTED]> wrote:
>
> On Mon, Mar 10, 2008 at 5:16 PM, Dirk Mast <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > I use a Atheros Mini-PCI Card, which I brought up with the following
> command
> > (via the Book of pf):
> >
> > sudo ifc
On Mon, Mar 10, 2008 at 5:16 PM, Dirk Mast <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I use a Atheros Mini-PCI Card, which I brought up with the following command
> (via the Book of pf):
>
> sudo ifconfig ath0 up mediaopt hostap mode 11b chan 11 nwid pla nwkey pladoh
>
> sudo ifconfig ath0 10.50.9
Hello,
I use a Atheros Mini-PCI Card, which I brought up with the following command
(via the Book of pf):
sudo ifconfig ath0 up mediaopt hostap mode 11b chan 11 nwid pla nwkey pladoh
sudo ifconfig ath0 10.50.90.1
I then can't find the AP, even when standing a few centimeters away.
(Not when
Humppa,
I would like to install -current on my Acer Travelmate 290 to use it
with my D-Link DWL-650 or Netgear MA521 WLAN PCMCIA Card.
The boot process (cd41.iso and selfmade floppyC41.fs ISO) always stops
at the following point:
cbb0 at pci2 dev 3 function 0 "ENE CB-1410 CardBus" rev 0x01: irq 5
Hello,
On Wed, 21.02.2007 at 10:21:09 +0100, Toni Mueller <[EMAIL PROTECTED]> wrote:
> I have a strange problem: A machine I have to tend locks up once or
> twice a day.
after moving from that 4.0-stable MP kernel to a 4.0 -release + patches
UP kernel, the machine held up for about a week. pf has
Hello,
I have a strange problem: A machine I have to tend locks up once or
twice a day.
The situation:
LAN --- box1 (OpenBSD 4.0-stable)
| |
| |
| |
pppoe0 pppoe1
1.2.3.41.2.3.5
--- The Intern
Hi,
I just had a my system hang while rebooting for the second time.
When I looked in the console I saw the last kernelmessage was:
`syncing disks...'
After pressing alt-ctrl-esc and typing `boot reboot' I got the
system to reboot.
How should I proceed from here? Is this a sign the HD is getting
89 matches
Mail list logo
