Re: mount: /dev/da0p1: Invalid argument
On Fri, Feb 08, 2013 at 12:30:51PM +, Anton Shterenlikht wrote: From kostik...@gmail.com Fri Feb 8 12:25:21 2013 On Fri, Feb 08, 2013 at 12:01:41PM +, Anton Shterenlikht wrote: I need to transfer some files from sparc64 -current box onto amd64 9.1-RELEASE laptop. The amd64 laptop has no network connection yet, so I'm trying to achive this with a USB flash drive.=20 =20 The problem is that I always end up with =20 # mount /dev/da0p1 /mnt/ mount: /dev/da0p1: Invalid argument #=20 =20 If I do newfs on the sparc64 box, then I can't mount it on the amd64 box, and vice versa. =20 I tried just newfs /dev/da0, and using gpart, e.g.: =20 # gpart show /dev/da0 =3D 34 4029373 da0 GPT (1.9G) 34 20481 freebsd-ufs (1.0M) 2082 4027325 - free - (1.9G) =20 # =20 and then newfs /dev/da0p1, or similar, but no luck. =20 I tried sparc64 VTOC8 partition scheme too - no help. =20 I can mount the device and use it as expected, i.e. copy files to/from it on either box, but the other box doesn't seem to understand the file system. =20 I tried loading various modules in desperation, e.g. on the sparc64 side: =20 # kldstat=20 Id Refs AddressSize Name 19 0xc000 a80e58 kernel 21 0x101bca000 104000 geom_part_mbr.ko 31 0x101cce000 11 geom_label.ko 41 0x101dde000 108000 geom_part_gpt.ko #=20 =20 but still no use.=20 =20 Am I missing something simple? UFS on FreeBSD is not endian-agnostic. It uses the host byte order for multibyte values. As result, you can share UFS volumes only between hosts with the same endianess, like i386/amd64/ia64 little endian or sparc64/mips big endian. AFAIK, NetBSD has such support. Wow... I didn't realise that. I thought UFS (1 or 2) takes all care of endian-ness. Do you mean that even I had say a SCSI internal disk with UFS2, I couldn't move it between a little and a big endian freebsd boxes? So what is the advice for transferring data via USB in such cases? Any other gpart partition I could use? FAT should work and ZFS is also endian-agnostic. I don't know how well these code paths of the latter are tested though and we seem to have grown bugs in this regard at least in the area of intra- ZFS-version compatibility (which due to lack of understanding of the ZFS internals I'm not able to fix) since the split from (Open) Solaris. Marius ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Changes to kern.geom.debugflags?
On Mon, Dec 24, 2012 at 07:35:57PM -0500, Chris Ross wrote:
On Dec 23, 2012, at 16:56 , Chris Ross cross+free...@distal.com wrote:
I had brought up a machine months ago with freebsd-9-stable. I configured
it to boot off of a single disk, with ZFS, expecting I would likely later
attach the other disk to the zpool. I tried to do that today, but find
that I can't write the bootloader to either disk.
gpart: /dev/da0a: Operation not permitted
[...]
Okay. It occurred to me today what was likely the problem. I was running,
even when single user, off of the zfs pool on the disks I was trying to write
the bootloader to.
I tar'd up /boot after my recent install from a Dec 22 9-stable, and moved
it off-host. Then, I booted off of the July stable-9 CD-ROM I have in the
machine, and was able to write bootblocks (with gpart bootcode) and a
bootloader (dd if=/boot/zfsloader of=/dev/${disk}a bs=512 oseek=1024
conv=notrunc).
Now, the new problem. When I try to boot my sparc64 with these bits, I see:
FreeBSD/sparc64 ZFS boot block
Boot path: /pci@1c,60/scsi@2/disk@0,0:a
Consoles: Open Firmware console
ERROR: Last Trap: Division by Zero
{1} ok
So, does anyone know if something has gone unstable in the sparc64 zfsboot
in recent months? If I boot from the cdrom again and load the July zfsboot
via gpart bootcode, it boots correctly again.
Please see
http://www.freebsd.org/cgi/getmsg.cgi?fetch=0+0+/usr/local/www/db/text/2012/freebsd-sparc64/20121223.freebsd-sparc64
and provide debug information.
Marius
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Working and Supported SCSI Controller
On Thu, May 24, 2012 at 01:02:09AM +0200, vermaden wrote: Hi, as HARDWARE NOTES are next to useless: http://lists.freebsd.org/pipermail/freebsd-questions/2012-May/241164.html What *working* PCI/PCI-X SCSI controller do You guys suggest? Requirements: PCI/PCI-X Ultra160 or Ultra320 with one or more 68-pin internal connector LSI 53C1010-66 (Ultra160, sym(4)) or 53C1030 (Ultra320, mpt(4)) based ones. Marius ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-update(8) under sparc64? Why is it not available?
On Thu, Mar 25, 2010 at 02:11:00PM +, Craig Butler wrote: On Thu, 2010-03-25 at 07:36 -0400, Ken Smith wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 3/24/10 6:38 PM, Marius Strobl wrote: On Wed, Mar 24, 2010 at 02:57:09AM -0500, Mark Linimon wrote: You're the first one to ask in a while. Since our userbase is small, and developer time is limited, we've never set it up. The last time this topic came up IMO there was quite some interest in getting this running but the showstopper was that cperciva@ said that a requirement for any platform supported by freebsd-update(8) would be that the build server is able to run buildworld in 1 hour at most (unfortunately I currently just can't find that email). My 4x1.5GHz V440 I originally intended for this purpose unfortunately still takes 72 minutes last time I checked. I suspect a 8x1.2GHz V880 would be able to meet this requirement but I simply can't afford the housing for such a beast. I have none that are faster than 900MHz processors, and the one with the most processors in it is 6x750MHz. Ken, did the V880s at your university become available as intended some time ago? At the moment there are two - one being used by portmgr@ for package builds which is the 6x750MHz machine. The other I do the monthly snapshots and release builds on, it's 4x900MHz. This was its performance on the world built of 7.3-RELEASE: World build started on Sat Mar 20 23:34:54 EDT 2010 World build completed on Sun Mar 21 00:50:58 EDT 2010 Can we bend the rules a little ?? Who set the requirement of an hour ? freebsd-update might be a good thing to have.. IIRC it was Colin who once mentioned that this was decided by the Security Officers in order to be able to react to high impact security issues affecting multiple branches in a timely manner should the need ever arise. In any case he should be the right person to talk to about this so I CC'ed him. Marius ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: freebsd-update(8) under sparc64? Why is it not available?
On Wed, Mar 24, 2010 at 02:57:09AM -0500, Mark Linimon wrote: You're the first one to ask in a while. Since our userbase is small, and developer time is limited, we've never set it up. The last time this topic came up IMO there was quite some interest in getting this running but the showstopper was that cperciva@ said that a requirement for any platform supported by freebsd-update(8) would be that the build server is able to run buildworld in 1 hour at most (unfortunately I currently just can't find that email). My 4x1.5GHz V440 I originally intended for this purpose unfortunately still takes 72 minutes last time I checked. I suspect a 8x1.2GHz V880 would be able to meet this requirement but I simply can't afford the housing for such a beast. Ken, did the V880s at your university become available as intended some time ago? Marius ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Signal over range, WAS: X -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Tue, Dec 22, 2009 at 08:12:14PM +, Anton Shterenlikht wrote: On Tue, Dec 22, 2009 at 12:26:03PM -0700, Warren Block wrote: On Tue, 22 Dec 2009, Anton Shterenlikht wrote: Warren, thank you, but this doesn't help. I've added: Section Monitor Identifier Monitor0 HorizSync 30-50 VertRefresh 60 EndSection Section Device Identifier Card0 Driver mach64 BusID PCI:0:2:0 EndSection Hmm. Some web searching says non-Intel platforms might need a different reference clock: http://www.gentoo.org/doc/en/gentoo-sparc-faq.xml#doc_chap4_sect1 yes, now you told me I see it's actually in the logs: (--) MACH64(0): Reference clock 157.5/11 (14.318) MHz. (II) MACH64(0): If modes do not work on Ultra 5/10 or Blade 100/150, set option reference_clock to 28.636 MHz or 29.5 MHz by using either 28.636 or 29.5 I now get no signal over range. The right value for a Rage XL is 29.5 MHz. Marius ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Signal over range, WAS: X -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Tue, Dec 22, 2009 at 08:47:19PM +, Anton Shterenlikht wrote: On Tue, Dec 22, 2009 at 09:29:54PM +0100, Marius Strobl wrote: On Tue, Dec 22, 2009 at 08:12:14PM +, Anton Shterenlikht wrote: On Tue, Dec 22, 2009 at 12:26:03PM -0700, Warren Block wrote: On Tue, 22 Dec 2009, Anton Shterenlikht wrote: Warren, thank you, but this doesn't help. I've added: Section Monitor Identifier Monitor0 HorizSync 30-50 VertRefresh 60 EndSection Section Device Identifier Card0 Driver mach64 BusID PCI:0:2:0 EndSection Hmm. Some web searching says non-Intel platforms might need a different reference clock: http://www.gentoo.org/doc/en/gentoo-sparc-faq.xml#doc_chap4_sect1 yes, now you told me I see it's actually in the logs: (--) MACH64(0): Reference clock 157.5/11 (14.318) MHz. (II) MACH64(0): If modes do not work on Ultra 5/10 or Blade 100/150, set option reference_clock to 28.636 MHz or 29.5 MHz by using either 28.636 or 29.5 I now get no signal over range. The right value for a Rage XL is 29.5 MHz. Marius, thank you, I figured it out already. Here's the winning xorg.conf: http://seis.bris.ac.uk/~mexas/freebsd/xorg.conf in case somebody else might be using this hardware. Also, could you comment on Warren's suggestion of Radeon 7000? Do you think it might work on blade 1500? It won't work currently and also unlikely in the future. Marius ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: X -configure fails: Number of created screens does not match number of detected devices. Configuration failed.
On Sun, Dec 20, 2009 at 10:10:10PM +, Anton Shterenlikht wrote: On Sun, Dec 20, 2009 at 04:00:05PM +0100, Marius Strobl wrote: On Sat, Dec 19, 2009 at 09:48:03PM +, Anton Shterenlikht wrote: I've built X without hal, but get this error on X -configure: Actually when running `X -configure` or when trying to use the resulting /root/xorg.conf.new? This looks more like an error in the configuration file and the results returned by google for this failure message suggest that this can be due to the server not being able to load a configured module. Anyway, I'd try to use the resulting xorg.conf.new and if that fails manually checking its contents and removing unnecessary and unavailable stuff like DRI for example. yes, on 'X -configure'. Removing modules doesn't help. and then on 'X -config ./xorg.conf.new': Could you please make that xorg.conf.new available somewhere? Marius ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: trouble installing to sun blade 1500
On Tue, Dec 01, 2009 at 04:57:52PM +, Anton Shterenlikht wrote: On Tue, Dec 01, 2009 at 05:27:11PM +0100, Gheorghe Ardelean wrote: Hello Anton ... to FreeBSD sparc64, I get to OK prompt, type boot cdrom, but the process stops after a few seconds with: jumping to kernel entry at 0xc0088000. You're using an unsupported framebuffer (see the release notes). I think supported system means that it is working at least via serial console (this is the case e.g for Plain Ultra 1). So when I see something like this I hook-up a serial console and try over it. ok, 8.0 installation went fine. On reboot I get this panic (typed by hand): Entropy harvesting: interrupts ethernet point_to_pointpanic: trap: memory address not aligned Automatic reboot in 15 seconds Any advice? This unfortunately isn't sufficient information and my Blade 1500 doesn't exhibit this problem. Could you please put the full dmesg output online somewhere (this should be easy to capture when using a serial console)? Can you boot to single user? Marius ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
