On Mon, 26 Sep 2011, Adrian Chadd wrote:
I've just tried to boot a FreeBSD-9.0 BETA2 (i386) memstick USB image
on my BIOS.
When inserted into a FreeBSD box (the one that I wrote it from), the
partition table has an MBR style partition setup with a single EFI
partition on it.
Also known as a "
On 26 September 2011 13:07, Kevin Oberman wrote:
> I may not have been entirely clear. The Android and the BIOS in my laptop seem
> to have an issue. The Thunderbolt does not seem to block boot on other
> systems,
> just my T520.
Oh I understood that. It was this comment:
> I suspect that the
On Sun, Sep 25, 2011 at 10:03 PM, Adrian Chadd wrote:
> On 26 September 2011 12:56, Kevin Oberman wrote:
>
>> I suspect that the thumb drive is the issue, not FreeBSD.
>
> I've booted the drive successfully on an older Via C3 board.
>
> I'm now watching it boot successfully on a Gigabyte GA-8I91
On 26 September 2011 12:56, Kevin Oberman wrote:
> I suspect that the thumb drive is the issue, not FreeBSD.
I've booted the drive successfully on an older Via C3 board.
I'm now watching it boot successfully on a Gigabyte GA-8I915PC Duo board.
I'm going to try dumping a Linux distro on this U
On Sun, Sep 25, 2011 at 9:14 PM, Adrian Chadd wrote:
> Hi all,
>
> I've just tried to boot a FreeBSD-9.0 BETA2 (i386) memstick USB image
> on my BIOS.
>
> When inserted into a FreeBSD box (the one that I wrote it from), the
> partition table has an MBR style partition setup with a single EFI
> par
I agree, the lack of a virtual/emergency terminal seems a bit silly.
I'm not sure about the cons25 versus xterm stuff - you're not the
first person to report this. Guys/girls/other (Hi SF!) - why is this?
:)
It shouldn't be that hard to submit a patch to enable those extra vtys?
Adrian
Hi all,
I've just tried to boot a FreeBSD-9.0 BETA2 (i386) memstick USB image
on my BIOS.
When inserted into a FreeBSD box (the one that I wrote it from), the
partition table has an MBR style partition setup with a single EFI
partition on it.
It however doesn't even get to the point where it fai
Hi,
On Sun, Sep 25, 2011 at 8:52 PM, Brett Glass wrote:
> Next thing I did was try to recompile the kernel to streamline it and add
> features I want compiled in, such as ipfw and dummynet. Alas, I saw no sign
> of the BSD-licensed Clang compiler, for which I've waited for many years (I
> can't b
All:
Just spent an afternoon and evening experimenting with FreeBSD
9.0-BETA2. Overall reaction: so far, it's been pretty stable and
responsive, but I'm concerned that it may have substantially
increased memory and CPU requirements relative to previous
versions. The new installer, while it's
I get a panic if I try to run a dtrace script that uses an fbt probe
from a module that does not have CTF data. The polling patch resolves
the issue for me:
Index: sys/cddl/dev/fbt/fbt.c
===
--- sys/cddl/dev/fbt/fbt.c (revision
20110331:
ath(4) has been split into bus- and device- modules. if_ath contains
the HAL, the TX rate control and the network device code. if_ath_pci
contains the PCI bus glue. For Atheros MIPS embedded systems,
if_ath_ahb
contains the AHB glue. Users need to load both
Hello, arrowdodger.
You wrote 25 сентября 2011 г., 19:58:02:
> Hello. I've updated my 8-stable installation to 9-stable and now there is no
> ath0 device. I'm almost sure that it isn't caused by tweaks in my kernel
> config file. I would be glad to provide more information if necessary.
Did you
Chris Rees wrote:
On 25 September 2011 14:01, Fbsd8 wrote:
deeptec...@gmail.com wrote:
Fbsd8 wrote:
[...]
the reboot starts. Don't let the reboot occur until the memstick is
removed.
Do NOT alter! More often than not,
(1) you keep floppies, optical discs, and memory sticks in your
compu
2011/9/25 Lev Serebryakov :
> Hello, Garrett.
> You wrote 25 сентября 2011 г., 12:06:05:
>
>> Talking to Xin yesterday, he was convinced that this was a
>> filesystem//kern bug. Before I file a PR, I'm wondering if anyone else
>> has seen this issue..
> Yes, and I posted message about it in em
Fbsd8 writes:
Hi,
> Fixing burncd should be a priority
It's not broken, so it doesn't need to be fixed.
burncd has been designed to work with the old ata stack, when using new
cam based ata stack, just use cdrecord.
It deserves an entry in the release notes, nothing less, nothing more.
Éric Ma
On Sun, Sep 25, 2011 at 9:29 AM, Gary Jennejohn
wrote:
> On Sun, 25 Sep 2011 07:30:49 -0500
> Antonio Olivares wrote:
>
>> > More concerns and questions onthe new bsdinstall:
>> >
>> > There is no upgrade function. How will a user be able to upgrade to BETA3
>> > (or RC1?) without wiping out BE
On Sun, Sep 25, 2011 at 10:16 AM, Warren Block wrote:
> On Sun, 25 Sep 2011, Antonio Olivares wrote:
>
>>> More concerns and questions onthe new bsdinstall:
>>>
>>> There is no upgrade function. How will a user be able to upgrade to
>>> BETA3 (or RC1?) without wiping out BETA2 installation?
>>>
>
On Sun, 25 Sep 2011, Antonio Olivares wrote:
More concerns and questions onthe new bsdinstall:
There is no upgrade function. How will a user be able to upgrade to BETA3 (or
RC1?) without wiping out BETA2 installation?
For instance, user might have built many software applications from ports
On Sun, 25 Sep 2011 07:30:49 -0500
Antonio Olivares wrote:
> > More concerns and questions onthe new bsdinstall:
> >
> > There is no upgrade function. How will a user be able to upgrade to BETA3
> > (or RC1?) without wiping out BETA2 installation?
> >
> > For instance, user might have built man
Hello. I've updated my 8-stable installation to 9-stable and now there is no
ath0 device. I'm almost sure that it isn't caused by tweaks in my kernel
config file. I would be glad to provide more information if necessary.
___
freebsd-current@freebsd.org ma
On 25 September 2011 14:01, Fbsd8 wrote:
> deeptec...@gmail.com wrote:
>>
>> Fbsd8 wrote:
>>>
>>> 6. At the "Complete screen" when the reboot option is selected the
>>> cd/dvd drive should automatically open so the install media can be
>>> removed just like sysinstall does. If disc1.iso or dvd.iso
deeptec...@gmail.com wrote:
Fbsd8 wrote:
6. At the "Complete screen" when the reboot option is selected the
cd/dvd drive should automatically open so the install media can be
removed just like sysinstall does. If disc1.iso or dvd.iso was installed
to memstick and used to boot from to install the
Jaakko Heinonen wrote:
On 2011-09-24, Joe Barbish wrote:
It seems that in 9.0 the cd/dvd/drive is now given a dev name of cd0
where in all previous releases it was acd0.
Tried to use the system burncd command in 9.0 and got this error msg
burncd: ioctl(CDRIOCGETBLOCKSIZE): Inappropriate ioctl
> More concerns and questions onthe new bsdinstall:
>
> There is no upgrade function. How will a user be able to upgrade to BETA3
> (or RC1?) without wiping out BETA2 installation?
>
> For instance, user might have built many software applications from ports and
> not want to rebuild everything.
Hello, Garrett.
You wrote 25 сентября 2011 г., 12:06:05:
> Talking to Xin yesterday, he was convinced that this was a
> filesystem//kern bug. Before I file a PR, I'm wondering if anyone else
> has seen this issue..
Yes, and I posted message about it in embedded@ (Message-ID
<1175277342.20110
On 24 September 2011 13:13, Alexander Motin wrote:
> OK, but how taskqueue related to the timer? Taskqueue uses SWI that are
> called in separate thread and except "swi4: clock" AFAIR they are not
> anyhow related to the timer.
What about possible effects on the scheduler?
Is it possible that on
Now that you mention it, yes.
adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
More concerns and questions onthe new bsdinstall:
There is no upgrade function. How will a user be able to upgrade to BETA3 (or
RC1?) without wiping out BETA2 installation?
For instance, user might have built many software applications from ports and
not want to rebuild everything.
Other issu
Hi,
I've been doing builds with FreeNAS recently on 9.x-BETA2 machines
recently and I've noticed that I need to add 2 'sync's prior to each
umount command in the nanobsd scripts when running repeated builds,
otherwise it fails with:
umount: unmount of /scratch/freenas/obj.amd64/_.mnt failed: D
29 matches
Mail list logo
