v5.8 boots in Wyse Thin client (AMD G-T48E) but v5.9 does not.

2016-04-09 Thread Pekka Niiranen
Hello everybody, I tried to install OpenBSD v5.9 but as soon as kernel loads the screen goes black. Cannot enter into UKC> either. hd0a:5.9/amd64/bsd.mp dropped into debugger with some radeon errors. 1) Boots with v5.8 but I get console messages (like in NetBSD 7.0) as long as have the USB

Re: v5.8 boots in Wyse Thin client (AMD G-T48E) but v5.9 does not.

2016-04-09 Thread Pekka Niiranen
On 09/04/16 12:04, Mark Kettenis wrote: From: Pekka Niiranen Date: Sat, 9 Apr 2016 11:33:55 +0300 r600_cp: Failed to load firmware "radeon-palm_pfp" error: [drm:pid0:evergreen_startup] *ERROR* Failed to load firmware! This means you don't have the radeon firmware installed.

vmxnet3 jams spuriously on VMware Fusion

2023-07-19 Thread Pekka Niiranen
Hello, Description: Using VMXNET3 adapter in dual core Openbsd 7.3 (release) on VMware Fusion 13.0,2 the network jams. I noticed this during initial installation of packages when "pkg_add" would stop with error "ftp: no route to host" Observations: When I pinged default gateway "top" -comm

Tested with -current: bwi-firmware jams Powerbook G4 AL 17", but Zyxel works

2012-08-06 Thread Pekka Niiranen
Hello again, 1. I tried (as suggested by Kenneth so time ago) with -current (I build kernel and userland) but the problems persists; Executing console command "ifconfig bwi0 scan" jams the whole machine with console printing (in blue color) continuously line: bwi0: intr fatal TX/RX (0): error

Snapshot 19/10/2012: Re: bwi-firmware jams Powerbook G4

2012-10-20 Thread Pekka Niiranen
Hi, tried today, still the same: bwi0: intr fatal TX/RX (0): error 0x0001 The number in parentheses varies between 0 and 1. -pekka- Original Message Subject:Re: bwi-firmware jams Powerbook G4 Date: Tue, 17 Jul 2012 23:45:03 +0300 From: pekka N

SOLVED: Sun Ultra 45 freezes at fsck

2013-05-29 Thread Pekka Niiranen
On 5/28/13 11:20 PM, Mark Kettenis wrote: From: pekka Date: Tue, 28 May 2013 22:51:32 +0300 On 5/28/13 12:53 AM, slhac tivist wrote: If it's good when you hard boot, then maybe an rc.* script is causing problems? Maybe you could figure it by elimination. Reboot flushes the cache and then execu