Search results

The answer is "no". If GNUstep advances further and FreeBSD is getting a compat layer like Darling it could change.

You probably need to delete some kernel options regarding diskless booting. Here is my kernel configuration file as reference: include SHEEVAPLUG ident SHEEVA options GEOM_PART_BSD options GEOM_PART_GPT options GEOM_PART_MBR options GEOM_LABEL options ROOTDEVNAME=\"ufs:/dev/ufs/sheevaroot\"...

I'm using the following in /etc/rc.conf: cloned_interfaces="lagg0" ifconfig_bge0="up" ifconfig_bge1="up" ifconfig_lagg0="up laggproto failover laggport bge0 laggport bge1 1.2.3.4/24"

Hi, They haven't. From the links above, you can get diffs/patches, which you can apply to your 9.x sources and rebuild the kernel.

Should be fixed by https://github.com/gliaskos/freebsd-chromium/commit/a17fb65be18bc06f625f159cb3c11167ebe782e7 which should show up in the ports tree with the next Chromium update.

AFAIK, 802.11n is not supported in 9.X with ath, only in -CURRENT: https://wiki.freebsd.org/dev/ath(4)/80211n

Hi, if you use 9.x, have a look at the following patches which were commited to 10.x but not MFCed: http://www.secnetix.de/olli/FreeBSD/svnews/index.py?r=226837 http://www.secnetix.de/olli/FreeBSD/svnews/index.py?r=226840

Not really sure if this is needed, howver here is a list of variables from a working V240: # eeprom -a|grep ttya ttya-rts-dtr-off: false ttya-ignore-cd: true ttya-mode: 9600,8,n,1,- output-device: ttya input-device: ttya Otherwise ask on freebsd-sparc64@freebsd.org, there are some people who...

Hm, normally removing it solves this problem. The coresponding OBP-variables were set to ttya after removal?

Remove the graphics card and install via serial console.

I think sunlabel -B ada0 is all that's missing (probably best after gpart). This will write the bootblock to the disk.

Is console="ofw" really required? I thought, this was deprecated (but I can be wrong)...

FYI, this is fixed in more recent (post 8.2-RELEASE) 8-STABLE and 9, see http://lists.freebsd.org/pipermail/freebsd-sparc64/2011-May/007865.html

Login via ALOM works just fine on a SF V240 for me. login: Nov 8 16:08:54 FreeBSD getty[1499]: open /dev/ttyv1: No such file or directory" To get rid of the message, edit /etc/ttys and set the status of /dev/ttyv* from "on" to "off". What's the exact symptom? What happens when you just press...

Maybe you can try a 9.0-RC ISO. If this also doesn't work, freebsd-sparc64@ might indeed be the best place.

ZFS is not supported as root-filesystem on FreeBSD/sparc64 ATM. Use UFS for / and then you can use ZFS for the rest.

I did several net installs on sparc64 without problems. If you can describe the problem more precisely maybe one has an idea.

Hi, You don't tell which type of machine you use, but I suspect one with an unsupported framebuffer. Try to install via serial console.

In -CURRENT it should now be possible with ZFS v28, see this blog post. In the comments there a workaround with zfs send/receive is also described.

No further ideas... :( It's running just fine on my 280R. Maybe ask on freebsd-sparc64@