Displaying 20 results from an estimated 400 matches similar to: "FreeBSD 9.0 - GPT boot problems?"
2012 Aug 04
2
FreeBSD 9.0 - GPT boot problems?
> On Fri, Aug 3, 2012 at 3:09 PM, Torfinn Ingolfsen
> <torfinn.ingolfsen@getmail.no> wrote:
> > Just a short update on this machine (Acer Aspire X1470) and the GPT / UEFI situation.
> > Today I set up another partition, EFI system partition. The partyitions now looks like this:
> > root@kg-vm2# gpart show ada0
> > => 34 250069613 ada0 GPT (119G)
2008 Jan 27
3
FreeBSD 6.3-stable and if_re - stability problems?
Hello!
Is anybody having stability problems with if_re under FreeBSD
6.3-stable?
I know about PR kern/118719[1] but it doesn't look like the problem I'm
having - at least my machine doesn't panic.
My machine[2] runs FreeBSD 6.3-stable / amd64:
root@kg-vm# uname -a
FreeBSD kg-vm.kg4.no 6.3-STABLE FreeBSD 6.3-STABLE #1: Sun Jan 27 02:10:15 CET 2008
2013 Jul 14
1
There is an error in chmod(1)
There is an error in the chmod(1) man page.
tingo at kg-v2$ uname -a
FreeBSD kg-v2.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #6: Fri Apr 27 23:50:55 CEST 2012
root at kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
tingo at kg-v2$ apropos ^sticky
sticky(7) - sticky text and append-only directories
tingo at kg-v2$ man 1 chmod | grep sticky
1000 (the sticky bit). See chmod(2)
2008 May 12
4
7.0 issues fixed? upgrade timing?
1. I have a realtek network card and am using a cable modem router. Does anyone know if fixes for problems with these (see below) have been backported from HEAD to RELENG_7?
2. Is this a good time to upgrade to RELENG_7?
3. I read a post last week that advised that 7.1 is a long way off. Appreciate any advice on use of ULE 3.0 and ZFS prior to 7.1 and a comment on what is holding up 7.1.
Thanks
2009 Apr 08
1
uchcom and RELENG_7?
Hi,
Is there any reason why uchcom[1] hasn't been MFC'ed to RELENG_7 yet?
I see discussion[2] about this subject as far back as around
7.0-release, but I can't find any uchcom.c files in my src, not even
for latest RELENG_7.
References:
1) http://www.freebsd.org/cgi/man.cgi?query=uchcom&apropos=0&sektion=0&manpath=FreeBSD+8-current&format=html
2)
2008 Feb 23
1
packet loss with re(4)
With FreeBSD 6.3-RELEASE, I'm finding significant packet loss
(sometimes 85%).
If I insert an Intel nic (fxp), there is nil packet loss with similar
tests (ping -c 100).
re0: <RealTek 8168/8111B PCIe Gigabit Ethernet> port 0xc800-0xc8ff
mem 0xf9fff000-0xf9ffffff irq 17 at device 0.0 on pci1
I have seen a thread on current mentioning similar problems:
2013 Feb 17
1
RELENG_8: amdtemp module and newer CPUs not working. MFC?
Hello,
I'm running FreeBSD 8.3-stable on a machine with an AMD A8-5600K cpu.
tingo at kg-quiet$ uname -a
FreeBSD kg-quiet.kg4.no 8.3-STABLE FreeBSD 8.3-STABLE #2: Fri Jan 4 19:18:15 CET 2013
root at kg-quiet.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
tingo at kg-quiet$ dmesg | grep CPU | head -1
CPU: AMD A8-5600K APU with Radeon(tm) HD Graphics (3618.02-MHz K8-class CPU)
2008 Mar 04
1
FreeBSD 7.9-stable: weird messages in /var/log/messages?
Hello
One one of my stable machines I see these messages in /var/log/messages:
Mar 3 18:37:41 kg-i82 kernel: 16.011e9e3975b3aa06 too long
Mar 3 21:41:42 kg-i82 kernel: 16.016a24cf0742715c too long
Mar 3 21:41:58 kg-i82 kernel: 15.feb784aee196608c too short
Does anyone know hwat the messages mean, or which part of the kernel
they are from?
Googling didn't help me.
The machine runs FreeBSD
2008 Feb 06
3
Reconstruct disklabel for UFS and GELI volumes
Hi,
Somehow[TM] an installation of 4.11 to ad0s3 managed to wipe out my
existing disklabel for 7.0 on ad0s4. I now need to recover the
disklabel to get my system to boot!
There were three labels
- ad0s4a: UFS, exact size unknown. Is it possible to infer this from
the UFS partition size? I can mount this already, as I simply wrote an
'a' label of maximum size to the disklabel
- ad0s4b:
2008 Sep 17
1
floppy disk controller broken
Hello,
when testing FreeBSD-7.1-BETA i discovered that the floppy disk
controller doesn't work correctly. Trying to format a floppy (perhaps
with bad blocks) i get:
Processing fdformat: ioctl(FD_FORM): Device not configured
instead of the normal E letter. I then checked the same problem is
present on FreeBSD-6.3 and it has been reported by Beech Rintoul (*) in
2006! Of course the floppy disk
2009 Jan 06
2
ACPI support?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello All,
I have had a problem detecting the network card on my notebook when ACPI
is enabled for a year. The problem still exists in 7.1-RELEASE.
with ACPI:
...
bge0: <Broadcom NetLink Gigabit Ethernet Controller, ASIC rev. 0xb002>
irq 17 at device 0.0 on pci8
bge0: 0x10000 bytes of rid 0x10 res 3 failed (0, 0xffffffff).
bge0: couldn't
2008 May 18
2
possible zfs bug? lost all pools
after trying to mount my zfs pools in single user mode I got the following
message for each:
May 18 09:09:36 gw kernel: ZFS: WARNING: pool 'cache1' could not be loaded as
it was last accessed by another system (host: gw.bb1.matik.com.br hostid:
0xbefb4a0f). See: http://www.sun.com/msg/ZFS-8000-EY
any zpool cmd returned nothing else as not existing zfs, seems the zfs info on
disks
2008 Oct 23
1
After an update stable doesn't boot
Hi
I just did a system update and after I've rebooted it doesn't boot up any
more.
All I'm getting is a blank screen with a curser blinking at the top left
corner of the screen.
This system was running 7.0-STABLE
Any ideas as to how I can get it back up?
Regards
Reinhold
2013 Aug 27
6
Suggest changing dirhash defaults for FreeBSD 9.2.
I have been experimenting with dirhash settings, and have scoured the internet
for other peoples' experience with it.
(I found the performance improvement in compiling has forestalled the need to
add an SSD drive. ;-)
I believe that increasing the following values by 10 would benefit most FreeBSD
users without disadvantage.
vfs.ufs.dirhash_maxmem: 2097152 to 20971520
2004 Mar 10
5
unexpected softupdate inconsistency
Hi there,
System is FreeBSD 4.9 Stable
Had a problem during a portupgrade that when portupgrade did some
cleaning a directory could not be deleted because it were not empty.
However, it was empty. rm -rf didn't help either.
Because I didn't know what to do I decided to boot.
At system startup fsck was started which produced the message: unexpected
softupdate inconsistency and also that
2006 Oct 17
4
FreeBSD 4.x EoL
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There has been a lot of discussion on these two mailing lists about the upcoming
EoL of FreeBSD 4.x which I mentioned in my email entitled "HEADS UP: FreeBSD
5.3, 5.4, 6.0 EoLs coming soon". Now that everybody (hopefully) has had their
say, I'd like to offer some background and explanation.
The concept of "security branches"
2009 Mar 03
1
bce: unable to fix media
Hi,
tuning my network fixing nic's speed and duplex (both on server and
switch) i got this error with bce driver:
# ifconfig bce0
bce0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=1bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4>
ether 00:15:c5:fe:11:01
inet 192.168.1.13 netmask 0xffffff00 broadcast
2012 Nov 21
3
Increasing the DMESG buffer....
Hi,
As a next question to my building this server.
I'm nogt able to get a full verbose dmesg.
Probably because the kernelbuffer for it is too small.
I know there used to be a kernel option to increase it.
But I can not find it with the setting in NOTES or any other place I
looked....
Is it still there?
Thanx,
--WjW
2019 May 03
2
VM: Unable to enable scatter-gather / tx-checksumming / tcp-segmentation offload
In my Linux VM, I am unable to change scatter-gather / tx-checksumming /
TCP-segmentation offload features by ethtool command. I am using virtio nic
with vhostuser port backend.
It shows me an error:
Cannot change tx-checksumming
Cannot change scatter-gather
Cannot change tcp-segmentation offload
Could not change any device features
Ony running command ethtool -k ens3, I get the following:
2010 Sep 01
2
HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Everyone,
On November 30th, FreeBSD 6.4 and FreeBSD 8.0 will have reached their
End of Life and will no longer be supported by the FreeBSD Security Team.
Since FreeBSD 6.4 is the last remaining supported release from the FreeBSD
6.x stable branch, support for the FreeBSD 6.x stable branch will also
cease at the same point. Users of either of