Re: fail to boot snapshot 5.5 on MBPro8,2 - solved, X also working.

2014-02-09 Thread Volker Nowarra
short update / hint:
if for the very first time after the install the system does not boot, go to a 
running system and try to configure the 55 bsd kernel:

config -o bsd.fix -e bsd

and remove the radeondrm module (find and disable are your friends, type help 
at the UKC prompt).
Then boot with boot hd0a:/bsd.fix.

rgds,
Volker

 Von: Volker Nowarra volker.nowa...@me.com
 Betreff: Aw: fail to boot snapshot 5.5 on MBPro8,2 - solved, X also working.
 Datum: 10. Februar 2014 00:07:56 MEZ
 An: tech@openbsd.org
 
 Hi,
 
 Reference: http://marc.info/?l=openbsd-techm=139175497630924w=4
 
 bsd55 does not start per default from snapshots. 
 Thx to Joerg, I could now successfully boot MBPro 8,2 with snapshot 
 (bsd55-beta).
 Main topic is to get the radeondrm firmware, my procedure was this:
 
 I booted bsd55.rd, and installed from http (CDROM not recognized, internal 
 wireless not working, but bge0 works).
 Then get src.tar.gz and sys.tar.gz installed, and cvs up to -current. 
 Also installed ports and xenocara, and updated to -current, as in Building 
 the System from Source (http://openbsd.org/faq/faq5.html).
 
 Then update the radeon firmware as described in following current 
 (http://openbsd.org/faq/current.html).
 I had to use fw_update. To use pkg_add, the environment variable should point 
 to the right direction. 
 
 pkg_add'd icewm and firefox, started X with icewm, all works well.
 
 DMESG:
 OpenBSD 5.5-beta (GENERIC) #243: Wed Feb  5 14:48:36 MST 2014
t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
 RTC BIOS diagnostic error 
 ffclock_battery,ROM_cksum,config_unit,memory_size,fixed_disk,invalid_time
 real mem = 4185079808 (3991MB)
 avail mem = 4065501184 (3877MB)
 mainbus0 at root
 ...
 



Re: fail to boot snapshot 5.5 on MBPro8,2

2014-02-06 Thread Joerg Jung
Hi,

Am 05.02.2014 um 15:08 schrieb Sven-Volker Nowarra peb.nowa...@bluewin.ch:

 I tried to install 5.5 snapshots from 2. Feb and 3. Feb onto my laptop 
 MacBook Pro 8,2 - both failed. Then used an older snapshot from 
 spacehopper.org/mirrmon, which claimed to be 12 days old. Failed as well. 
 
 MacBook Pro runs perfectly well with 5.4, and 5.5 bsd.rd lets me go into the 
 installation. After a reboot (bsd.mp), the system hangs after the line where 
 the disk should be mounted, and the nvram/clock message normally appears 
 (actually before going into userland). The screen then turns shortly but 
 steady into white/grey, so the blue kernel lines can't be read anymore.
 
 I then tried to boot with bsd -c, with an external USB keyboard - but it 
 hangs as well (as such no difference to the internal keyboard). Looks like I 
 have two prompts (underlines) on the screen, that are flickering.

I see the same issue with my MacBook Air 4,2

 With this status I cannot provide any dmesg:-(

You may at least provide the dmesg from the working 5.4 bsd and the snapshot 
bsd.rd.

Regards,
Joerg

 The first line after boot -c would show the booting hd0a:bsd: 
 7635180+1660460+1097336... line, and then entry point at  The kernels 
 blue lines would say:
 
 kbc: cmd word write error
 [ using 926384 bytes of bsd ELF symbol table ]
 Copyright (c) 1982, 1986, 1989, 1991, 1993
  The Regents of the University ...
 
 OpenBSD 5.5-beta (GENERIC.MP) #284: Mon Feb  3 07:57:32 MST 2014
  t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
 RTC BIOS diagnostic error 
 ffclock_battery,ROM_cksum,config_unit,memory_size,fixed_disk,invalid_time
 real mem = 4185079808 (3991MB)
 avail mem = 4065452032 (3877MB)
 User Kernel Config
 UKC
 
 The errors on RTC BIOS line also appears in the fully functional 5.4 
 version. But I couldn't see the line kbc: cmd word write error in other 
 dmesgs on OpenBSD-tech.
 
 As mentioned, no dmesg possible, anyone else with MBPro issue?
 
 Any idea were to get old snapshots? 
 I could try to build the kernel from scratch, I successfully built 5.4, and 
 building with -current shows same behaviour as snapshots. Any ideas where to 
 go from here?
 (No serial port obviously).
 
 Volker
 




fail to boot snapshot 5.5 on MBPro8,2

2014-02-05 Thread Sven-Volker Nowarra
Hi,

I tried to install 5.5 snapshots from 2. Feb and 3. Feb onto my laptop MacBook 
Pro 8,2 - both failed. Then used an older snapshot from 
spacehopper.org/mirrmon, which claimed to be 12 days old. Failed as well. 

MacBook Pro runs perfectly well with 5.4, and 5.5 bsd.rd lets me go into the 
installation. After a reboot (bsd.mp), the system hangs after the line where 
the disk should be mounted, and the nvram/clock message normally appears 
(actually before going into userland). The screen then turns shortly but steady 
into white/grey, so the blue kernel lines can't be read anymore.

I then tried to boot with bsd -c, with an external USB keyboard - but it 
hangs as well (as such no difference to the internal keyboard). Looks like I 
have two prompts (underlines) on the screen, that are flickering.

With this status I cannot provide any dmesg:-(

The first line after boot -c would show the booting hd0a:bsd: 
7635180+1660460+1097336... line, and then entry point at  The kernels 
blue lines would say:

kbc: cmd word write error
[ using 926384 bytes of bsd ELF symbol table ]
Copyright (c) 1982, 1986, 1989, 1991, 1993
  The Regents of the University ...

OpenBSD 5.5-beta (GENERIC.MP) #284: Mon Feb  3 07:57:32 MST 2014
  t...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
RTC BIOS diagnostic error 
ffclock_battery,ROM_cksum,config_unit,memory_size,fixed_disk,invalid_time
real mem = 4185079808 (3991MB)
avail mem = 4065452032 (3877MB)
User Kernel Config
UKC

The errors on RTC BIOS line also appears in the fully functional 5.4 version. 
But I couldn't see the line kbc: cmd word write error in other dmesgs on 
OpenBSD-tech.

As mentioned, no dmesg possible, anyone else with MBPro issue?

Any idea were to get old snapshots? 
I could try to build the kernel from scratch, I successfully built 5.4, and 
building with -current shows same behaviour as snapshots. Any ideas where to go 
from here?
(No serial port obviously).

Volker