Yes, unfortunately right now the -current stuff will only work with panda ES. Things are being worked on, please be patient.
On Sun, Jun 16, 2013 at 10:05 AM, minux <[email protected]> wrote: > Dear List, > > I'm working on getting OpenBSD/beagle running on a Pandaboard, but so > far, without success. > I'm using latest binary sets of armish port as root fs. > > the GENERIC kernel seemed to boot correctly, and it recognized most > hardware, however, the console > output stopped after the WARNING line: > > <snip> > scsibus0 at sdmmc0: 2 targets, initiator 0 > sd0 at scsibus0 targ 1 lun 0: <SD/MMC, Drive #01, > SCSI2 0/direct fixed > sd0: 3781MB, 512 bytes/sector, 7744512 sectors > vscsi0 at root > scsibus1 at vscsi0: 256 targets > softraid0 at root > scsibus2 at softraid0: 256 targets > boot device: lookup '' failed. > root device: sd0a > swap device (default sd0b): > root on sd0a swap on sd0b dump on sd0b > WARNING: CHECK AND RESET THE DATE! > > I tried to add some printf to init(8) and enabled SYSCALL_DEBUG, but > every time it boots, init(8) stops > at a different point. > > example 1: > proc 22279 (init): native num 194 ret: err = 0, rv = 0x0,0xbffc3380 > proc 22279 (init): native num 195 call: setrlimit(0x8, 0xbffc3390) > proc 22279 (init): native num 195 ret: err = 0, rv = 0x0,0xbffc3390 > proc 22279 (init): native num 194 call: getrlimit(0x4, 0xbffc3380) > proc 22279 (init): native num 194 ret: err = 0, rv = 0x0,0xbffc3380 > proc 22279 (init): native num 195 call: setrlimit(0x4, 0xbffc3390) > proc 22279 (init): native num 195 ret: err = 0, rv = 0x0,0xbffc3390 > proc 22279 (init): native num 96 call: setpriority(0x0, 0x0, 0x0) > proc 22279 (init): native num 96 ret: err = 0, rv = 0x0,0x0 > proc 22279 (init): native num 60 call: umask(0x12) > proc 22279 (init): native num 60 ret: err = 0, rv = 0x12,0x0 > proc 22279 (init): native num 59 call: execve(0x49f00, 0xbffc3428, 0xbffc3528) > namei: '/bin/sh' > > example 2: > proc 26707 (init): native num 197 ret: err = 0, rv = 0x4047a000,0x0 > proc 26707 (init): native num 197 call: mmap(0x0, 0x1000, 0x3, 0x1002, > 0xffffffff, 0x0, 0x0, 0x0) > proc 26707 (init): native num 197 ret: err = 0, rv = 0x48e3b000,0x0 > proc 26707 (init): native num 197 call: mmap(0x0, 0x1000, 0x3, 0x1002, > 0xffffffff, 0x0, 0x0, 0x0) > proc 26707 (init): native num 197 ret: err = 0, rv = 0x40d98000,0x0 > proc 26707 (init): native num 197 call: mmap(0x0, 0x1000, 0x3, 0x1002, > 0xffffffff, 0x0, 0x0, 0x0) > proc 26707 (init): native num 197 ret: err = 0, rv = 0x49e19000,0x0 > proc 26707 (init): native num 197 call: mmap(0x0, 0x1000, 0x3, 0x1002, > 0xffffffff, 0x0, 0x0, 0x0) > proc 26707 (init): native num 197 ret: err = 0, rv = 0x4de2d000,0x0 > proc 26707 (init): native num 197 call: mmap(0x0, 0x1000, 0x3, 0x1002, > 0xffffffff, 0x0, 0x0, 0x0) > proc 26707 (init): native num 197 ret: err = 0, rv = 0x4e1e3000,0x0 > > > I'm running out of ideas, could anyone please give me some hints on > how to debug this problem? > Thank you in advance. > > > Cheers, > minux
