Graham Menhennitt wrote:
Foo2zjs doesn't seem to have changed recently. CUPS has changed but I
doubt that's the problem. Maybe something to do with USB drivers?
In 8.x, CUPS 1.4.x wants libusb support and the ugen driver, rather than
ulpt. Once I changed over to that, all was fine.
It's
Hi,
please CC me on replies.
I have a system which was at 7.1-pX. After the update to 7.2-p5 it
started to exhibit deadlocks after some minutes of uptime.
With 7.1 (generic kernel) it was running fine, with 7.2 generic the
problems started directly.
The system is now at 7-stable with a
Juergen Lock wrote:
Hi!
In article 4b150d60.5050...@denninger.net you write:
-=-=-=-=-=-
Jeremy Chadwick wrote:
On Sat, Nov 28, 2009 at 09:43:25PM -0600, Karl Denninger wrote:
Karl Denninger wrote:
Jeremy Chadwick wrote:
On
Alexander Leidinger wrote:
Hi,
please CC me on replies.
I have a system which was at 7.1-pX. After the update to 7.2-p5 it
started to exhibit deadlocks after some minutes of uptime.
With 7.1 (generic kernel) it was running fine, with 7.2 generic the
problems started directly.
The system
On Monday 14 December 2009 9:37:51 pm Jonathan Chen wrote:
On Mon, Dec 14, 2009 at 10:46:27AM -0500, John Baldwin wrote:
On Sunday 13 December 2009 2:19:05 pm Jonathan Chen wrote:
Hi,
This is a general rehash of a problem that I've been having with my
Dell Latitude D830 with an
On Thu, 03 Dec 2009 03:03:29 -0600
Scot Hetzel swhet...@gmail.com wrote:
If you have a look at the Root On ZFS tutorial, it shows how to create
a GPT formated system from the Fixit environment:
http://wiki.freebsd.org/RootOnZFS
Just FYI, this tutorial worked nicely with the memtick image,
On Tue, 15 Dec 2009 17:54:06 +0100
Torfinn Ingolfsen torfinn.ingolf...@broadpark.no wrote:
On Thu, 03 Dec 2009 03:03:29 -0600
Scot Hetzel swhet...@gmail.com wrote:
If you have a look at the Root On ZFS tutorial, it shows how to
create a GPT formated system from the Fixit environment:
Hi,
I've just upgraded my 8 from around the 6th of december 2 days ago. Now
the system won't boot up. When it is going to mount the rootfs, it
receives some ICRC error and the harddisk gets accessed massivly. The the
error shown on the screenshot is repeating and repeating. Apart from my
custom
On Dec 15, 2009, at 7:03 AM, Karl Denninger wrote:
This is now marked fixed and it appears (after limited testing thus far)
that it indeed is.
The bug existed in 7 as well. It's not a regression introduced in 8.
The reason why this didn't come up in the 7 time frame is that sio(4)
was still
Marcel Moolenaar wrote:
On Dec 15, 2009, at 7:03 AM, Karl Denninger wrote:
This is now marked fixed and it appears (after limited testing thus far)
that it indeed is.
The bug existed in 7 as well. It's not a regression introduced in 8.
The reason why this didn't come up in the 7
On Tue, Dec 15, 2009 at 09:57:59AM -0800, Marcel Moolenaar wrote:
On Dec 15, 2009, at 7:03 AM, Karl Denninger wrote:
This is now marked fixed and it appears (after limited testing thus far)
that it indeed is.
The bug existed in 7 as well. It's not a regression introduced in 8.
The
2009/12/12 Alexander Motin m...@freebsd.org:
To unlock drive permanently SET MAX ADDRESS ATA command should be used
(probably the same as Linux uses) with Volatile bit set, to make it not
restore on power cycle. I don't know how to send this command with
legacy ata(4), you need some external
Oliver Lehmann wrote:
I've just upgraded my 8 from around the 6th of december 2 days ago. Now
the system won't boot up. When it is going to mount the rootfs, it
receives some ICRC error and the harddisk gets accessed massivly. The the
error shown on the screenshot is repeating and repeating.
On Dec 15, 2009, at 10:36 AM, Jeremy Chadwick wrote:
Thanks for fixing the problem Karl's reported. As I've stated in the
past, I appreciate your efforts and attentiveness to this sort of thing.
If there's any way I can repay you (Paypal donations, etc.), just let me
know and I'll do what I
On Tue, Dec 15, 2009 at 09:44:22PM +0300, KOT MATPOCKuH wrote:
2009/12/12 Alexander Motin m...@freebsd.org:
To unlock drive permanently SET MAX ADDRESS ATA command should be used
(probably the same as Linux uses) with Volatile bit set, to make it not
restore on power cycle. I don't know how
On Tue, Dec 15, 2009 at 12:16:25PM -0800, Marcel Moolenaar wrote:
On Dec 15, 2009, at 10:36 AM, Jeremy Chadwick wrote:
Thanks for fixing the problem Karl's reported. As I've stated in the
past, I appreciate your efforts and attentiveness to this sort of thing.
If there's any way I can
On Tuesday 15 December 2009 2:47:03 pm Jonathan Chen wrote:
On Tue, Dec 15, 2009 at 10:18:36AM -0500, John Baldwin wrote:
On Monday 14 December 2009 9:37:51 pm Jonathan Chen wrote:
On Mon, Dec 14, 2009 at 10:46:27AM -0500, John Baldwin wrote:
On Sunday 13 December 2009 2:19:05 pm
I didn't think this routing patch was related to the bad neighbor solicitation
messages as suggested in the subject field but I tried it anyway. It does not
fix my IPv6 problem. I still get bad neighbor solicitation messages and
freebsd 8 doesn't respond to 4/5 IPv6 pings.
Thanks,
Tom
On Dec
Thanks for reporting back. I asked you for a routing table dump
in my previous email, would you mind emailing it to me privately?
-- Qing
-Original Message-
From: Tom Pusateri [mailto:pusat...@bangj.com]
Sent: Tuesday, December 15, 2009 1:28 PM
To: Li, Qing
Cc:
Thanks for sending me the routing table output.
Actually I believe both your problems are indeed related to the
prefix route.
I was able to reproduce Dennis Glatting's problem, which was due
to one of the prefix entry being off-link.
In your case the prefix route for
Hi Folks,
today I did an update from 7.2-RELEASE-p4 to 8.0-RELEASE using
freebsd-update.
Everything went smooth, apart from the fact that I can't mount my second
disk.
It's all a bit puzzling...
Here are the facts:
[r...@talisker ~]# cat /etc/fstab
# DeviceMountpointFStype
On Dec 14, 2009, at 10:46 AM, Robert Noland wrote:
On Sun, 2009-12-13 at 23:21 +0100, Rolf G Nielsen wrote:
Adam Jacob Muller wrote:
Hi,
I'm trying to setup a system with a very large RAID array (total ~10TB), I
would ideally like to have the system boot directly off that 10TB array, so
Hi all,
I am playing with iscsi_initiator on FreeBSD 7-STABLE and Dell
PowerVault MD3000i. This is the first time I am testing iSCSI...
Does anyone have FreeBSD's iSCSI initiator in production / heavy load?
Or does somebody have experiences with Dell MD3000i?
One thing is poor performance ~
On Tuesday 15 December 2009 04:42:06 pm Marian Hettwer wrote:
Hi Folks,
today I did an update from 7.2-RELEASE-p4 to 8.0-RELEASE using
freebsd-update.
Everything went smooth, apart from the fact that I can't mount my second
disk.
It's all a bit puzzling...
Here are the facts:
You are correct. I added the route and it works fine.
route add -inet6 2610:28:1800:4001::/64 -iface em0
Thanks,
Tom
On Dec 15, 2009, at 5:00 PM, Li, Qing wrote:
Thanks for sending me the routing table output.
Actually I believe both your problems are indeed related to the
prefix route.
On Dec 15, 2009, at 2:20 PM, Steven Friedrich wrote:
FreeBSD 8.0 no longer supports dangerously dedicated disks.
This is not true. The problem is that sysinstall creates an invalid
dangerously dedicated disk, as demonstrated by doing:
# fdisk ad8
(shows FreeBSD slice
Hi,
Recently there have been several reports regarding issues with ppp, mpd5
and proxy-arp configuration over the ppp links. I read through the
various postings and the problems seem to be:
1. Unable to add proxy-arp entries for the remote ppp clients.
2. Log showing ifa_add_loopback_route:
Quoth Marcel Moolenaar xcl...@mac.com:
On Dec 15, 2009, at 2:20 PM, Steven Friedrich wrote:
FreeBSD 8.0 no longer supports dangerously dedicated disks.
This is not true. The problem is that sysinstall creates an invalid
dangerously dedicated disk, as demonstrated by doing:
# fdisk
On Tue, Dec 15, 2009 at 4:08 PM, Ben Morrow b...@morrow.me.uk wrote:
Quoth Marcel Moolenaar xcl...@mac.com:
On Dec 15, 2009, at 2:20 PM, Steven Friedrich wrote:
FreeBSD 8.0 no longer supports dangerously dedicated disks.
This is not true. The problem is that sysinstall creates an invalid
On Dec 15, 2009, at 4:08 PM, Ben Morrow wrote:
Quoth Marcel Moolenaar xcl...@mac.com:
On Dec 15, 2009, at 2:20 PM, Steven Friedrich wrote:
FreeBSD 8.0 no longer supports dangerously dedicated disks.
This is not true. The problem is that sysinstall creates an invalid
dangerously
Quoth Xin LI delp...@gmail.com:
On Tue, Dec 15, 2009 at 4:08 PM, Ben Morrow b...@morrow.me.uk wrote:
Are you able to clarify exactly what is no longer working in 8? I've
read things here and there about dangerously dedicated disks no longer
being supported, but no detail about what
Quoth Marcel Moolenaar xcl...@mac.com:
On Dec 15, 2009, at 4:08 PM, Ben Morrow wrote:
Quoth Marcel Moolenaar xcl...@mac.com:
On Dec 15, 2009, at 2:20 PM, Steven Friedrich wrote:
FreeBSD 8.0 no longer supports dangerously dedicated disks.
This is not true. The problem is that
On Wed, 16 Dec 2009, Xin LI wrote:
My $0.02: what about labelling them, say, tunefs -L on UFS
partitions, and glabel for swap, then change corresponding entry in
fstab. Say:
- Start into single user
- tunefs -L root /
- reboot into single user --- reboot required after tuning /
-
Hello!
I have problem with kern.icp.shmseg, when a change value from 128 to 256,
512 in /boot/loader.conf. When system loading the value kern.icp.shmseg
doesn't change.
# cat /boot/loader.conf
# Number of shared memory identifiers
kern.ipc.shmmni=2048
# Number of segments per process #2048
This patch works for me.
On Mon, 14 Dec 2009, Li, Qing wrote:
Please find the more proper fix at
http://people.freebsd.org/~qingli/nd6-patch.diff
I realized I was slightly off in my previous email after
I spent a bit more time looking through the problem.
Both prefixes are present
Hi all,
I am playing with iscsi_initiator on FreeBSD 7-STABLE and Dell
PowerVault MD3000i. This is the first time I am testing iSCSI...
Does anyone have FreeBSD's iSCSI initiator in production / heavy load?
Or does somebody have experiences with Dell MD3000i?
One thing is poor
36 matches
Mail list logo
