Re: failed to create gmirror with the handbook instructions

[Andy Zammy]

I tried creating the mirror before the install. As the drives are now
mirrored, the installer picked up on the face that there are two gm0 nodes
- one on each hard drive. I installed onto ada0's gm0 node.

After it reboots, the bootloader stops at the manual prompt. From what I
can see that's not dissapeared up the screen, it tried and failed to mount
from mirror/gm0s1a with error 19. I had to mount from ada0s1a in order for
the boot to get further, but as it's been installed to boot from gm0s1x, it
stops after it mounts /.

After having checked my partition setup many times at this point, I know
for a fact there's a rather large 500MB section free at the end of my hard
drives with this partition set up. Is there any reason I can't just install
as normal, do a 'gmirror label gm0 ada0', and then do a 'gmirror insert gm0
ada1', before changing my fstab to use mirror/gm0? I can't see why dumping
and restoring is necessary, it's just manually doing what gmirror is there
for in the first place. Correct me if I'm wrong :)


On 9 October 2013 00:11, Warren Block  wrote:

> On Tue, 8 Oct 2013, Andy Zammy wrote:
>
>  # gpart show ada0s1
>> gpart: No such geom: ada0s1
>>
>> By the way, this is after a restart of the machine.
>>
>> There's nothing to back up, I'm installing a fresh os, so I just install
>> on one drive, plug the other in, and start following the handbook
>> instructions for this method. So the only
>> thing in loader.conf is geom_mirror_load="YES".
>>
>> I'll rephrase the question: given that the handbook originally wanted me
>> to dump from ada0s1 to the mounted mirror/gm0s1 (which was ada1 at the
>> time), and I cannot do this, would it be
>> enough to dump from mirror/gm0s1 (which is what ada0 is now mounted as),
>> to ada1s1 (even though this *should* be the other way around, it's
>> equivalent as far as i can see, isn't it?)?
>>
>
> There is not much point in dumping from the mirror to another drive. The
> dump/restore is how the single drive is copied to the mirror.
>
> On a fresh install, use the Shell mode of the installer to set up the
> mirror, then install directly to it.  There are some instructions on
> mountpoints in the bsdinstall man page.  This will avoid the lag of waiting
> for the second drive to sync.
>
___
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: failed to create gmirror with the handbook instructions

[Michael Powell]

Andy Zammy wrote:

> # gpart show ada0s1
> gpart: No such geom: ada0s1
> 
> By the way, this is after a restart of the machine.
> 
> There's nothing to back up, I'm installing a fresh os, so I just install
> on one drive, plug the other in, and start following the handbook
> instructions for this method. So the only thing in loader.conf is
> geom_mirror_load="YES".
> 
[snip]

Since you are beginning to reinstall from scratch, please allow/forgive a 
small interjection from some of my recent experience with this. Warren is 
more knowledgeable on this than I am, and I have followed many of his 
instructions in the past.

With the shift towards GPT and away from the old DOS mbr/partition table stuff 
of the past, the current Handbook pages reflect this. The central point of 
contention arises from the fact that GPT, GEOM (gmirror), and many hardware 
RAID controllers require to claim the very last sector of a drive to store 
their metadata. Obviously, the effect of this collision is a "whoever wrote 
last wrote best" - so you can't use combinations of things that all want 
this sector.

The most simple gmirroring is to slice an entire drive, with partitions 
contained within. The very end of the drive must NOT have any file system on 
it, and this is usually the case by default as most of the time 
slicing/partitioning leaves a little free space at the end anyway. This will 
not work with GPT; only with the old DOS compatible mbr and disklabel 
scheme.

In order to use GPT and gmirror together you gmirror individual partitions 
(as opposed to the slice) , e.g. gmirror will write its metadata at the end 
of each partition leaving the very last sector at the end of the drive for 
GPT. This is what the content on the relevant Handbook pages reflects.   
More complicated, but allows for the demise of the ancient DOS/mbr 
partitioning.

Notice that if you combine GPT and a hardware RAID controller card the same 
collision problem noted previously can still happen. If you utilize the BIOS 
on the controller card for anything it will save its metadata on the last 
drive sector.

When not faced with terabyte sized humongous volumes and the huge amount of 
time an fsck will consume, the old DOS way with disklabel is still an option 
that works. The main reason for the journaling is to sidestep waiting for a 
very long fsck on a huge volume to run to completion before finishing a boot 
into a cleaned up/repaired file system. If your drive volume is small this 
is not so much a problem. Indeed my old gateway/firewall/IDS router box I 
did the old DOS/mbr scheme with gmirror (the old single-slice entire drive 
and mirror the drive) as the pair of drives are ancient 74GB Raptors.

On my web/database test box I did go the GPT and SUJ+journaling route but am 
not using any mirroring here (yet). I have not experienced any problems with 
dump - but I also do not use the -L switch. It will show an error/warning 
about not dumping a live file system this way but I go ahead and do it 
anyway. IIRC the dump problem you may be seeing may be related to drive 
snapshotting. The caveat is I can sort of 'get away' with it as my boxen are 
largely quiescent, but would hesitate to do this on something like a public 
web/database box that was continually being hammered with lots of traffic.

Just tossing out some ideas for your perusal and consideration. The way I 
used the old DOS/mbr and disklabel scheme on my router machine is very 
simple, quick to do, and has survived a few power outages now with no data 
loss (other than the time it takes to rebuild which it does automagically on 
boot). On the 74GB Raptors this rebuild takes about twenty minutes. Your 
situation and needs may force you in a different direction. Hence, the 
proverbial "YMMV" applies. FWIW. Now for to finally get around to purchasing 
a new UPS to replace the old one that went up in smoke and died horribly...

-Mike



___
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: failed to create gmirror with the handbook instructions

[Warren Block]

On Tue, 8 Oct 2013, Andy Zammy wrote:


# gpart show ada0s1
gpart: No such geom: ada0s1

By the way, this is after a restart of the machine.

There's nothing to back up, I'm installing a fresh os, so I just install on one 
drive, plug the other in, and start following the handbook instructions for 
this method. So the only
thing in loader.conf is geom_mirror_load="YES".

I'll rephrase the question: given that the handbook originally wanted me to 
dump from ada0s1 to the mounted mirror/gm0s1 (which was ada1 at the time), and 
I cannot do this, would it be
enough to dump from mirror/gm0s1 (which is what ada0 is now mounted as), to 
ada1s1 (even though this *should* be the other way around, it's equivalent as 
far as i can see, isn't it?)?


There is not much point in dumping from the mirror to another drive. 
The dump/restore is how the single drive is copied to the mirror.


On a fresh install, use the Shell mode of the installer to set up the 
mirror, then install directly to it.  There are some instructions on 
mountpoints in the bsdinstall man page.  This will avoid the lag of 
waiting for the second drive to sync.

___
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: failed to create gmirror with the handbook instructions

[Warren Block]

On Tue, 8 Oct 2013, Andy Zammy wrote:



Thanks very much. Please could I make a suggestion that this be included in the 
handbook page?


Please do not top-post, it makes replies more difficult.

I have added a warning about SUJ to the top of the gmirror section in 
the Handbook.

___
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: failed to create gmirror with the handbook instructions

[Andy Zammy]

# gpart show ada0s1
gpart: No such geom: ada0s1

By the way, this is after a restart of the machine.

There's nothing to back up, I'm installing a fresh os, so I just install on
one drive, plug the other in, and start following the handbook instructions
for this method. So the only thing in loader.conf is geom_mirror_load="YES".

I'll rephrase the question: given that the handbook originally wanted me to
dump from ada0s1 to the mounted mirror/gm0s1 (which was ada1 at the time),
and I cannot do this, would it be enough to dump from mirror/gm0s1 (which
is what ada0 is now mounted as), to ada1s1 (even though this *should* be
the other way around, it's equivalent as far as i can see, isn't it?)?


On 8 October 2013 22:59, Warren Block  wrote:

> On Tue, 8 Oct 2013, Andy Zammy wrote:
>
>  This is actually trickier than it first looked. First I got into single
>> user mode by supplying 'shutdown now', but the tunefs commands all failed
>> with the following:
>> #tunefs -j disable /dev/ada0s1a
>> Clearing journal flags from inode 4
>> tunefs: Failed to write journal inode: Operation not permitted
>> tunefs: soft updates journalling cleared but soft updates still set.
>> tunefs: remove .sujournal to reclaim space
>> tunefs: /dev/ada0s1a: failed to write superblock
>>
>> I tried the dump command on the off-chance, and it failed with the
>> original errors. Is there anything you can recommend?
>>
>> I then noticed you specified to boot into single user more, so I
>> restarted the machine, with only ada0 attached. Because the handbook wants
>> me to use the mirror/gm0sX devices, I swapped
>> my fstab file back to the original. The boot loader now only seems to
>> recognise the mirror/gm0 nodes, the original ada0sX are gone (though ada0
>> still shows up).
>>
>
> I don't know what would do that.  The device nodes on the original drive
> should be untouched until it is added back to the mirror.  What does
>   gpart show ada0s1
> show?  Did you make a backup of the original drive first?  Is there an
> entry for vfs.root.mountfrom in /boot/loader.conf?
>
>  I'm not sure if it's acceptable to do the dump by booting the 1st hard
>> drive using the mirror/gm0, and then dump to the 2nd hard drive by mounting
>> what will be ada1sX. Is this okay to do?
>>
>
> Sorry, I don't quite understand the question.  The mirror will not be
> usable until a good copy of the original drive is made to it.
>
___
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: failed to create gmirror with the handbook instructions

[Warren Block]

On Tue, 8 Oct 2013, Andy Zammy wrote:


This is actually trickier than it first looked. First I got into single user 
mode by supplying 'shutdown now', but the tunefs commands all failed with the 
following:
#tunefs -j disable /dev/ada0s1a
Clearing journal flags from inode 4
tunefs: Failed to write journal inode: Operation not permitted
tunefs: soft updates journalling cleared but soft updates still set.
tunefs: remove .sujournal to reclaim space
tunefs: /dev/ada0s1a: failed to write superblock

I tried the dump command on the off-chance, and it failed with the original 
errors. Is there anything you can recommend?

I then noticed you specified to boot into single user more, so I restarted the 
machine, with only ada0 attached. Because the handbook wants me to use the 
mirror/gm0sX devices, I swapped
my fstab file back to the original. The boot loader now only seems to recognise 
the mirror/gm0 nodes, the original ada0sX are gone (though ada0 still shows up).


I don't know what would do that.  The device nodes on the original drive
should be untouched until it is added back to the mirror.  What does
  gpart show ada0s1
show?  Did you make a backup of the original drive first?  Is there an 
entry for vfs.root.mountfrom in /boot/loader.conf?


I'm not sure if it's acceptable to do the dump by booting the 1st hard 
drive using the mirror/gm0, and then dump to the 2nd hard drive by 
mounting what will be ada1sX. Is this okay to do?


Sorry, I don't quite understand the question.  The mirror will not be 
usable until a good copy of the original drive is made to it.

___
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: failed to create gmirror with the handbook instructions

[Andy Zammy]

I
On 8 October 2013 01:31, Warren Block  wrote:

> On Tue, 8 Oct 2013, Andy Zammy wrote:
>
>  Hi,
>>
>> I used the second section of the handbook (20.4) to create a gmirror. In
>> my
>> particular setup I had a 1GB /, 6GB swap, 1GB /tmp and the rest of the 1TB
>> drive was left for /usr
>>
>> I had to deviate from the handbook when it came to running the dump +
>> restore commands, as the dump failed due to an issue with the journalling.
>> To get around this problem, I dropped into single user mode, so I could
>> remount root as read-only. The dump commands then worked. It specified in
>> the handbook to restart the machine, and boot from ada1.
>>
>> It was at this point that I noticed something wasn't quite right. There
>> was
>> a spew of 'not found/no such file or directory' messages. These were all
>> trying to reference libs and binaries that live in /usr.
>>
>> I boot into single user mode, and upon checking the other partitions, I
>> notice that /tmp and /usr are empty, apart from a .snap file, and the
>> restoresymtable file.
>>
>> Please could someone help me troubleshoot this problem? Let me know if you
>> need any more info, and I'll post it up asap.
>>
>
> dump does not work reliably on filesystems with SUJ enabled.  Turn off SUJ
> on the filesystems to be dumped by booting in single-user mode and running
>   tunefs -j disable /dev/ada0whatever
>
> Do each filesystem, then use dump.
>
___
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: failed to create gmirror with the handbook instructions

[Andy Zammy]

This is actually trickier than it first looked. First I got into single
user mode by supplying 'shutdown now', but the tunefs commands all failed
with the following:
#tunefs -j disable /dev/ada0s1a
Clearing journal flags from inode 4
tunefs: Failed to write journal inode: Operation not permitted
tunefs: soft updates journalling cleared but soft updates still set.
tunefs: remove .sujournal to reclaim space
tunefs: /dev/ada0s1a: failed to write superblock

I tried the dump command on the off-chance, and it failed with the original
errors. Is there anything you can recommend?

I then noticed you specified to boot into single user more, so I restarted
the machine, with only ada0 attached. Because the handbook wants me to use
the mirror/gm0sX devices, I swapped my fstab file back to the original. The
boot loader now only seems to recognise the mirror/gm0 nodes, the original
ada0sX are gone (though ada0 still shows up). I'm not sure if it's
acceptable to do the dump by booting the 1st hard drive using the
mirror/gm0, and then dump to the 2nd hard drive by mounting what will be
ada1sX. Is this okay to do?


On 8 October 2013 01:31, Warren Block  wrote:

> On Tue, 8 Oct 2013, Andy Zammy wrote:
>
>  Hi,
>>
>> I used the second section of the handbook (20.4) to create a gmirror. In
>> my
>> particular setup I had a 1GB /, 6GB swap, 1GB /tmp and the rest of the 1TB
>> drive was left for /usr
>>
>> I had to deviate from the handbook when it came to running the dump +
>> restore commands, as the dump failed due to an issue with the journalling.
>> To get around this problem, I dropped into single user mode, so I could
>> remount root as read-only. The dump commands then worked. It specified in
>> the handbook to restart the machine, and boot from ada1.
>>
>> It was at this point that I noticed something wasn't quite right. There
>> was
>> a spew of 'not found/no such file or directory' messages. These were all
>> trying to reference libs and binaries that live in /usr.
>>
>> I boot into single user mode, and upon checking the other partitions, I
>> notice that /tmp and /usr are empty, apart from a .snap file, and the
>> restoresymtable file.
>>
>> Please could someone help me troubleshoot this problem? Let me know if you
>> need any more info, and I'll post it up asap.
>>
>
> dump does not work reliably on filesystems with SUJ enabled.  Turn off SUJ
> on the filesystems to be dumped by booting in single-user mode and running
>   tunefs -j disable /dev/ada0whatever
>
> Do each filesystem, then use dump.
>
___
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: failed to create gmirror with the handbook instructions

[Andy Zammy]

Thanks very much. Please could I make a suggestion that this be included in
the handbook page?
On 8 Oct 2013 01:31, "Warren Block"  wrote:

> On Tue, 8 Oct 2013, Andy Zammy wrote:
>
>  Hi,
>>
>> I used the second section of the handbook (20.4) to create a gmirror. In
>> my
>> particular setup I had a 1GB /, 6GB swap, 1GB /tmp and the rest of the 1TB
>> drive was left for /usr
>>
>> I had to deviate from the handbook when it came to running the dump +
>> restore commands, as the dump failed due to an issue with the journalling.
>> To get around this problem, I dropped into single user mode, so I could
>> remount root as read-only. The dump commands then worked. It specified in
>> the handbook to restart the machine, and boot from ada1.
>>
>> It was at this point that I noticed something wasn't quite right. There
>> was
>> a spew of 'not found/no such file or directory' messages. These were all
>> trying to reference libs and binaries that live in /usr.
>>
>> I boot into single user mode, and upon checking the other partitions, I
>> notice that /tmp and /usr are empty, apart from a .snap file, and the
>> restoresymtable file.
>>
>> Please could someone help me troubleshoot this problem? Let me know if you
>> need any more info, and I'll post it up asap.
>>
>
> dump does not work reliably on filesystems with SUJ enabled.  Turn off SUJ
> on the filesystems to be dumped by booting in single-user mode and running
>   tunefs -j disable /dev/ada0whatever
>
> Do each filesystem, then use dump.
>
___
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: failed to create gmirror with the handbook instructions

[Warren Block]

On Tue, 8 Oct 2013, Andy Zammy wrote:


Hi,

I used the second section of the handbook (20.4) to create a gmirror. In my
particular setup I had a 1GB /, 6GB swap, 1GB /tmp and the rest of the 1TB
drive was left for /usr

I had to deviate from the handbook when it came to running the dump +
restore commands, as the dump failed due to an issue with the journalling.
To get around this problem, I dropped into single user mode, so I could
remount root as read-only. The dump commands then worked. It specified in
the handbook to restart the machine, and boot from ada1.

It was at this point that I noticed something wasn't quite right. There was
a spew of 'not found/no such file or directory' messages. These were all
trying to reference libs and binaries that live in /usr.

I boot into single user mode, and upon checking the other partitions, I
notice that /tmp and /usr are empty, apart from a .snap file, and the
restoresymtable file.

Please could someone help me troubleshoot this problem? Let me know if you
need any more info, and I'll post it up asap.


dump does not work reliably on filesystems with SUJ enabled.  Turn off 
SUJ on the filesystems to be dumped by booting in single-user mode and 
running

  tunefs -j disable /dev/ada0whatever

Do each filesystem, then use dump.
___
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"

failed to create gmirror with the handbook instructions

[Andy Zammy]

Hi,

I used the second section of the handbook (20.4) to create a gmirror. In my
particular setup I had a 1GB /, 6GB swap, 1GB /tmp and the rest of the 1TB
drive was left for /usr

I had to deviate from the handbook when it came to running the dump +
restore commands, as the dump failed due to an issue with the journalling.
To get around this problem, I dropped into single user mode, so I could
remount root as read-only. The dump commands then worked. It specified in
the handbook to restart the machine, and boot from ada1.

It was at this point that I noticed something wasn't quite right. There was
a spew of 'not found/no such file or directory' messages. These were all
trying to reference libs and binaries that live in /usr.

I boot into single user mode, and upon checking the other partitions, I
notice that /tmp and /usr are empty, apart from a .snap file, and the
restoresymtable file.

Please could someone help me troubleshoot this problem? Let me know if you
need any more info, and I'll post it up asap.

Kind Regards

Andy
___
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: UPDATING 20120116 -- x11/xcb-util -- instructions not working

[Conrad J. Sabatier]

On Thu, 26 Jan 2012 06:06:57 -0500
Michael Powell  wrote:

> Conrad J. Sabatier wrote:
> 
> > On Wed, 25 Jan 2012 08:53:39 -0600
> > Mark Felder  wrote:
> > 
> >> For the life of me I can't work around this xcb-util issue. This is
> >> a pretty fresh install and I have not made any workaround symlinks.
> >> 
> >> I ran:
> >> 
> >> # portmaster -R -r xcb-util-0
> >> 
> >> And the problem persists. It didn't even complete all the packages
> >> because some were still erroring on missing xcb libraries.
> >> 
> >> Example, editors/mousepad:
> >> 
> >> 
> >> libtool: link: cannot find the library
> >> `/usr/local/lib/libxcb-aux.la' or unhandled argument
> >> `/usr/local/lib/libxcb-aux.la' gmake[2]: *** [mousepad] Error 1
> > 
> > I'm getting this same error in several ports.  Just exactly which
> > package is supposed to be providing libxcb-aux.la?  And why isn't
> > it?
> > 
> 
> I'm not exactly certain about this, and so am probably wrong. I
> thought the '*.la' files were 'linker archives' created by libtool.

Yes, that's right.

> But I never really got completely through the process of fully
> understanding exactly how all the autotools, make and gmake, and
> libtool operate.

I did some research on this issue yesterday, and found the answer.  I
posted a complete explanation with step-by-step instructions to the
FreeBSD Forums at:

http://forums.FreeBSD.org/showthread.php?p=163415#post163415

Sorry, I should have followed up here sooner as well.  :-)

-- 
Conrad J. Sabatier
conr...@cox.net
___
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: UPDATING 20120116 -- x11/xcb-util -- instructions not working

[Michael Powell]

Conrad J. Sabatier wrote:

> On Wed, 25 Jan 2012 08:53:39 -0600
> Mark Felder  wrote:
> 
>> For the life of me I can't work around this xcb-util issue. This is
>> a pretty fresh install and I have not made any workaround symlinks.
>> 
>> I ran:
>> 
>> # portmaster -R -r xcb-util-0
>> 
>> And the problem persists. It didn't even complete all the packages
>> because some were still erroring on missing xcb libraries.
>> 
>> Example, editors/mousepad:
>> 
>> 
>> libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la'
>> or unhandled argument `/usr/local/lib/libxcb-aux.la'
>> gmake[2]: *** [mousepad] Error 1
> 
> I'm getting this same error in several ports.  Just exactly which
> package is supposed to be providing libxcb-aux.la?  And why isn't it?
> 

I'm not exactly certain about this, and so am probably wrong. I thought the 
'*.la' files were 'linker archives' created by libtool. But I never really 
got completely through the process of fully understanding exactly how all 
the autotools, make and gmake, and libtool operate.

-Mike


___
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: UPDATING 20120116 -- x11/xcb-util -- instructions not working

[Conrad J. Sabatier]

On Wed, 25 Jan 2012 08:53:39 -0600
Mark Felder  wrote:

> For the life of me I can't work around this xcb-util issue. This is
> a pretty fresh install and I have not made any workaround symlinks.
> 
> I ran:
> 
> # portmaster -R -r xcb-util-0
> 
> And the problem persists. It didn't even complete all the packages
> because some were still erroring on missing xcb libraries.
> 
> Example, editors/mousepad:
> 
> 
> libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la'
> or unhandled argument `/usr/local/lib/libxcb-aux.la'
> gmake[2]: *** [mousepad] Error 1

I'm getting this same error in several ports.  Just exactly which
package is supposed to be providing libxcb-aux.la?  And why isn't it?

-- 
Conrad J. Sabatier
conr...@cox.net
___
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: UPDATING 20120116 -- x11/xcb-util -- instructions not working

[Mark Felder]

On 25.01.2012 09:52, Mark wrote:


I got stuck in this hell the other day, I had to do this.

 "portmaster --check-depends"

 to see if anything is missing

then

 "portmaster -a -f"



I want to report back that this did end up working pretty darn well. 
:-)  THANKS!


___
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: UPDATING 20120116 -- x11/xcb-util -- instructions not working

[Jakub Lach]

Try rebuilding libtool first.

--
View this message in context: 
http://freebsd.1045724.n5.nabble.com/UPDATING-20120116-x11-xcb-util-instructions-not-working-tp5430407p5431468.html
Sent from the freebsd-questions mailing list archive at Nabble.com.
___
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"

UPDATING 20120116 -- x11/xcb-util -- instructions not working

[Mark Felder]

For the life of me I can't work around this xcb-util issue. This is a  
pretty fresh install and I have not made any workaround symlinks.


I ran:

# portmaster -R -r xcb-util-0

And the problem persists. It didn't even complete all the packages because  
some were still erroring on missing xcb libraries.


Example, editors/mousepad:


libtool: link: cannot find the library `/usr/local/lib/libxcb-aux.la' or  
unhandled argument `/usr/local/lib/libxcb-aux.la'

gmake[2]: *** [mousepad] Error 1
gmake[2]: Leaving directory  
`/usr/ports/editors/mousepad/work/mousepad-0.2.16/src'

gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory  
`/usr/ports/editors/mousepad/work/mousepad-0.2.16'

gmake: *** [all] Error 2
*** Error code 1


Is there a solution I'm missing? I'd really like to get this resolved  
today so all my programs work again :P

___
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: Instructions on Installing HP LaserJet P1102 on FreeBSD 8 (solved)

[Julian H. Stacey]

Bahman Kahinpour wrote:
> After going through a hard time on installing HP LaserJet P1102 on
> FreeBSD 8.1, I decided to write this.
> 
> *** Installing HP LaserJet P1102 on FreeBSD 8.1 ***

Nice, Well done for documenting :-)  I dont have such a printer
myself, but seems valuable, probably applies to similar printers
too).  Text should not just rot as mail hard to find in the archive,
but be submitted with send-pr.  But to which section ?

For ports ? for print/cups/files/README.something ?  
Or more likely for www ? for under
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/printing.html
Or in ?
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/printing-advanced.html

Please run send-pr so it gets saved somewhere :-)

Cheers,
Julian
-- 
Julian Stacey, BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com
 Mail plain text;  Not quoted-printable, Not HTML, Not base 64.
 Reply below text sections not at top, to avoid breaking cumulative context.
___
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: Instructions on Installing HP LaserJet P1102 on FreeBSD 8 (solved)

[Polytropon]

Allow me a little sidenote:

On Sat, 29 Jan 2011 00:48:31 +0330, Bahman Kahinpour  
wrote:
>  ** PART THREE: Install FOO2ZJS from FOO2ZJS.RKKDA.COM **
> 
> foo2zjs in the Ports Collection is a little old and it does not work
> with HP LaserJet P1102. (Checked Jan 29,2011) Go to foo2zjs.rkkda.com
> and download http://foo2zjs.rkkda.com/foo2zjs.tar.gz.
> 
> # cd ~

The ~ is not needed. The command "cd" without any
parameters will bring you to your home directory.
For more typing, use "cd $HOME". :-)



And of course:

> The printer has a built-in fake CD-ROM feature which prevents it from
> working correctly on non-Windows PCs. Once it is connected to a
> Windows PC, a CD-ROM appears containing Windows drivers. In order for
> HP LaserJet P1102 to work correctly on a FreeBSD PC, you must disable
> this feature.

Correct: You must work around this bug (it's not a feature). :-)



> 1.Connect the printer to a Windows PC. (Unfortunately you have to
> connect it to a Windows PC which is too bad.)

This would be reason enough for me to kick the thing out
of the window. :-)



> 2.Insert the original driver CD. (The physical CD-ROM that ships with
> the product, NOT THIS FAKE CD-ROM).
> 3.Run SIUtility.exe or SIUtility64.exe from UTIL folder to disable
> this fake CD feature. (It's called “HP Smart Install”

Yeah, very smart. Deliver incompatible (defective!) stuff and
require a proprietary program for an obscure OS imitation to
fix the thing... refer to "kick out of the window" for further
proceeding. :-)



> Plug out your printer and plug it in again. (In order for the
> permission in the devfs to be correct. They should be writable for the
> printer nodes in the /dev)

A more technical note, or question: If I remember correctly,
CUPS introduces a "cups" or "usb" group to the system. Did
you check if it is needed to work with that group in order
to get the required permissions for the ulpt device?


I will definitely NOT buy this printer, but good to know that
it is at least possible (with hard work not common to UNIX
operations) to make it work.

Thank you for your little HOWTO, I will keep it in mind - and
hope I *never* will have to deal with such a "printer". :-)




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
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"

Instructions on Installing HP LaserJet P1102 on FreeBSD 8 (solved)

[Bahman Kahinpour]

After going through a hard time on installing HP LaserJet P1102 on
FreeBSD 8.1, I decided to write this.

*** Installing HP LaserJet P1102 on FreeBSD 8.1 ***

Note: HPLIP 3.10.9 doesn't work for this printer.

** PART ONE: Disable the fake CD-ROM feature **

The printer has a built-in fake CD-ROM feature which prevents it from
working correctly on non-Windows PCs. Once it is connected to a
Windows PC, a CD-ROM appears containing Windows drivers. In order for
HP LaserJet P1102 to work correctly on a FreeBSD PC, you must disable
this feature.

1.Connect the printer to a Windows PC. (Unfortunately you have to
connect it to a Windows PC which is too bad.)
2.Insert the original driver CD. (The physical CD-ROM that ships with
the product, NOT THIS FAKE CD-ROM).
3.Run SIUtility.exe or SIUtility64.exe from UTIL folder to disable
this fake CD feature. (It's called “HP Smart Install”

Now, life becomes easier. Connect your HP LaserJet P1102 to your
FreeBSD PC. Printer should be recognized and /dev/ulpt0 appears.

** PART TWO: Install CUPS and FOOMATIC-FILTERS **

1.Update your Ports Collection tree.
2.Install Common Unix Printing System (CUPS).

# cd /usr/ports/print/cups
# make install clean

3.Add cupsd_enable=”YES” to /etc/rc.conf

# ee /etc/rc.conf

4.Start CUPS now. (You do not need to restart your FreeBSD)

# /usr/local/etc/rc.d/cupsd start

4.Install Foomatic Filters.

# cd /usr/ports/print/foomatic-filters
# make install clean

 ** PART THREE: Install FOO2ZJS from FOO2ZJS.RKKDA.COM **

foo2zjs in the Ports Collection is a little old and it does not work
with HP LaserJet P1102. (Checked Jan 29,2011) Go to foo2zjs.rkkda.com
and download http://foo2zjs.rkkda.com/foo2zjs.tar.gz.

# cd ~
# wget http://foo2zjs.rkkda.com/foo2zjs.tar.gz
# gzip -dc foo2zjs.tar.gz | tar -xvf -
# cd foo2zjs
# gmake
# gmake install
# gmake install-hotplug
# ./freebsd-install

Please note that you do not need any firmware download for this
printer. (Any of these ./getweb stuff) Now restart the CUPS.

# gmake cups

Now, make sure that your printer is recognized on your FreeBSD system.
Check dmesg and verify that printer is recognized. Make sure that
/dev/ulpt0 exists.

Plug out your printer and plug it in again. (In order for the
permission in the devfs to be correct. They should be writable for the
printer nodes in the /dev)

Now, open your browser and goto http://localhost:631. Click on the
Administration and Add Printer. Your printer should be recognized and
also there is a special filter (driver) for that in the next pages.

Use /dev/ulpt0 as the URI.

Good Luck
Bahman Kahinpour
___
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: MySQL 5.5.7->5.5.8 instructions seem scary

[Bryan H.]

Oops, forgot the reply-all.  :X  Sorry Bill.  :)

I ran the update two nights ago, and it went rather smoothly for me
(updating from the 5.5.7 RC to 5.5.8 GA), but your mileage may vary.

Additionally, you can find some general rules for updating your MySQL
install here:  http://dev.mysql.com/doc/refman/5.5/en/upgrading.html

As the others recommended, backups are critical!

On Wed, Dec 29, 2010 at 8:10 AM, Bill Moran wrote:

> In response to Odhiambo Washington :
>
> > On Wed, Dec 29, 2010 at 1:57 PM, Nerius Landys 
> wrote:
> >
> > > I read this in /usr/ports/UPDATING today:
> > >
> > > =
> > > 20101227:
> > >  AFFECTS: users of databases/mysql55-server
> > >  AUTHOR: a...@freebsd.org
> > >
> > >  MySQL 5.5 has been updated to 5.5.8 GA release. Since layout is
> > >  changed you should remove mysql55-{client/server/scripts} ports
> > >  before upgrading. The build system is changed too, so expect
> > >  failures.
> > > =
> > >
> > >
> > > Now that seems pretty scary.  Remove all mysql packages from my
> system?!?!
> > > Expect failures?!?!?
> > >
> > > I have important data in my current mysql install.
> > >
> > If there is no reason for you to run it, then keep off.
> > Otherwise backup your DB and follow the instructions:-)
>
> Better yet, make a jail, install the version of MySQL you're currently
> using and copy your data over, then practice upgrading in the jail.
> Once you have the procedure figured out, you can execute it on the
> production system with a high level of confidence.
>
> --
> Bill Moran
> http://www.potentialtech.com
> http://people.collaborativefusion.com/~wmoran/
> ___
> 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"
>
___
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: MySQL 5.5.7->5.5.8 instructions seem scary

[Bill Moran]

In response to Odhiambo Washington :

> On Wed, Dec 29, 2010 at 1:57 PM, Nerius Landys  wrote:
> 
> > I read this in /usr/ports/UPDATING today:
> >
> > =
> > 20101227:
> >  AFFECTS: users of databases/mysql55-server
> >  AUTHOR: a...@freebsd.org
> >
> >  MySQL 5.5 has been updated to 5.5.8 GA release. Since layout is
> >  changed you should remove mysql55-{client/server/scripts} ports
> >  before upgrading. The build system is changed too, so expect
> >  failures.
> > =
> >
> >
> > Now that seems pretty scary.  Remove all mysql packages from my system?!?!
> > Expect failures?!?!?
> >
> > I have important data in my current mysql install.
> >
> If there is no reason for you to run it, then keep off.
> Otherwise backup your DB and follow the instructions:-)

Better yet, make a jail, install the version of MySQL you're currently
using and copy your data over, then practice upgrading in the jail.
Once you have the procedure figured out, you can execute it on the
production system with a high level of confidence.

-- 
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
___
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: MySQL 5.5.7->5.5.8 instructions seem scary

[Odhiambo Washington]

On Wed, Dec 29, 2010 at 1:57 PM, Nerius Landys  wrote:

> I read this in /usr/ports/UPDATING today:
>
> =
> 20101227:
>  AFFECTS: users of databases/mysql55-server
>  AUTHOR: a...@freebsd.org
>
>  MySQL 5.5 has been updated to 5.5.8 GA release. Since layout is
>  changed you should remove mysql55-{client/server/scripts} ports
>  before upgrading. The build system is changed too, so expect
>  failures.
> =
>
>
> Now that seems pretty scary.  Remove all mysql packages from my system?!?!
> Expect failures?!?!?
>
> I have important data in my current mysql install.
>
>
If there is no reason for you to run it, then keep off.
Otherwise backup your DB and follow the instructions:-)



-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Damn!!
___
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"

MySQL 5.5.7->5.5.8 instructions seem scary

[Nerius Landys]

I read this in /usr/ports/UPDATING today:

=
20101227:
  AFFECTS: users of databases/mysql55-server
  AUTHOR: a...@freebsd.org

  MySQL 5.5 has been updated to 5.5.8 GA release. Since layout is
  changed you should remove mysql55-{client/server/scripts} ports
  before upgrading. The build system is changed too, so expect
  failures.
=


Now that seems pretty scary.  Remove all mysql packages from my system?!?!
Expect failures?!?!?

I have important data in my current mysql install.

porky/zsh# pkg_info -Qao | grep -i mysql
mysql-client-5.5.7:databases/mysql55-client
mysql-server-5.5.7:databases/mysql55-server
php5-mysql-5.3.4:databases/php5-mysql

Should I wait until things settle down before upgrading?
I need better instruction on how to upgrade.
___
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: rc.conf: gnome_enable="YES" - which instructions executed?

[RW]

On Wed, 30 Jun 2010 22:03:04 -0700 (PDT)
Chris Stankevitz  wrote:

> I would like to learn more about how rc operates.  I want to know
> where on the hard drive the instructions are located that activate
> when I say gnome_enable="YES".  I naively thought I would find a file
> called "/usr/local/etc/rc.d/gnome" -- but I did not.  Something more
> complicated is going on.  So my question is -- how is this working?

Normally it works they way you thought it did - this is special case. 

Mostly "*_enable" variables are defaulted to NO, but those five scripts
set their default from gnome_enable, which in turn is defaulted to NO.

By setting  gnome_enable="YES" you can start all the daemons that Gnome
needs without having to know which they are, and without having to keep
track of them as Gnome is upgraded. And you can still turn-off things
you don't want e.g.:

gnome_enable=YES
gdm_enable=NO
___
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: rc.conf: gnome_enable="YES" - which instructions executed?

[Robert Bonomi]

> Date: Wed, 30 Jun 2010 21:10:41 -0700 (PDT)
> From: Chris Stankevitz 
> Subject: rc.conf: gnome_enable="YES" - which instructions executed?
>
> My rc.conf file has this entry: gnome_enable="YES"
>
> Q: Where on my hard drive can I find the instructions executed to "enable" 
> GNOME?
>
> A: /usr/local/etc/rc.d/gnome [bad answer: file does not exist]

rc.conf is sourced by -every- script in the rc.d directory.

cd /etc/rc.d
grep gnome_enable *

should give some hints.


___
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: rc.conf: gnome_enable="YES" - which instructions executed?

[Giorgos Keramidas]

On Wed, 30 Jun 2010 21:10:41 -0700 (PDT), Chris Stankevitz 
 wrote:
> My rc.conf file has this entry: gnome_enable="YES"
>
> Q: Where on my hard drive can I find the instructions executed to "enable" 
> GNOME?
>
> A: /usr/local/etc/rc.d/gnome [bad answer: file does not exist]

gnome_enable is a 'default' option that enables some services that make
GNOME desktop experience a bit more useful & pleasurable.  You can see
which services default to "YES" by running:

keram...@kobe:/home/keramida$ cd /usr/local/etc/rc.d
keram...@kobe:/usr/local/etc/rc.d$ fgrep -l gnome_enable *
avahi-daemon
avahi-dnsconfd
dbus
gdm
hald
keram...@kobe:/usr/local/etc/rc.d$

___
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: rc.conf: gnome_enable="YES" - which instructions executed?

[Kevin Kinsey]

Chris Stankevitz wrote:

From: Rob Farmer 

Q: Where on my hard drive can I find the instructions

executed to "enable" GNOME?

This enables dbus, avahi, hal, and gdm (assuming that they
are installed, of course). See the files for those things in
/usr/local/etc/rc.d for the details of what is run.

See:
http://www.freebsd.org/gnome/docs/faq2.html#full-gnome


Rob,

Thank you for your response.  I also saw that comment in

> the docs; however, I am actually not interested in knowing
> what gnome_enable="YES" does.  I should have been more clear.


I would like to learn more about how rc operates.  I want

> to know where on the hard drive the instructions are

located that activate when I say gnome_enable="YES".

> I naively thought I would find a file called "/usr/local/etc/rc.d/gnome"
>  -- but I did not.  Something more complicated is going
> on.  So my question is -- how is this working?


Thank you,



Err, Magic?

More seriously, `man rc` and several hours of cross-references
(rc.subr., rc.conf., rc.local, etc. etc.) might be enlightening.

HTH,

Kevin Kinsey
___
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: rc.conf: gnome_enable="YES" - which instructions executed?

[Chris Stankevitz]

> From: Rob Farmer 
> >
> > Q: Where on my hard drive can I find the instructions
> executed to "enable" GNOME?
> 
> This enables dbus, avahi, hal, and gdm (assuming that they
> are
> installed, of course). See the files for those things in
> /usr/local/etc/rc.d for the details of what is run.
> 
> See:
> http://www.freebsd.org/gnome/docs/faq2.html#full-gnome

Rob,

Thank you for your response.  I also saw that comment in the docs; however, I 
am actually not interested in knowing what gnome_enable="YES" does.  I should 
have been more clear.

I would like to learn more about how rc operates.  I want to know where on the 
hard drive the instructions are located that activate when I say 
gnome_enable="YES".  I naively thought I would find a file called 
"/usr/local/etc/rc.d/gnome" -- but I did not.  Something more complicated is 
going on.  So my question is -- how is this working?

Thank you,

Chris


  
___
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: rc.conf: gnome_enable="YES" - which instructions executed?

[Chris Stankevitz]

> From: Dan Nelson 
> > Q: Where on my hard drive can I find the instructions
> >executed to "enable" GNOME?
> 
> Try:
> 
> grep "name=.*gnome" /usr/local/etc/rc.d/*

Thank you.  This command returns nothing, but it got me looking in the right 
place.

There are multiple references to gnome_enable within files in this directory: 
/usr/local/etc/rc.d/

The references appear like so:

grep gnome /usr/local/etc/rc.d/*
hald:. /usr/local/etc/gnome.subr
hald:hald_enable=${hald_enable-${gnome_enable}}

Thank you,

Chris


  
___
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: rc.conf: gnome_enable="YES" - which instructions executed?

[Rob Farmer]

On Wed, Jun 30, 2010 at 9:10 PM, Chris Stankevitz
 wrote:
> My rc.conf file has this entry: gnome_enable="YES"
>
> Q: Where on my hard drive can I find the instructions executed to "enable" 
> GNOME?

This enables dbus, avahi, hal, and gdm (assuming that they are
installed, of course). See the files for those things in
/usr/local/etc/rc.d for the details of what is run.

See:
http://www.freebsd.org/gnome/docs/faq2.html#full-gnome

-- 
Rob Farmer

>
> A: /usr/local/etc/rc.d/gnome [bad answer: file does not exist]
>
> Thank you,
>
> Chris
>
>
>
>
> ___
> 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"
>
___
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: rc.conf: gnome_enable="YES" - which instructions executed?

[Dan Nelson]

In the last episode (Jun 30), Chris Stankevitz said:
> My rc.conf file has this entry: gnome_enable="YES"
> 
> Q: Where on my hard drive can I find the instructions executed to "enable" 
> GNOME?
> 
> A: /usr/local/etc/rc.d/gnome [bad answer: file does not exist]
> 
> Thank you,

Try:

grep "name=.*gnome" /usr/local/etc/rc.d/*

Most rc scripts are named the same as their rc.subr enable_* variables, but
they don't have to be.  If no rc.d scripts have "name=gnome" in them, then
your gnome_enable line doesn't do a thing.  Maybe you had installed a port
at some point in the past that required it, but the port has been
uninstalled since then?

-- 
Dan Nelson
dnel...@allantgroup.com
___
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"

rc.conf: gnome_enable="YES" - which instructions executed?

[Chris Stankevitz]

My rc.conf file has this entry: gnome_enable="YES"

Q: Where on my hard drive can I find the instructions executed to "enable" 
GNOME?

A: /usr/local/etc/rc.d/gnome [bad answer: file does not exist]

Thank you,

Chris



  
___
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: Where do I find instructions on how to configure sane-epkowa

[Warren Block]

On Thu, 31 Dec 2009, Leslie Jensen wrote:



On 2009-12-31 12:04, Roland Smith wrote:

On Thu, Dec 31, 2009 at 12:06:20AM +0100, Leslie Jensen wrote:


my dll.conf:


Personally, I would only leave in the backends that I actually use.


What do you mean?




epkowa.conf

usb 0x04b8 0x0130


For my non-epkowa Epson, I had

usb /dev/ugen2.3

Maybe that doesn't matter.  There is a page that talks about using the 
epkowa driver on Linux with some possibly relevant information:


http://www.mnsoft.org/scanner_on_linux.0.html

-Warren Block * Rapid City, South Dakota USA
___
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: Where do I find instructions on how to configure sane-epkowa

[Leslie Jensen]

On 2009-12-31 17:05, Roland Smith wrote:

On Thu, Dec 31, 2009 at 04:27:12PM +0100, Leslie Jensen wrote:


I did a

sane-find-scanner -v -v






According to
[http://www.sane-project.org/lists/sane-backends-external.html#S-EPKOWA],
your scanner "requires DFSG non-free iscan-plugin-gt-x770". Not sure what that
means, though.


Neither do I. I'll ask on the sane-devel list.



And according to /usr/ports/graphics/sane-epkowa/Makefile, the latest version
of the driver doesn't work yet because of runtime issues, so it builds an
earlier version. It could just be that this version does not support your
scanner yet.


Maybe! I'm usually not reading the Makefile, but in this case I can see 
the benefits ;-) Thanks for pointing it out.




Maybe you should contact the port maintainer.

Roland




/Leslie

___
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: Where do I find instructions on how to configure sane-epkowa

[Roland Smith]

On Thu, Dec 31, 2009 at 04:27:12PM +0100, Leslie Jensen wrote:
> 
> I did a
> 
> sane-find-scanner -v -v

>  EPSON Scanner)>

According to
[http://www.sane-project.org/lists/sane-backends-external.html#S-EPKOWA], 
your scanner "requires DFSG non-free iscan-plugin-gt-x770". Not sure what that
means, though.

And according to /usr/ports/graphics/sane-epkowa/Makefile, the latest version
of the driver doesn't work yet because of runtime issues, so it builds an
earlier version. It could just be that this version does not support your
scanner yet.

Maybe you should contact the port maintainer.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpx0qv7uEb2B.pgp
Description: PGP signature

Re: Where do I find instructions on how to configure sane-epkowa

[Leslie Jensen]

I did a

sane-find-scanner -v -v

I've pasted what's relevant for the scanner.


This is sane-find-scanner from sane-backends 1.0.20

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

searching for SCSI scanners:
checking /dev/scanner... failed to open (Invalid argument)
checking /dev/scanner0... failed to open (Invalid argument)
checking /dev/scanner1... failed to open (Invalid argument)
checking /dev/pass0... open ok
  Inquiry for device:
000: 05 80 00 32 5b 00 00 00 50 4c 44 53 20 20 20 20 
...2[...PLDS
016: 44 56 44 2b 2d 52 57 20 44 55 2d 38 41 32 53 20DVD+-RW 
DU-8A2S
032: 34 44 31 33 00 00 00 00 00 00 00 00 00 00 00 00 
4D13
048: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

064: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 

080: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 


found SCSI CD-drive "PLDS DVD+-RW DU-8A2S 4D13" at /dev/pass0
checking /dev/pass1... failed to open (Invalid argument)
checking /dev/pass2... failed to open (Invalid argument)
checking /dev/pass3... failed to open (Invalid argument)
checking /dev/pass4... failed to open (Invalid argument)
checking /dev/pass5... failed to open (Invalid argument)
checking /dev/pass6... failed to open (Invalid argument)
checking /dev/pass7... failed to open (Invalid argument)
  # Your SCSI scanner was detected. It may or may not be supported by 
SANE. Try

  # scanimage -L and read the backend's manpage.

searching for USB scanners:
checking /dev/uscanner... failed to open (Invalid argument)
checking /dev/uscanner0... failed to open (Invalid argument)
checking /dev/uscanner1... failed to open (Invalid argument)
checking /dev/uscanner2... failed to open (Invalid argument)
checking /dev/uscanner3... failed to open (Invalid argument)
checking /dev/uscanner4... failed to open (Invalid argument)
checking /dev/uscanner5... failed to open (Invalid argument)
checking /dev/uscanner6... failed to open (Invalid argument)
checking /dev/uscanner7... failed to open (Invalid argument)
checking /dev/uscanner8... failed to open (Invalid argument)
checking /dev/uscanner9... failed to open (Invalid argument)
checking /dev/uscanner10... failed to open (Invalid argument)
checking /dev/uscanner11... failed to open (Invalid argument)
checking /dev/uscanner12... failed to open (Invalid argument)
checking /dev/uscanner13... failed to open (Invalid argument)
checking /dev/uscanner14... failed to open (Invalid argument)
checking /dev/uscanner15... failed to open (Invalid argument)
trying libusb:


EPSON Scanner)>

bLength   18
bDescriptorType   1
bcdUSB2.00
bDeviceClass  255
bDeviceSubClass   255
bDeviceProtocol   255
bMaxPacketSize0   64
idVendor  0x04B8
idProduct 0x0130
bcdDevice 1.00
iManufacturer 1 (EPSON)
iProduct  2 (EPSON Scanner)
iSerialNumber 0 ()
bNumConfigurations1
 
 bLength  9
 bDescriptorType  2
 wTotalLength 32
 bNumInterfaces   1
 bConfigurationValue  1
 iConfiguration   0 ()
 bmAttributes 192 (Self-powered)
 MaxPower 2 mA
  
   
   bLength9
   bDescriptorType4
   bInterfaceNumber   0
   bAlternateSetting  0
   bNumEndpoints  2
   bInterfaceClass255
   bInterfaceSubClass 255
   bInterfaceProtocol 255
   iInterface 0 ()

bLength   7
bDescriptorType   5
bEndpointAddress  0x81 (in 0x01)
bmAttributes  2 (bulk)
wMaxPacketSize512
bInterval 255 ms
bRefresh  0
bSynchAddress 0

bLength   7
bDescriptorType   5
bEndpointAddress  0x02 (out 0x02)
bmAttributes  2 (bulk)
wMaxPacketSize512
bInterval 255 ms
bRefresh  0
bSynchAddress 0


checking for GT-6801 ...
this is not a GT-6801 (bcdUSB = 0x200)
checking for GT-6816 ...
this is not a GT-6816 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GT-8911 ...
this is not a GT-8911 (check 1, bDeviceClass = 255, bInterfaceClass 
= 255)

checking for MA-1017 ...
this is not a MA-1017 (bDeviceClass = 255, bInterfaceClass = 255)
checking for MA-1015 ...
this is not a MA-1015 (bcdUSB = 0x200)
checking for MA-1509 ...
this is not a MA-1509 (bcdUSB = 0x200)
checking for LM983[1,2,3] ...
this is not a LM983x (bcdUSB = 0x200)
checking for GL646 ...
this is not a GL646 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GL646_HP ...
this is not a GL646_HP (bcdUSB = 0x200)
checking for GL660+GL646 ...
this is not a GL660+GL646 (bDeviceClass = 255, bInterfaceClass = 255)
checking for GL84x ..

Re: Where do I find instructions on how to configure sane-epkowa

[Leslie Jensen]

On 2009-12-31 13:09, Roland Smith wrote:

On Thu, Dec 31, 2009 at 12:25:53PM +0100, Leslie Jensen wrote:


On 2009-12-31 12:04, Roland Smith wrote:

On Thu, Dec 31, 2009 at 12:06:20AM +0100, Leslie Jensen wrote:


my dll.conf:


Personally, I would only leave in the backends that I actually use.


What do you mean?


I only have one line in my dll.conf, containing just the epson driver. In your
case, only the line 'epkowa' should suffice.


ok, I'll try commenting out all but epkowa




If scanning works as root but not as a normal user, it is probably a
permission problem.


The messages above plus the fact that scanimage -L produces the same
message as above suggests to me that the system stil needs to be made
aware of the scanner. I just not able to figure out where to do it.


What does sane-find-scanner say?


sane-find-scanner -q
found USB scanner (vendor=0x04b8 [EPSON], product=0x0130 [EPSON 
Scanner]) at libusb:/dev/usb:/dev/ugen7.2




Roland

___
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: Where do I find instructions on how to configure sane-epkowa

[Roland Smith]

On Thu, Dec 31, 2009 at 12:25:53PM +0100, Leslie Jensen wrote:
> 
> On 2009-12-31 12:04, Roland Smith wrote:
> > On Thu, Dec 31, 2009 at 12:06:20AM +0100, Leslie Jensen wrote:
> >>
> >> my dll.conf:
> >
> > Personally, I would only leave in the backends that I actually use.
> 
> What do you mean?

I only have one line in my dll.conf, containing just the epson driver. In your
case, only the line 'epkowa' should suffice.
 
> > If scanning works as root but not as a normal user, it is probably a
> > permission problem.
> 
> The messages above plus the fact that scanimage -L produces the same 
> message as above suggests to me that the system stil needs to be made 
> aware of the scanner. I just not able to figure out where to do it.

What does sane-find-scanner say?

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpkke6EBkD88.pgp
Description: PGP signature

Re: Where do I find instructions on how to configure sane-epkowa

[Leslie Jensen]

On 2009-12-31 12:04, Roland Smith wrote:

On Thu, Dec 31, 2009 at 12:06:20AM +0100, Leslie Jensen wrote:


my dll.conf:


Personally, I would only leave in the backends that I actually use.


What do you mean?




epkowa.conf

usb 0x04b8 0x0130


That should be OK.


I've created /etc/devfs.rules it was not present!

With the line:

add path 'usb/*' mode 0660


This means you'd have to be in the wheel or operator group to have access!
Either add a specific group that you are a member of, or use 0666.


Yes I am, and I always test as root.



You should also have a ruleset identifier in devfs.rules. Read devfs.rules(5).
And you'd have to activate the ruleset in /etc/rc.conf. After that it is best
to reboot to make sure all the changes are in effect.


I have devfs_system_ruleset="system" i rc.conf and

[system=10]
add path 'usb/*' mode 0660
in devfs.rules



Or you can test the scanner as root, like Warren said. Root has access to all
devices. Try running xscanimage from a terminal, and look at the error
messages, if any.


:xscanimage
[xscanimage] No scanners were identified. If you were expecting something
  different, check that the scanner is plugged in, turned on and
  detected by sane-find-scanner (if appropriate). Please read
  the documentation which came with this software (README, FAQ,
  manpages).
:sudo xscanimage
[xscanimage] No scanners were identified. If you were expecting something
  different, check that the scanner is plugged in, turned on and
  detected by sane-find-scanner (if appropriate). Please read
  the documentation which came with this software (README, FAQ,
  manpages).




If scanning works as root but not as a normal user, it is probably a
permission problem.


The messages above plus the fact that scanimage -L produces the same 
message as above suggests to me that the system stil needs to be made 
aware of the scanner. I just not able to figure out where to do it.




Roland

/Leslie
___
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: Where do I find instructions on how to configure sane-epkowa

[Roland Smith]

On Thu, Dec 31, 2009 at 12:06:20AM +0100, Leslie Jensen wrote:
> 
> my dll.conf:

Personally, I would only leave in the backends that I actually use.

> epkowa.conf
> 
> usb 0x04b8 0x0130

That should be OK.
 
> I've created /etc/devfs.rules it was not present!
> 
> With the line:
> 
> add path 'usb/*' mode 0660

This means you'd have to be in the wheel or operator group to have access! 
Either add a specific group that you are a member of, or use 0666.

You should also have a ruleset identifier in devfs.rules. Read devfs.rules(5).
And you'd have to activate the ruleset in /etc/rc.conf. After that it is best
to reboot to make sure all the changes are in effect.

Or you can test the scanner as root, like Warren said. Root has access to all
devices. Try running xscanimage from a terminal, and look at the error
messages, if any.

If scanning works as root but not as a normal user, it is probably a
permission problem.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgp792CWKTQ6R.pgp
Description: PGP signature

Re: Where do I find instructions on how to configure sane-epkowa

[Warren Block]

On Thu, 31 Dec 2009, Leslie Jensen wrote:

I've created /etc/devfs.rules it was not present!

With the line:

add path 'usb/*' mode 0660


A line in /etc/rc.conf is needed to activate those rules, too:

devfs_system_ruleset="localrules"

...assuming you had [localrules=10] at the start of devfs.rules.

These are just permissions applied to dynamic devices.  It's easier to 
first test the scanner as root.


-Warren Block * Rapid City, South Dakota USA
___
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: Where do I find instructions on how to configure sane-epkowa

[Leslie Jensen]

The uscanner device has been deprecated in favor of the libusb API that is in
the base system in 8.x. (Even the /dev/ugen devices are now just links to
nodes in /dev/usb/.)

If you have the configuration right (both dll.conf and epkowa.conf), check the
device permissions. I've got the following in /etc/devfs.rules (not 
devfs.conf!);

 add path 'usb/*' mode 0660 group usb

(Note that USB devices are now in a separate subdirectory!) All users of UDB
devices must be in the usb group, in this case. If you don't have untrusted
users you could use 'mode 0666' without the group statement.

If the device permissions are OK, please post your epkowa.conf and dll.conf,
and the output of 'usbconfig list' when the scanner is attached

As an aside, have you tried the plain epson driver?

Roland



my dll.conf:

# enable the next line if you want to allow access through the network:
net
abaton
agfafocus
apple
avision
artec
artec_eplus48u
as6e
bh
canon
canon630u
canon_dr
#canon_pp
cardscan
coolscan
#coolscan2
coolscan3
#dc25
#dc210
#dc240
dell1600n_net
dmc
epjitsu
#epson
epson2
fujitsu
#gphoto2
genesys
gt68xx
hp
hp3900
hpsj5s
hp3500
hp4200
hp5400
hp5590
hpljm1005
hs2p
ibm
leo
lexmark
ma1509
matsushita
microtek
microtek2
mustek
#mustek_pp
mustek_usb
mustek_usb2
nec
niash
pie
pint
pixma
plustek
#plustek_pp
#pnm
qcam
ricoh
rts8891
s9036
sceptre
sharp
sm3600
sm3840
snapscan
sp15c
#st400
#stv680
tamarack
teco1
teco2
teco3
#test
u12
umax
#umax_pp
umax1220u
v4l
xerox_mfp
epkowa



epkowa.conf

usb 0x04b8 0x0130



I've created /etc/devfs.rules it was not present!

With the line:

add path 'usb/*' mode 0660




usbconfig list


ugen0.1:  at usbus0, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON
ugen1.1:  at usbus1, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON
ugen2.1:  at usbus2, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON
ugen3.1:  at usbus3, cfg=0 md=HOST spd=HIGH 
(480Mbps) pwr=ON
ugen4.1:  at usbus4, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON
ugen5.1:  at usbus5, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON
ugen6.1:  at usbus6, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON
ugen7.1:  at usbus7, cfg=0 md=HOST spd=HIGH 
(480Mbps) pwr=ON
ugen4.2:  at usbus4, cfg=0 md=HOST spd=FULL 
(12Mbps) pwr=ON
ugen2.2: <5880 Broadcom Corp> at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) 
pwr=ON
ugen7.2:  at usbus7, cfg=0 md=HOST spd=HIGH 
(480Mbps) pwr=ON



I've not tried the plain epson driver. Acording to the SANE home page my 
scanner (Epson Perfection V500 Photo) is only supported by the epkowa 
driver.


/Leslie
___
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: Where do I find instructions on how to configure sane-epkowa

[Roland Smith]

On Wed, Dec 30, 2009 at 11:03:54PM +0100, Leslie Jensen wrote:
> When I was running 7.2 I had found a way to make it work.
> 
> First I added the product in /sys/dev/usb/usbdevs then the same 
> information had to be added in /sys/dev/usb/uscanner.c then I had to 
> recompile the kernel, build and install it. The scanner would then be found.
> 
> Now on 8.0 I can't find uscanner.c so there must be another way to 
> handle it.

The uscanner device has been deprecated in favor of the libusb API that is in
the base system in 8.x. (Even the /dev/ugen devices are now just links to
nodes in /dev/usb/.)

If you have the configuration right (both dll.conf and epkowa.conf), check the
device permissions. I've got the following in /etc/devfs.rules (not 
devfs.conf!);

add path 'usb/*' mode 0660 group usb

(Note that USB devices are now in a separate subdirectory!) All users of UDB
devices must be in the usb group, in this case. If you don't have untrusted
users you could use 'mode 0666' without the group statement.

If the device permissions are OK, please post your epkowa.conf and dll.conf,
and the output of 'usbconfig list' when the scanner is attached

As an aside, have you tried the plain epson driver? 

Roland
--
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpqdrfSiFYTd.pgp
Description: PGP signature

Re: Where do I find instructions on how to configure sane-epkowa

[Leslie Jensen]

On 2009-12-30 19:58, Roland Smith wrote:

On Wed, Dec 30, 2009 at 06:48:56PM +0100, Leslie Jensen wrote:

I'm at the point where sane-find-scanner detects my scanner but
scanimage cannot find it.

I know I must use the sane-epkowa backend.

I've edited the /usr/local/etc/sane.d/epkowa.conf but I think I need to
make sane aware of the epkowa backend.


Put a line

epkowa

in /usr/local/etc/sane.d/dll.conf


It's already there



Put the vendor and device-id you get from sane-find-scanner in epkowa.conf


I did it before I posted this question.



Roland


When I was running 7.2 I had found a way to make it work.

First I added the product in /sys/dev/usb/usbdevs then the same 
information had to be added in /sys/dev/usb/uscanner.c then I had to 
recompile the kernel, build and install it. The scanner would then be found.


Now on 8.0 I can't find uscanner.c so there must be another way to 
handle it.


/Leslie
___
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: Where do I find instructions on how to configure sane-epkowa

[Roland Smith]

On Wed, Dec 30, 2009 at 06:48:56PM +0100, Leslie Jensen wrote:
> I'm at the point where sane-find-scanner detects my scanner but 
> scanimage cannot find it.
> 
> I know I must use the sane-epkowa backend.
> 
> I've edited the /usr/local/etc/sane.d/epkowa.conf but I think I need to 
> make sane aware of the epkowa backend.

Put a line

epkowa

in /usr/local/etc/sane.d/dll.conf

Put the vendor and device-id you get from sane-find-scanner in epkowa.conf

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpMxH7gGRdff.pgp
Description: PGP signature

Where do I find instructions on how to configure sane-epkowa

[Leslie Jensen]

I'm at the point where sane-find-scanner detects my scanner but 
scanimage cannot find it.


I know I must use the sane-epkowa backend.

I've edited the /usr/local/etc/sane.d/epkowa.conf but I think I need to 
make sane aware of the epkowa backend.


The man page for sane-epkowa is not very helpful and there's nothing in 
the handbook to help me out.


Any suggestions?

Thanks

/Leslie
___
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: Rebuild instructions for amd64 systems

[Adam Vande More]

>
>
> then, add the following line below all other 'options' lines:
> options PAE # large memory (>4G) support
>
> then, find and comment out these two lines to avoid a conflict with PAE:
>
> device adv  # Advansys SCSI adapters
> device  adw # Advansys wide SCSI adapter
>
>
This is unnecessary and bad.  pae should be used on i386 for large memory
support, amd64 in some ways exists so you don't have to run pae which is a
considerable performance hit.  I'm surprised that actually works.

-- 
Adam Vande More
___
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: Rebuild instructions for amd64 systems

[Matt Szubrycht]

Hi Richard,

Kernel recompilation part of the handbook is fairly straightforward  
and should walk you through step-by-step without any snags: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html
Just remember to use amd64 instead i386 in the examples @ the link  
above.  You will need full source tree to play with kernel (sysinstall  
to the rescue if you don't).


Disclaimer - the below worked for me multiple times and may or may not  
work for you.  If you decide to follow the steps outlined below and it  
breaks your box, spills your coffee or converts the datacenter into a  
recycling center, you are responsible for it and I cannot be held  
accountable in any way.  In other words - use at your own risk.




The way I do it (6.0-RELEASE) - at this point you must be root:

cd
mkdir kernels
cd /usr/src/sys/amd64/conf
cp GENERIC ~/kernels/GENERIC.ORIG
cp GENERIC NEWKERNEL

vim NEWKERNEL, search for
ident GENERIC
and change to NEWKERNEL

then, add the following line below all other 'options' lines:
options PAE # large memory (>4G) support

then, find and comment out these two lines to avoid a conflict with PAE:

device adv  # Advansys SCSI adapters
device  adw # Advansys wide SCSI adapters


I am not sure about the Advansys conflict in versions newer than 6.0.
A total of 4 lines to edit on of my stock 6.0-RELEASE GENERIC kernel.

Then:

cd /usr/src
make buildkernel KERNCONF=NEWKERNEL
if compiles, install:
make installkernel KERNCONF=NEWKERNEL

once that's done, reboot and you should see your new kernel



Here's a diff from my 6.0:

[r...@banksy /usr/src/sys/i386/conf]# diff BANKSYPAE GENERIC
25c25
< ident  BANKSYPAE
---
> ident  GENERIC
65c65
< optionsPAE # 2006-12-12 Large memory support 
ma...@bmihosting.com
---
>
96,97c96,97
< # conflicts with PAE deviceadv # Advansys SCSI 
adapters
< # conflicts with PAE deviceadw # Advansys wide 
SCSI adapters
---
> device adv # Advansys SCSI adapters
> device adw # Advansys wide SCSI adapters


Good luck.

Cheers,
Matthew Szubrycht


On Oct 29, 2009, at 8:52 PM, Richard Gehlbach wrote:

I am installing FreeBSD 7.2 / amd64 on a new server (HP DL370 G6)  
with 2 quad Xeon processors and 16GB memory.  I have worked with the  
i386 versions since version 3.x, but this is the first server large  
enough to need amd64.


I have been trying to determine the correct procedures for  
rebuilding the world and kernel.  I have not been able to find a  
location that had step by step instructions, similar to the  
handbook, for properly working with the amd64 version.  Searches  
have turned up so many fragments of what needs to be done, that I  
cannot feel confident trying to put the pieces together.


I need instructions for the command line compile options, conf file  
additions, and any special instructions.


If anyone can point me to some applicable links or some specific  
instructions, it would be appreciated.


TIA
Richard

--
Richard D. Gehlbach   Gehlbach Consulting Services
rdgeh...@gehlbach.com 3321 Pepperhill Ct.
859.269.6658  Fax 859.266.7446Lexington, KY  40502


___
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 
"


___
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: Rebuild instructions for amd64 systems

[ill...@gmail.com]

2009/10/29 Richard Gehlbach :
> I am installing FreeBSD 7.2 / amd64 on a new server (HP DL370 G6) with 2
> quad Xeon processors and 16GB memory.  I have worked with the i386 versions
> since version 3.x, but this is the first server large enough to need amd64.
>
> I have been trying to determine the correct procedures for rebuilding the
> world and kernel.  I have not been able to find a location that had step by
> step instructions, similar to the handbook, for properly working with the
> amd64 version.  Searches have turned up so many fragments of what needs to
> be done, that I cannot feel confident trying to put the pieces together.
>
> I need instructions for the command line compile options, conf file
> additions, and any special instructions.
>
> If anyone can point me to some applicable links or some specific
> instructions, it would be appreciated.

It's not that different in most ways.  From the forums and
this mailing list, the biggest "gotcha" seems to be that
HAMMER is the only valid setting for cpu in your kernconf.

Otherwise, the normal stuff from /usr/src/UPDATING applies
as with anything else.

-- 
--
___
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: Rebuild instructions for amd64 systems

[Adam Vande More]

On Thu, Oct 29, 2009 at 10:52 PM, Richard Gehlbach wrote:

> I am installing FreeBSD 7.2 / amd64 on a new server (HP DL370 G6) with 2
> quad Xeon processors and 16GB memory.  I have worked with the i386 versions
> since version 3.x, but this is the first server large enough to need amd64.
>
> I have been trying to determine the correct procedures for rebuilding the
> world and kernel.  I have not been able to find a location that had step by
> step instructions, similar to the handbook, for properly working with the
> amd64 version.  Searches have turned up so many fragments of what needs to
> be done, that I cannot feel confident trying to put the pieces together.
>
> I need instructions for the command line compile options, conf file
> additions, and any special instructions.
>
> If anyone can point me to some applicable links or some specific
> instructions, it would be appreciated.
>
> TIA
> Richard
>

It is exactly the same procedure, cvsup/csup and build/installation
procedure.  This is assuming of course that amd64 is currently on the
system.



-- 
Adam Vande More
___
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"

Rebuild instructions for amd64 systems

[Richard Gehlbach]

I am installing FreeBSD 7.2 / amd64 on a new server (HP DL370 G6) with 2 
quad Xeon processors and 16GB memory.  I have worked with the i386 
versions since version 3.x, but this is the first server large enough to 
need amd64.


I have been trying to determine the correct procedures for rebuilding 
the world and kernel.  I have not been able to find a location that had 
step by step instructions, similar to the handbook, for properly working 
with the amd64 version.  Searches have turned up so many fragments of 
what needs to be done, that I cannot feel confident trying to put the 
pieces together.


I need instructions for the command line compile options, conf file 
additions, and any special instructions.


If anyone can point me to some applicable links or some specific 
instructions, it would be appreciated.


TIA
Richard

--
Richard D. Gehlbach   Gehlbach Consulting Services
rdgeh...@gehlbach.com 3321 Pepperhill Ct.
859.269.6658  Fax 859.266.7446Lexington, KY  40502


___
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: pgpsendmail instructions

[bsd schaft]

Glenn,

My mailer.conf contains:

/etc/mail >cat mailer.conf
# $FreeBSD: src/etc/mail/mailer.conf,v 1.3.34.1 2009/04/15 03:14:26 kensmith
Exp $
#
# Execute the "real" sendmail program, named /usr/libexec/sendmail/sendmail
#
sendmail/usr/libexec/sendmail/sendmail
send-mail   /usr/libexec/sendmail/sendmail
mailq   /usr/libexec/sendmail/sendmail
newaliases  /usr/libexec/sendmail/sendmail
hoststat/usr/libexec/sendmail/sendmail
purgestat   /usr/libexec/sendmail/sendmail

regarding the symbolic link:

/etc/mail >ls -l /usr/sbin/sen*
lrwxr-xr-x  1 root  wheel 21 May 31 10:28 /usr/sbin/sendmail ->
/usr/sbin/mailwrapper

It was the /usr/sbin/sendmail, sorry about that!

So lets say , we replace the /usr/libexec/sendmail/sendmail with the
pgpsendmail object from /usr/local/lib.

/etc/mail >cd /usr/libexec/sendmail/
/usr/libexec/sendmail >ls -l
total 704
-r-xr-sr-x  1 root  smmsp  665512 May 31 10:28 sendmail
-r-xr-sr-x  1 root  smmsp   30944 Jul 23 19:17 sendmail.pgp
/usr/libexec/sendmail >mv sendmail sendmail.real
/usr/libexec/sendmail >mv sendmail.pgp sendmail

As you can see, exactly the same security and all.
Now check my env , for the PGPPATH variable:

SHELL=/usr/local/bin/bash
TERM=xterm
OLDPWD=/etc/mail
USER=root
PAGER=more
FTP_PASSIVE_MODE=YES
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin
:/root/bin
MAIL=/var/mail/root
BLOCKSIZE=K
PWD=/usr/libexec/sendmail
PS1=$PWD >
SHLVL=1
HOME=/root
_=/usr/bin/env

Not there, so i can restart the process...

/etc/rc.d >./sendmail restart
Stopping sendmail.
Starting sendmail.
SENDMAIL refers back to PGPsendmail!
Someone didn't read the installation notes...

I checked the pkg-message file:

/usr/ports/mail/pgpsendmail >ls -l
total 10
-rw-r--r--  1 root  wheel  640 Oct 16  2005 Makefile
-rw-r--r--  1 root  wheel  204 Nov 25  2005 distinfo
drwxr-xr-x  2 root  wheel  512 May 31 17:07 files
-rw-r--r--  1 root  wheel  456 Apr 17  1995 pkg-descr
-rw-r--r--  1 root  wheel   58 Aug 17  1998 pkg-plist

But is is not there...
What can i do next, add/replace a line in mailer.conf:

sendmail/usr/local/lib/pgpsendmail

Again, after a restart, i receive the same error...

,Danny




- Original Message - 
From: "Glen Barber" 
To: "Familie van der Schaft" 
Cc: 
Sent: Sunday, August 02, 2009 1:08 PM
Subject: Re: pgpsendmail instructions


On Sun, Aug 2, 2009 at 6:48 AM, Familie van der
Schaft wrote:
> LS,
>
> I am trying to get pgpsenmail working but i can't figure out what to do.
> For example which instance of sendmail can/must be replaced:
>
> /usr/libexec/sendmail (which is symbolic link)

What do you have this linked to?
/usr/libexec/sendmail -> /usr/libexec/sendmail/sendmail ?

> /usr/sbin/sendmail
>
> in both cases, i get the following message:
>
> /etc/rc.d >./sendmail restart
> sendmail not running? (check /var/run/sendmail.pid).
> Starting sendmail.
> SENDMAIL refers back to PGPsendmail!
> Someone didn't read the installation notes...

Sometimes the problem is explained in the errors...
Other times, pkg-message would be helpful in a port.

%ls -1 /usr/ports/mail/pgpsendmail/
Makefile
distinfo
files
pkg-descr
pkg-plist

> /etc/rc.d >sendmail forcestart
> SENDMAIL refers back to PGPsendmail!
> Someone didn't read the installation notes...
>
> But where can i find these instructions (notes).
> The man-page (pgpsendmail(8)) does not give any extra info.
> Can anybody help me?
>

Have a look at mailer.conf(5)

-- 
Glen Barber







No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.392 / Virus Database: 270.13.40/2276 - Release Date: 08/01/09
18:04:00

___
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: pgpsendmail instructions

[Glen Barber]

On Sun, Aug 2, 2009 at 6:48 AM, Familie van der
Schaft wrote:
> LS,
>
> I am trying to get pgpsenmail working but i can't  figure out what to do.
> For example which instance of sendmail can/must  be replaced:
>
> /usr/libexec/sendmail (which is symbolic link)

What do you have this linked to?
/usr/libexec/sendmail -> /usr/libexec/sendmail/sendmail ?

> /usr/sbin/sendmail
>
> in both cases, i get the following message:
>
> /etc/rc.d >./sendmail  restart
> sendmail not running? (check /var/run/sendmail.pid).
> Starting sendmail.
> SENDMAIL refers back to PGPsendmail!
> Someone didn't read the installation notes...

Sometimes the problem is explained in the errors...
Other times, pkg-message would be helpful in a port.

%ls -1 /usr/ports/mail/pgpsendmail/
Makefile
distinfo
files
pkg-descr
pkg-plist

> /etc/rc.d >sendmail forcestart
> SENDMAIL refers back to PGPsendmail!
> Someone didn't read the installation notes...
>
> But where can i find these instructions (notes).
> The man-page (pgpsendmail(8)) does not give any extra info.
> Can anybody help me?
>

Have a look at mailer.conf(5)

-- 
Glen Barber
___
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"

pgpsendmail instructions

[Familie van der Schaft]

LS,

I am trying to get pgpsenmail working but i can't  figure out what to do.
For example which instance of sendmail can/must  be replaced:

/usr/libexec/sendmail (which is symbolic link)
/usr/sbin/sendmail

in both cases, i get the following message:

/etc/rc.d >./sendmail  restart
sendmail not running? (check /var/run/sendmail.pid).
Starting sendmail.
SENDMAIL refers back to PGPsendmail!
Someone didn't read the installation notes...
/etc/rc.d >sendmail forcestart
SENDMAIL refers back to PGPsendmail!
Someone didn't read the installation notes...

But where can i find these instructions (notes).
The man-page (pgpsendmail(8)) does not give any extra info.
Can anybody help me?

Danny.
___
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: Installing MATLAB: processor is missing the SSE2 instructions

[Daniel Underwood]

Upon further investigation, I've learned that I can disregard the sse2 error.

I changed:

expr "`cat /proc/cpuinfo`" : '.* sse2 .*$'

to:

#expr "`cat /proc/cpuinfo`" : '.* sse2 .*$'
echo 1
___
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"

Installing MATLAB: processor is missing the SSE2 instructions

[Daniel Underwood]

Trying to install MATLAB (R2008b) according to the directions here:
<http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/linuxemu-matlab.html>

Here's what happens when I try to install:

devil # /compat/linux/bin/sh /home/daniel/matlab-install/install
expr: illegal option -- r
usage: expr [-e] expression
/home/daniel/matlab-install/install: line 197: [: -ne: unary operator expected

Error: Your computer processor is missing the SSE2 instructions that
   are required for MATLAB to run correctly.
   For system requirements consult http://www.mathworks.com ...


Ignore, for now, the line 197 error.  The following is an excerpt from
the install script:

instructioncheck() { # check /proc/cpuinfo on glnx86 for
 # correct level of instructions
 # Output the flag location. A zero mean
 # no flag.
case $Arch in
glnx86)
# Example: Be sure that the platform has flag sse2
#  There are many ways to do this.
#  Output the flag location.
expr "`cat /proc/cpuinfo`" : '.* sse2 .*$'
return
;;
*)
;;
esac


This "sse2" flag is not found in /compat/linux/proc/cpuinfo:

[dan...@devil ~]$ cat /compat/linux/proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 7
model name  : Intel(R) Core(TM)2 Duo CPU T7700  @ 2.40GHz
stepping: 10
processor   : 1
vendor_id   : GenuineIntel
cpu family  : 6
model   : 7
model name  : Intel(R) Core(TM)2 Duo CPU T7700  @ 2.40GHz
stepping: 10
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 b19 b21 mmxext mmx fxsr xmm b26 b27 b28 b29 3dnow
cpu MHz : 2394.02
bogomips: 2394.02
[dan...@devil ~]$

Surely my cpu supports the needed instructions sets for MATLAB,
because I've installed and used this exact MATLAB distribution on this
machine when running Linux.

What exactly is going on here?  How do I fix this problem?

TIA,
Daniel
___
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"

Using CPUTYPE=core2, Penryn instructions support

[Jakub Lach]

Hello.

>From what I understand, gcc42 does not support core2 option. How it's
possible that
some people are using it with FreeBSD -CURRENT (and it's not used as mere
prescott alias).

http://www.nabble.com/Re%3A-CPUTYPE-p10787174.html

Is -CURRENT using newer version of gcc, despite licensing problems?

I'm interested in using full Penryn instructions, if that would be
possible...
-- 
View this message in context: 
http://www.nabble.com/Using-CPUTYPE%3Dcore2%2C-Penryn-instructions-support-tp18792525p18792525.html
Sent from the freebsd-questions mailing list archive at Nabble.com.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: /usr/src/Makefile instructions

[KAYVEN RIESE]

On Fri, 23 May 2008, Oliver Fromme wrote:

KAYVEN RIESE <[EMAIL PROTECTED]> wrote:
> Tom Evans wrote:



> > I've redirected this to questions@, as this seems more like a 'User
> > question/technical support' rather than 'General technical discussion'.
> > Please try to keep the mailing lists on topic.
>
> That list is too busy.  I find I don't have to unsubscribe to
> "hackers," and it doesn't seem as hard core to misinterpret
> what "hackers" are, than say "ports" or "acpi"

Well, "hackers" usually means developers, i.e. people
hacking on the FreeBSD code.  Therefore I'm afraid I
have to agree with Tom:  Your questions should better
go to the questions list.


ergo: because obviously I am a flumming idiot.  I thought hacker
was something you took eucalyptus fro.



> I realized that "make delete-old" and "make delete-old-libs"
> are both part of the "cannonical," I guess because I am going
> RELENG_6_3 to RELENG_7

I always use "make delete-old", as instructed in the
/usr/src/UPDATING file, and it has never bitten me.
Please have a look at that file; the important part
starts at the section titled "To rebuild everything".



Actually, after composing this I kicked myself, because
/usr/src/Makefile has clearly instructed me to do
make delete-old after make installworld and I think
I will throw caution to the wind and append -U to my
subsequent mergemaster followed by make delete-old-libs



> On that note, was I given misinformation when I was advised
> that it would be impossible to upgrade RELENG_6_2 directly to
> RELENG_7 ?

"Nothing is impossible!", as Dr. Farnsworth from the
Futurama series used to say.  :-)



Oh well.  Water under the bridge.  I expect to someday edit
this to RELENG_7_1 or the like when freebsd.org says so and
following the instructions in /usr/src/Makefile again.



But seriously ...  I think going from 6.2 to 7.0 should
work fine.  However, the official notion is that updates
across major versions have to be supported only for the
latest stable release.  Any other configurations might
work, but it's not guaranteed.  If it fails, you're not
expected to complain or ask for help, but instead try
the officially supported way (i.e. first update to the
latest stable on your existing branch, then update
across the major version boundary).  If that still fails,
you may complain and ask for help.



Interesting.  No.  Fascinitating.  Captian Kirk, I believe
this star will supernova in approximately 12 days, 13 hours,
34 minutes and 23.3425 seconds.



Note that it is IMPORTANT to rebuild *all* of your ports
when you update from 6.x to 7.x.  (This holds true for
any major version update.)  If you don't do this, you
will get library dependency collisions, i.e. port A uses
libc.so.7 and depends on port B, but port B still links
against the older libc.so.6.  Things will break sooner
or later.  That's why you should rebuild *all* ports
after updating to 7.x.  (You can keep older ports only
if you are absolutely sure that they are not part of any
dependencies, and never will be.)



My habit is to run cvsup standard-supfile followed by
cvsup ports-supfile.  IS that a dumb thing to do?



In your previous mail you mentioned:
> Things work, but dmesg has errors,

Would you please tell us what those errors are?  We might
be able to help you, but only if you tell us.



I told the ACPI folks and they told me nicely that my appropriate
post was too much of a hassle to bother with.  Some ding dong
was attaching after the fact of the wing ding and the fact that
the errors occured between the wing and the ding was irrelevant
since the dong ding subsequent to the ding ding recalibrated the
whosits in an adequate fashion before reaching single user mode.



> and many ports fail and their makes

Again:  Please post messages and everything relevant to
the problems.  There are really people on these lists
that are willing to help, but we need as much information
as possible in order to be able to help.

Best regards
  Oliver



Well.. I reckon I mights a git up thah gumpshun whenis I's gonna
get tootin' on sumptin that gits mah goat subsequently.


--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'



*--*
  Kayven Riese, BSC

Re: /usr/src/Makefile instructions

[KAYVEN RIESE]

On Fri, 23 May 2008, [EMAIL PROTECTED] wrote:




On that note, was I given misinformation when I was advised
that it would be impossible to upgrade RELENG_6_2 directly to
RELENG_7 ?



pcm/mixer.c 
/usr/src/sys/modules/sound/sound/../../../dev/sound/pcm/sndstat.c 
/usr/src/sys/modules/sound/sound/../../../dev/sound/pcm/sound.c 
/usr/src/sys/modules/sound/sound/../../../dev/sound/unit.c 
/usr/src/sys/module




Close to implausible, perhaps? That would indeed be the case, unless you
truly are longing for a major workout, either with mergemaster et al, or
both with mergemaster and the ports. The former case, which assumes you
don't have many ports installed, is often a no-brainer: install a fresh
system. The latter case may be somewhat more complicated: install a fresh
system for the least effort on your side, or go the update route if you need
to keep your system up and usable during the process.




awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h
awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE 
-DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq 
-I/usr/obj/usr/src/sys/GENERIC 
/usr/src/sys/modules/sym/../../dev/sym/sym_hipd.c

===> syscons (depend)
===> syscons/apm (depend)
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE 
-DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq 
-I/usr/obj/usr/src/sys/GENERIC 
/usr/src/sys/modules/syscons/apm/../../../dev/syscons/apm/apm_saver.c

===> syscons/blank (depend)
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE 
-DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq 
-I/usr/obj/usr/src/sys/GENERIC 
/usr/src/sys/modules/syscons/blank/../../../dev/syscons/blank/blank_saver.c

===> syscons/daemon (depend)
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE 
-DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq 
-I/usr/obj/usr/src/sys/GENERIC 
/usr/src/sys/modules/syscons/daemon/../../../dev/syscons/daemon/daemon_saver.c

===> syscons/dragon (depend)
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE 
-DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq 
-I/usr/obj/usr/src/sys/GENERIC 
/usr/src/sys/modules/syscons/dragon/../../../dev/syscons/dragon/dragon_saver.c

===> syscons/fade (depend)
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE 
-DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq 
-I/usr/obj/usr/src/sys/GENERIC 
/usr/src/sys/modules/syscons/fade/../../../dev/syscons/fade/fade_saver.c

===> syscons/fire (depend)
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE 
-DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq 
-I/usr/obj/usr/src/sys/GENERIC 
/usr/src/sys/modules/syscons/fire/../../../dev/syscons/fire/fire_saver.c

===> syscons/green (depend)
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE 
-DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq 
-I/usr/obj/usr/src/sys/GENERIC 
/usr/src/sys/modules/syscons/green/../../../dev/syscons/green/green_saver.c

===> syscons/logo (depend)
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE 
-DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq 
-I/usr/obj/usr/src/sys/GENERIC 
/usr/src/sys/modules/syscons/logo/../../../dev/syscons/logo/logo_saver.c 
/usr/src/sys/modules/syscons/logo/../../../dev/syscons/logo/logo.c










I should note that I always took the update trail, and never regretted it
afterwards (well, if only so slightly). For instance, my workstation lived
through 5.2.1-R, 6.2-R, RELENG_6, and finally RELENG_7, all with the aid of
cvsup. The process is straightforward, well-designed and easily executed
(thanks to the developers), but problems often pop-up with ports
(especially such messy ones as Gnome, etc) which take lots of time to
correct.


rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE 
-DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq 
-I/usr/obj/usr/src/sys/GENERIC 
/usr/src/sys/modules/sysvipc/sysvshm/../../../kern/sysv_shm.c

===> ti (depend)
@ -> /usr/src/sys
machine -> /usr/src/sys/i386/include
awk -f @/tools/makeobjops.awk @/kern/device_if.m -h
awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h
awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h
ln -sf /usr/obj/usr/src/sys/GENERIC/opt_ti.h opt_ti.h
ln -sf /usr/obj/usr/src/sys/GENERIC/opt_zero.h opt_zero.h
rm -f .depend
mkdep -f .depend -a   -nostdinc -D_KERNEL -DKLD_MODULE 
-DHAVE_KERNEL_OPTION_HEADERS -I. -I@ -I@/contrib/altq 
-I/usr/obj/usr/src/sys/GEN

Re: /usr/src/Makefile instructions

[KAYVEN RIESE]

On Fri, 23 May 2008, [EMAIL PROTECTED] wrote:




On that note, was I given misinformation when I was advised
that it would be impossible to upgrade RELENG_6_2 directly to
RELENG_7 ?


Close to implausible, perhaps? That would indeed be the case, unless you
truly are longing for a major workout, either with mergemaster et al, or
both with mergemaster and the ports. The former case, which assumes you
don't have many ports installed, is often a no-brainer: install a fresh
system. The latter case may be somewhat more complicated: install a fresh
system for the least effort on your side, or go the update route if you need
to keep your system up and usable during the process.


I didn't really understand that and I don't understand why I am a bad
person for spamming my idiotic thoughts on the matter, but in any case
this is moot because I am up an runing RELENG_6_3 and making kernel
after editing the stable-supfiles RELENG_6_3 to RELENG_7 let's all
cross our fingers that communication has just happened.


I should note that I always took the update trail, and never regretted it
afterwards (well, if only so slightly). For instance, my workstation lived
through 5.2.1-R, 6.2-R, RELENG_6, and finally RELENG_7, all with the aid of
cvsup. The process is straightforward, well-designed and easily executed
(thanks to the developers), but problems often pop-up with ports
(especially such messy ones as Gnome, etc) which take lots of time to
correct.


I am feeling better about cvsup and even mergemaster nowadays. Thank
you very much for your support.



So, in summary, a sane person should probably go with clean system update.



Is that what I am doing? Umm.. maybe not.  I have all these errors that
I don't understand and that people ignore but I have a browser and
a terminal, so I feel like a functioning pile of carbon compounds.


P.S.: whoever replies next, it's safe to drop hackers@ from CC: anytime now



Nah.. hackers needs the publicity!



   Kayven Riese, BSCS, MS (Physiology and Biophysics)


[SorAlx]  ridin' VS1400



*--*
  Kayven Riese, BSCS, MS (Physiology and Biophysics)
  (415) 902 5513 cellular
  http://kayve.net
  Webmaster http://ChessYoga.org
*--*
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: /usr/src/Makefile instructions

[soralx]

> On that note, was I given misinformation when I was advised
> that it would be impossible to upgrade RELENG_6_2 directly to
> RELENG_7 ?

Close to implausible, perhaps? That would indeed be the case, unless you
truly are longing for a major workout, either with mergemaster et al, or
both with mergemaster and the ports. The former case, which assumes you
don't have many ports installed, is often a no-brainer: install a fresh
system. The latter case may be somewhat more complicated: install a fresh
system for the least effort on your side, or go the update route if you need
to keep your system up and usable during the process.

I should note that I always took the update trail, and never regretted it
afterwards (well, if only so slightly). For instance, my workstation lived
through 5.2.1-R, 6.2-R, RELENG_6, and finally RELENG_7, all with the aid of
cvsup. The process is straightforward, well-designed and easily executed
(thanks to the developers), but problems often pop-up with ports
(especially such messy ones as Gnome, etc) which take lots of time to
correct.

So, in summary, a sane person should probably go with clean system update.

P.S.: whoever replies next, it's safe to drop hackers@ from CC: anytime now

>Kayven Riese, BSCS, MS (Physiology and Biophysics)

[SorAlx]  ridin' VS1400
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: /usr/src/Makefile instructions

[Oliver Fromme]

KAYVEN RIESE <[EMAIL PROTECTED]> wrote:
 > Tom Evans wrote:
 > > I've redirected this to questions@, as this seems more like a 'User
 > > question/technical support' rather than 'General technical discussion'.
 > > Please try to keep the mailing lists on topic.
 > 
 > That list is too busy.  I find I don't have to unsubscribe to
 > "hackers," and it doesn't seem as hard core to misinterpret
 > what "hackers" are, than say "ports" or "acpi"

Well, "hackers" usually means developers, i.e. people
hacking on the FreeBSD code.  Therefore I'm afraid I
have to agree with Tom:  Your questions should better
go to the questions list.

 > I realized that "make delete-old" and "make delete-old-libs"
 > are both part of the "cannonical," I guess because I am going
 > RELENG_6_3 to RELENG_7

I always use "make delete-old", as instructed in the
/usr/src/UPDATING file, and it has never bitten me.
Please have a look at that file; the important part
starts at the section titled "To rebuild everything".

 > On that note, was I given misinformation when I was advised
 > that it would be impossible to upgrade RELENG_6_2 directly to
 > RELENG_7 ?

"Nothing is impossible!", as Dr. Farnsworth from the
Futurama series used to say.  :-)

But seriously ...  I think going from 6.2 to 7.0 should
work fine.  However, the official notion is that updates
across major versions have to be supported only for the
latest stable release.  Any other configurations might
work, but it's not guaranteed.  If it fails, you're not
expected to complain or ask for help, but instead try
the officially supported way (i.e. first update to the
latest stable on your existing branch, then update
across the major version boundary).  If that still fails,
you may complain and ask for help.

Note that it is IMPORTANT to rebuild *all* of your ports
when you update from 6.x to 7.x.  (This holds true for
any major version update.)  If you don't do this, you
will get library dependency collisions, i.e. port A uses
libc.so.7 and depends on port B, but port B still links
against the older libc.so.6.  Things will break sooner
or later.  That's why you should rebuild *all* ports
after updating to 7.x.  (You can keep older ports only
if you are absolutely sure that they are not part of any
dependencies, and never will be.)

In your previous mail you mentioned:
 > Things work, but dmesg has errors,

Would you please tell us what those errors are?  We might
be able to help you, but only if you tell us.

 > and many ports fail and their makes

Again:  Please post messages and everything relevant to
the problems.  There are really people on these lists
that are willing to help, but we need as much information
as possible in order to be able to help.

Best regards
   Oliver

-- 
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606,  Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758,  Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart

FreeBSD-Dienstleistungen, -Produkte und mehr:  http://www.secnetix.de/bsd

'Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.'
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: /usr/src/Makefile instructions

[KAYVEN RIESE]

On Fri, 23 May 2008, Tom Evans wrote:

On Fri, 2008-05-23 at 05:49 -0700, KAYVEN RIESE wrote:




I've redirected this to questions@, as this seems more like a 'User
question/technical support' rather than 'General technical discussion'.
Please try to keep the mailing lists on topic.


That list is too busy.  I find I don't have to unsubscribe to
"hackers," and it doesn't seem as hard core to misinterpret
what "hackers" are, than say "ports" or "acpi"

I realized that "make delete-old" and "make delete-old-libs"
are both part of the "cannonical," I guess because I am going
RELENG_6_3 to RELENG_7

On that note, was I given misinformation when I was advised
that it would be impossible to upgrade RELENG_6_2 directly to
RELENG_7 ?



Cheers

Tom



*--*
  Kayven Riese, BSCS, MS (Physiology and Biophysics)
  (415) 902 5513 cellular
  http://kayve.net
  Webmaster http://ChessYoga.org
*--*
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ports/UPDATING instructions and Python 2.4

[Nikola Lecic]

On Sat, 25 Aug 2007 09:15:52 -0500
Kirk Strauser <[EMAIL PROTECTED]> wrote:

> I need to keep Python 2.4 on my system to run Zope (which isn't  
> compatible with 2.5).  So, I dutifully followed the instructions  
> under /usr/ports/UPDATING starting with "If want to keep 2.4.x  
> installed alongside 2.5.x [...]".  When I came back a little later,  
> all of my dependent ports had been upgraded from py24-* to py25-*,  
> effectively killing my webserver.
> 
> Could someone else take a look at those instructions and see if they  
> make sense - they look a little suspicious to me - or if there is  
> some gotcha that I might have missed?  Thanks.

Hello Kirk,

A couple of thoughts that could be useful.

The instructions explain how to keep both 2.4 and 2.5 versions of
_Python_itself_, that's all. The "PYTHON_DEFAULT_VERSION=python2.5" line
of /etc/make.conf serves as an indicator to all new applications to
avoid confusion if python-2.4 is installed alongside.

You now probably have something like:

  # ls -d /var/db/pkg/py*
  /var/db/pkg/python24-2.4.4_1
  /var/db/pkg/python25-2.5.1
  /var/db/pkg/py25-cairo-1.4.0_1
  /var/db/pkg/py25-chardet-1.0_3
  [... etc., py25-* only ...]

Zope feels fine in this situation:

  # cd /usr/ports/www/zope3
  # make configure
  [...]
  ===>  Patching for zope-3.3.1
  ===>  Applying FreeBSD patches for zope-3.3.1
  ===>   zope-3.3.1 depends on file: /usr/local/bin/python2.4 - found
  ===>  Configuring for zope-3.3.1
  Configuring Zope installation
  Using Python interpreter at /usr/local/bin/python2.4

(The same for other py-* ports that are fixed to 2.4 interpreter (i.e.
www/py-pylons).)

Now, I'm trying to understand what happened to your webserver: you said
that changing py24-* to py25-* broke it. Maybe I'm mistaken, but I
see just 7 py-* ports that have any relationship with Zope. These are: 

  databases/py-psycopg   [WITH_ZOPE optional]
  devel/py-zopeInterface
  devel/py-twistedCore   [dependent on devel/py-zopeInterface]
  lang/py-mx-base[WITH_ZOPE optional]
  x11-toolkits/py-kiwi   [optionally linked with devel/py-zopeInterface]
  devel/py-zconfig   [not sure about this one]
  textproc/py-zpt[not sure about this one]

The presence of 'WITH_ZOPE' flag will force the port to use correct
version of Python: 

  # cd /usr/ports/lang/py-mx-base/
  # make USE_ZOPE=yes
  ===>   py23-mx-base-2.0.6 depends on file: /usr/local/bin/python2.3 - not 
found
  ===>Verifying install for /usr/local/bin/python2.3 in 
/usr/ports/lang/python23

(ZOPE_VERSION is also available.) So where is the connection between
zope and py-* ports that crashed your webserver? Please elaborate on
this, i.e. how does you webserver depend on py24-*?

In meantime, if you just need py24- versions of several ports, you can
do something like this:

  # portupgrade -f -r -m "PYTHON_VERSION=2.4" py25-imaging

This will install py24-imaging and rebuild ports dependent on it (e.g.
graphics/skencil). Use '-n' flag to see what will happen first.

This is a quick and non-elegant help to get your webserver working
again. If you provide more information you will surely get more
in-depth explanation and more elegant solution from someone, preferably
from other Zope users.

Nikola Lečić
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

ports/UPDATING instructions and Python 2.4

[Kirk Strauser]

I need to keep Python 2.4 on my system to run Zope (which isn't  
compatible with 2.5).  So, I dutifully followed the instructions  
under /usr/ports/UPDATING starting with "If want to keep 2.4.x  
installed alongside 2.5.x [...]".  When I came back a little later,  
all of my dependent ports had been upgraded from py24-* to py25-*,  
effectively killing my webserver.


Could someone else take a look at those instructions and see if they  
make sense - they look a little suspicious to me - or if there is  
some gotcha that I might have missed?  Thanks.

--
Kirk Strauser



PGP.sig
Description: This is a digitally signed message part

Developer's Handbook DDB instructions

[David Kirchner]

I'm trying to track down a background fsck deadlock bug. I've found a
thread on groups.google.com about another person having a similar
problem but with snapshots. The suggestion made there was to compile a
kernel with DDB, and the user was referred to the Developer's
Handbook.

http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-online-ddb.html

The Handbook appears to be out of date -- it states that you have to
add "options DDB" to the kernel config to enable DDB. When you try
that, part way through the make depend process it informs you that you
also need KDB. Are there any other steps necessary to get DDB to work
on a newer version of FreeBSD (say 6.0-RELEASE)?

Since this particular deadlock test will probably take 12+ hours of
runtime to trigger, I'd like to get this right, so I can get as much
information as possible into a PR.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

problems with handbook instructions for creating a CCD on 6-RELEASE

[Mike Hunter]

Hi,

I ran into some trouble following the handbook to create a CCD on a server
I built recently.

I have 4 identical disks that I wanted to use in a CCD.  Problem 1 was
after labeling each disk per the instructions, I end up with an a and a
c partition.  When I follow the instructions to create an all-encompassing
e partition, the partition editor complains that I am creating an
over-lapping partition.  Removing the a partition fixes the problem

Then, after I run ccdconfig, "disklabel -e ccd0" does not work, I have to
run "disklabel -w ccd0 auto" and get things going from there.

Finally, I'm a bit confused about soft-updates:

# mount
/dev/da0s1a on / (ufs, local)
devfs on /dev (devfs, local)
/dev/da0s1e on /tmp (ufs, local, soft-updates)
/dev/da0s1f on /usr (ufs, local, soft-updates)
/dev/da0s1d on /var (ufs, local, soft-updates)
/dev/ccd0c on /data3 (ufs, local)
/dev/da1s1e on /data4 (ufs, local)

Ok, so softupdates sounds cool, but it's off on ccd0why?  It's treated the 
same
in /etc/fstab:

# cat /etc/fstab 
# DeviceMountpoint  FStype  Options Dump # Pass#
/dev/da0s1b noneswapsw  0   0
/dev/da0s1a /   ufs rw  1   1
/dev/da0s1e /tmpufs rw  2   2
/dev/da0s1f /usrufs rw  2   2
/dev/da0s1d /varufs rw  2   2
/dev/ccd0c  /data3  ufs rw  2   3
/dev/da1s1e /data4  ufs rw  2   4
/dev/cd0/cdrom  cd9660  ro,noauto   0   0

Pleaes cc me as I'm not on -questions.

Thanks!

Mike
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Instructions for upgrading?

[Dr. Jennifer Nussbaum]

 



Dr. Jennifer Nussbaum wrote:

>where can i find simple instructions for upgrading to a new major version?
   
In addition to the advice given earlier, you might
read Bruce Mah's "Migration Guide".  The 5.3 version
is here:

http://people.freebsd.org/~bmah/relnotes/5.3-RELEASE/early-adopter.html

and might be quite applicable to the 4.x > 5.x migration,
as 5.3 was the first "-STABLE" release in the 5.X branch, and
many users were expected to move to it from 4.11, etc.
   
 thanks for this! i looked att his pretty closely and thought i did everything 
right but
 did run into trouble in the end. something went wrong at "installworld", i 
guess with
 the 4.x compatability layer, and now im not sure what to do to get things 
fixed.
 when i boot into the singleuser shell, even simple commands i gett hings like
 "/usr/libexec/ld-elf.so.1: Shared object "libncurses.so.5" not found, required 
by "more"".
 
 i can use basic commands like ls and cat but not even slightly hard things 
like more or vi.
 
 at this point i would be willing to save my /usr directory and just try to 
find a cd
 drive to do a clean install, but im not sure how to save it. i did do a backup 
of my
 most important things but if the install is going completely wrong i guess id 
like 
 to save everything. my files in /usr are all still there but i dont know if i 
can hook
 up to the network or save to an attached cd, seeing how many commands i cant 
run.
 
 thanks! next time i just stay with 4.10, or do a better backup!
 
 Jen



-
 Yahoo! Music Unlimited - Access over 1 million songs. Try it free.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Instructions for upgrading?

[Kevin Kinsey]

Dr. Jennifer Nussbaum wrote:


where can i find simple instructions for upgrading to
a new major
version? im running 4.10 right now and want to change
to 6.0--why not? heh--but the installation page in the
handbook just talks about doing it from
scratch. and the entire "upgrade' section of the 6.0
release notes just says 
"Source upgrades to FreeBSD 6.0-RELEASE are only

supported from FreeBSD 5.3-RELEASE or later. Users of
older systems wanting to upgrade 6.0-RELEASE will need
to update to FreeBSD 5.3 or newer first, then to
FreeBSD 6.0-RELEASE. Important: Upgrading FreeBSD
should, of course, only be attempted after backing up
all data and configuration files." but doesnt say how
to really do it.

same with the 5.x release notes. im willing to do this
in two step, from 4.10 to 5.4 and then to 6.0, if that
is neccessary.

my laptop doesnt have a CD drive of a floppy drive, so
i want to do it over the network but i need simple
instructions if someone can help.

thank you!

jen
 



In addition to the advice given earlier, you might
read Bruce Mah's "Migration Guide".  The 5.3 version
is here:

http://people.freebsd.org/~bmah/relnotes/5.3-RELEASE/early-adopter.html

   and might be quite applicable to the 4.x > 5.x migration,
as 5.3 was the first "-STABLE" release in the 5.X branch, and
many users were expected to move to it from 4.11, etc.

As mentioned, a recent 5.X to 6.0-RELEASE upgrade is a
relative breeze by comparison, and doesn't require much
"special" at all.  YMMV, of course.  As with all upgrades, be
sure and read /src/UPDATING (and /usr/ports/UPDATING if
you use any "ports".)

Regards,

Kevin Kinsey
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Instructions for upgrading?

[RW]

On Saturday 26 November 2005 20:16, Dr. Jennifer Nussbaum wrote:
> where can i find simple instructions for upgrading to
> a new major
> version? im running 4.10 right now and want to change
> to 6.0--why not? heh--but the installation page in the
> handbook just talks about doing it from
> scratch. and the entire "upgrade' section of the 6.0
> release notes just says
> "Source upgrades to FreeBSD 6.0-RELEASE are only
> supported from FreeBSD 5.3-RELEASE or later. Users of
> older systems wanting to upgrade 6.0-RELEASE will need
> to update to FreeBSD 5.3 or newer first, then to
> FreeBSD 6.0-RELEASE. Important: Upgrading FreeBSD
> should, of course, only be attempted after backing up
> all data and configuration files." but doesnt say how
> to really do it.
>
> same with the 5.x release notes. im willing to do this
> in two step, from 4.10 to 5.4 and then to 6.0, if that
> is neccessary.

It's covered in chapter 20 of the handbook. Unfortunately it's under the 
rather misleading title "The Cutting Edge", because it's written in terms of 
tracking current/stable.  Upgrading to 5.4 and 6.0 is just the same, but with 
RELENG_5_4 and RELENG_6_0 as the release tags.  You should also look at the 
chapter on building the kernel, which gives more detail on that part of the 
process. 

You should disable any drivers in loader.conf that are built out of ports (eg 
nvidia). After the upgrade is done you will have to rebuild your ports or 
replace everything from packages.










> my laptop doesnt have a CD drive of a floppy drive, so
> i want to do it over the network but i need simple
> instructions if someone can help.
>
> thank you!
>
> jen
>
>
>
> __
> Yahoo! Music Unlimited
> Access over 1 million songs. Try it free.
> http://music.yahoo.com/unlimited/
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Instructions for upgrading?

[Dr. Jennifer Nussbaum]

where can i find simple instructions for upgrading to
a new major
version? im running 4.10 right now and want to change
to 6.0--why not? heh--but the installation page in the
handbook just talks about doing it from
scratch. and the entire "upgrade' section of the 6.0
release notes just says 
"Source upgrades to FreeBSD 6.0-RELEASE are only
supported from FreeBSD 5.3-RELEASE or later. Users of
older systems wanting to upgrade 6.0-RELEASE will need
to update to FreeBSD 5.3 or newer first, then to
FreeBSD 6.0-RELEASE. Important: Upgrading FreeBSD
should, of course, only be attempted after backing up
all data and configuration files." but doesnt say how
to really do it.

same with the 5.x release notes. im willing to do this
in two step, from 4.10 to 5.4 and then to 6.0, if that
is neccessary.

my laptop doesnt have a CD drive of a floppy drive, so
i want to do it over the network but i need simple
instructions if someone can help.

thank you!

jen



__ 
Yahoo! Music Unlimited 
Access over 1 million songs. Try it free. 
http://music.yahoo.com/unlimited/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: correct instructions for building a 4.11 debugging kernel?

[Toomas Aas]

Dan Langille wrote:
In particular, I'm not getting the kernel I promised by the docs:
  The make(1) process will have built two kernels. kernel and
  kernel.debug.
>
I know I have a new kernel:
[EMAIL PROTECTED]:/] # ls -l /kernel*
-r-xr-xr-x  1 root  wheel  4077437 May 18 18:41 /kernel
-r-xr-xr-x  1 root  wheel  3559066 Sep 18  2001 /kernel.GENERIC
-r-xr-xr-x  1 root  wheel  3559066 Sep 18  2001 
/kernel.GENERIC.original
-r-xr-xr-x  1 root  wheel  4033421 May  8 19:38 /kernel.nodebug
-r-xr-xr-x  1 root  wheel  3954128 Apr  4  2003 /kernel.pre.tcp.patch
[EMAIL PROTECTED]:/] #

What am I missing?
Are you sure you're looking at the right place? The kernel.debug won't 
be placed in / directory when you install the new kernel, it remains in 
/usr/src/sys//compile/YOURKERNEL

--
Toomas Aas
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

correct instructions for building a 4.11 debugging kernel?

[Dan Langille]

Hi folks,

I'm trying to capture a dump from my 4.11 fatal trap 12.  Reading 
this URL:

   

I'm finding that I'm not getting the expected results.  In 
particular, I'm not getting the kernel I promised by the docs:

  The make(1) process will have built two kernels. kernel and
  kernel.debug.

I have no kernel.debug despite having done this:

cd /usr/src/sys/i386/conf/
config -g BAST
cd ../../compile/BAST
make depend && make && make install

I know I have a new kernel:

[EMAIL PROTECTED]:/] # ls -l /kernel*
-r-xr-xr-x  1 root  wheel  4077437 May 18 18:41 /kernel
-r-xr-xr-x  1 root  wheel  3559066 Sep 18  2001 /kernel.GENERIC
-r-xr-xr-x  1 root  wheel  3559066 Sep 18  2001 
/kernel.GENERIC.original
-r-xr-xr-x  1 root  wheel  4033421 May  8 19:38 /kernel.nodebug
-r-xr-xr-x  1 root  wheel  3954128 Apr  4  2003 /kernel.pre.tcp.patch
[EMAIL PROTECTED]:/] #


NOTE: /kernel.nodebug was renamed from /kernel.old to keep it around.

What am I missing?

FreeBSD bast.unixathome.org 4.11-STABLE FreeBSD 4.11-STABLE #1: Wed 
May 18 18:39:50 EDT 2005 [EMAIL PROTECTED]:/usr
/src/sys/compile/BAST  i386

Thank you
-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/
   NEW brochure available at http://www.bsdcan.org/2005/advocacy/

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Step-by-step instructions for MD_ROOT embedded, please?

[David Clear]

Here you go (found on the web):

1. Create a filesystem image:

# dd if=/dev/zero of=mdimage -bs=1024 count=4096
# mdconfig -a -t vnode -f mdimage -s 4096k -u 4
# disklabel -r -w md4 auto
# newfs /dev/md4c
# mount /dev/md4c /mnt
 .
 . put stuff on it
 .
# umount /mnt
# mdconfig -d -u 4

2. Make sure you have the kernel options:
options MD_ROOT
options MD_ROOT_SIZE=4096

...and rebuild.

3. As you said, compiling
/usr/src/release/write_mfs_in_kernel.c from
FreeBSD-4.11 with SBOFF set to 64K will work.  You'll
also need to #include  prior to
fs.h.

4. Set vfs.root.mountfrom to "ufs:md0" in
/boot/loader.conf.

Works for me on 5.3-RELEASE.

Good luck.

Regards,
David.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Step-by-step instructions for MD_ROOT embedded, please?

[Nine Forty]

I am having problems building an embedded kernel +
root filesystem image for FreeBSD-5.3.  I had
previously succeeded on 4.11.

For 4.11 I created a filesystem using vnconfig,
disklabel, newfs, etc. and installed it into the
kernel using write_mfs_in_kernel.  I built a kernel
with MD_ROOT and MD_ROOT_SIZE set to 32M.  I selected
the MD filesystem by setting vfs.root.mountfrom in
/boot/loader.conf.

Following these same steps in 5.3 (except using
mdconfig, and hacking write_mfs_in_kernel (setting
SBOFF to 64K)) the kernel failed to find the
filesystem.  If I let the kernel boot with the disk
filesystem I still can't mount md0 - a valid
filesystem is not found.


I would greatly appreciate a detailed, idiot-proof,
step-by-step literal command list starting with
nothing and ending with a kernel with a working
embedded filesystem.  I don't need the filesystem to
have contents, just to be there and be found... once
the kernel boots with md0 and fails to find
/sbin/init, I can take it from there.


Looking on the mailing list archives and on the web I
get the impression that this is not a common
procedure...  I haven't been able to find instructions
anywhere.


I hope someone can help me.

Regards,
Paul.


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[Loren M. Lang]

On Wed, Mar 02, 2005 at 03:27:09AM -0800, Ted Mittelstaedt wrote:
> 
> 

> > > Also one other thing that is important - if you don't get an answer
> > > within a week or so, ask again, politely.
> >
> > How do I ask after the second post with no reply?  On bended knee?
> 
> Just keep asking periodically.  Or, you could e-mail the developer of
> the SCSI device driver directly, it's not hard to read the source and
> see who it is, and their e-mail addresses are on the FreeBSD website.

Actually, I've found lately that a good irc chatroom can help with some
problems that ppl may just ignore on a mailing list.  I've been hanging
out in #freebsd and #netbsd on irc.freenode.net.

> 
> Ted
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "[EMAIL PROTECTED]"

-- 
I sense much NT in you.
NT leads to Bluescreen.
Bluescreen leads to downtime.
Downtime leads to suffering.
NT is the path to the darkside.
Powerful Unix is.

Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc
Fingerprint: CEE1 AAE2 F66C 59B5 34CA  C415 6D35 E847 0118 A3D2
 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Installation instructions for Firefox somewhere?

[Ted Mittelstaedt]

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Anthony
> Atkielski
> Sent: Wednesday, March 02, 2005 10:52 AM
> To: freebsd-questions@freebsd.org
> Subject: Re: Installation instructions for Firefox somewhere?
>

>
> So perhaps FreeBSD is issuing commands that the disk drives don't like.
>
> Incidentally, I've discovered that I can instantly generate similar
> messages by issuing "smartctl -a /dev/da0" (or da1).
>

That is 1000% better as far as troubleshooting goes, you need to file
a PR on this.

> > Secondly, you don't know how NT setup the disks and such on your
> > system.  It is quite possible that the NT driver saw the mismatch
> > and simply reprogrammed the SCSI adapter card to limit both disks
> > to 10Mbt transfers.  Or possibly the NT driver decided not to send
> > writes to both disks at the same time.  So, comparisons like "it
> > worked with NT so the hardware must be good" are almost useless.
>
> So how do I configure FreeBSD to do the same thing?  If NT can do it in
> software, so can FreeBSD.
>

The Adaptec driver gets the setting out of the SCS adapters setting that
are written into it's eeprom.  You know the Press f6 message you get
on boot, that lets you into the Adaptec BIOS?  Change it there and the
driver will pick up the change.

> > But the most important thing, and I think why your having so much
> > trouble here, is that you are trying to approach this problem
> > as though you paid $9,000 for this server, yesterday.
>
> I don't believe in throwing computers away just because they are a few
> years old.
>

I don't either but the world does and it is difficult to interest people
in support of gear that is 8 years old.  Hardware manufacturers in
particular
have a vested interest in helping you to write drivers for their brand
new gear so they can sell it, and a vested interest in not helpiing you
resurrect old gear that might steal sales away from new gear.

>
> So what is the difference between yours and mine?
>

FreeBSD 4.11 instead of 5.3 is a big one.  Also I am using a card, my
controller isn't on the motherboard.  Also I only have 1 disk drive -
although as you will note I have a SCSI cd and burner on the same bus.
And my disk drive is a Micrapolis not a Seagate or Quantum.

>
> But this is a stable system.  The hardware _does_ work.  I didn't put
> this together out of scrap parts.  It has run perfectly for
> eight years;
> I think I can safely say that it's pretty well broken in by now.  So
> when I switch from Windows to FreeBSD and it stops working, I know it's
> not hardware.
>

As long as you don't accept the fact that Windows drivers can and do
write around hardware kludges, and FreeBSD drivers may not have all the
same written-around kludges as the Windows ones do, your going to get
nowhere.


>
> I'll consider it.  The waste of time has been mutual.
>

If you don't take our advice here on the forum, it is a waste.  Try
limiting the sync negotiation to 10MB on the Quantum and see what
happens.

Ted

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[Anthony Atkielski]

 younger than
> it for under a hundred bucks - see:

Why should I pay anything for another machine, when I have a perfectly
good one here on my desk?

All I need is software that can drive it.

> The fact of the matter is that ANY life you can get out of this
> server today is found money - it's a freebie.  HP, 8 or 10 years
> ago when they designed this server would have told you THEN that
> they wern't expecting it to be in service today.

If so, they would have been deliberately lying, as even then everyone
knew that HP machines can run for a decade or more with ease.

> Now to be honest I have a soft spot for older hardware, the
> gateway router system that this very message is passing though just
> happens to be a dual Pentium Pro with 128MB of ram and a 4GB
> SCSI disk on an Adaptec controller, here's it's dmesg:

Looks familiar.

> ahc0:  port 0x9300-0x93ff mem

> aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBs

These look familiar, too.  I still have an Adaptec SCSI controller in a
box somewhere (it wouldn't run on the cheap hardware I used for my old
server, so I removed it and replaced it with a more modest
controller--in that case, it _was_ hardware).

> da0 at ahc0 bus 0 target 0 lun 0
> da0:  Fixed Direct Access SCSI-2 device
> da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing

Hmm.

> This is a real live system I just built last week.  It runs a champ.

So what is the difference between yours and mine?

> Said pile included cases even, it also includes a second dual Ppro
> motherboard (sans CPU's).

In some circles it is said that PPros still have considerable value.
They're not fast but they are reliable and classic, with hardware
features that Intel inexplicably abandoned thereafter.

> But, I have learned something in dealing with the older gear, and that
> is that you must be extremely flexible with it.  If I get 2 systems
> that are flakey, I will swap parts between them in an effort to get
> 1 stable system.  More commonly though I have a half dozen or more
> older systems in the pool at a time, that parts move around between,
> and that new systems in a state of disrepair come into, and old systems
> that are in a state of stability go out of to friends and others who
> need systems.

But this is a stable system.  The hardware _does_ work.  I didn't put
this together out of scrap parts.  It has run perfectly for eight years;
I think I can safely say that it's pretty well broken in by now.  So
when I switch from Windows to FreeBSD and it stops working, I know it's
not hardware.

> If you insist on going that route, your only hope is interesting the
> developer of the ahc driver in your problem.  Start by filing a PR in
> the correct manner (ie: by following the instructions in the Handbook)
> and if that does not get a response from the developer (the PR's are
> mailed to the developers of the drivers) then read the source code
> of the driver to find out who it is, look up his e-mail address on the
> website, send him an e-mail begging to take a look at your PR, and
> stop wasting our time here.

I'll consider it.  The waste of time has been mutual.

-- 
Anthony


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Installation instructions for Firefox somewhere?

[Ted Mittelstaedt]

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Anthony
> Atkielski
> Sent: Tuesday, March 01, 2005 8:53 PM
> To: freebsd-questions@freebsd.org
> Subject: Re: Installation instructions for Firefox somewhere?
>
>
> Ted Mittelstaedt writes:
>
> > It appears you have a narrow-SCSI max 10MB sync disk drive and a
> > ultra -3 20MB sync disk drive on the same adapter card.
> > Such a combination is iffy at best.
>
> The configuration was the one recommended by HP.  I bought the second
> drive from HP directly.  They both have the same type of SCSI
> interface,
> approved by HP.
>

HP didn't manufacture either of the drives nor the SCSI controller so
why would you think that they know what they are talking about?  HP
does the same thing Compaq does (now really the same since they
are the same company) they buy off-the-shelf parts from other
manufacturers
and bundle them together into systems that they sell.  Dell, Gateway
and all the rest of them do the same thing.  A very few of their
products (like the Vectra XU 6/200 that you have) they do design
the motherboards, but that's it.  And of course they design the
sheetmetal.  But for the motherboards in most of their stuff they
get OEMs to make them for them.

And despite all the testing on occasion they screw up and release
patches that patch around hardware problems.

> I'm tired of hearing why it's not FreeBSD's fault.  When you
> can tell me
> exactly what theses messages mean, instead of guessing, let me know.

Ok here goes:

Feb 26 20:09:23 contactdish kernel: (da0:ahc0:0:0:0): Retrying Command
Feb 26 20:09:23 contactdish kernel: (da0:ahc0:0:0:0): Request Requeued
Feb 26 20:09:23 contactdish kernel: (da0:ahc0:0:0:0): Retrying Command

This happens when the SCSI target disk0 stop answering
commands from the SCSI adapter.

Feb 26 20:09:26 contactdish kernel: (da1:ahc0:0:2:0): Retrying Command
Feb 26 20:09:26 contactdish kernel: (da1:ahc0:0:2:0): Queue Full
Feb 26 20:09:26 contactdish kernel: (da1:ahc0:0:2:0): Retrying Command

Same thing as above just with the second disk.

The usual problem is bad termination
that causes this, because what happens with bad termination is that
electrical noise causes one or more targets on the bus to receive a
command that is garbage, that target shuts down and goes out of sync with
the other initiators and targets on the bus, as soon as that happens all
targets shut down.  But it can also be caused
by a device that isn't totally compliant with the standard interfering
with another device on the bus (although this is rare)  And it can also
be caused by the adapter card driver sending a command to a target that
the target doesen't understand or does not process properly, this can
happen when during the probe on boot, a target responds saying it
supports
something, then really doesen't.  IDE devices are infamous for this,
claiming to support UDMA, PIO mode 4, and such when they really don't
support them properly.

Sometimes if the bus is left quiet, the devices can resync and things
go on.  Mostly though it almost always leads to the next thing that
you have, here:

eb 25 20:09:29 contactdish kernel: ahc0: Recovery Initiated
Feb 25 20:09:29 contactdish kernel: >>>>>>>>>>>>>>>>>> Dump Card State
Begins

The driver for the SCSI adapter has finally given up trying to send
commands
to the adapter card your disks are tied to and has decided to just
reset the card entirely, which resets the bus and all devices on it,
which reestablishes sync.

All the rest of the data that follows is a dump of the state of the card
and the commands sent, and what queue entries are trashed so the
operating
system can pick up where it left off if the card comes back online.

Feb 25 20:09:29 contactdish kernel: (da1:ahc0:0:2:0): SCB 0x49 - timed
out
Feb 25 20:09:29 contactdish kernel: sg[0] - Addr 0x1309b000 : Length 2048
Feb 25 20:09:29 contactdish kernel: (da1:ahc0:0:2:0): Queuing a BDR SCB
Feb 25 20:09:29 contactdish kernel: ahc0: Timedout SCBs already complete.
Interrupts may not be functioning.

This is a bit significant, after the bus reset, the second disk (the
Quantum) isn't answering. But it looks like it later on started
responding
since otherwise your system would probably have paniced.

None of this though is any help here.  You know what the problem is
you just don't know what is causing it.  The idea that a SCSI command
sent to a disk by the adapter card causing this is unlikely,
unless either the Seagate or Quantum models that you have are known
rogues (and I didn't find that they are) it is much more likely a
conflict on the SCSI bus.

> I'm not going to plug and unplug hardware all day based on your
> speculations, particularly since I know this hardware configuration
> works, and has 

Re: Installation instructions for Firefox somewhere?

[Peter Risdon]

On Wed, 2005-03-02 at 06:08 +0100, Anthony Atkielski wrote:
> Ted Mittelstaedt writes:
> 
> > The AIC7880 stuff is in the "good" category of stuff from Adaptec,
> > not the "junk" category.
> 
> Well, that's nice to hear.  I guess my $9000 wasn't entirely wasted.
> 
> > The people that can answer questions don't always respond.
> 
> Remember what I said about problems with FreeBSD support for
> mission-critical and large-scale deployments?

This is a voluntary mailing list. If you want FreeBSD support, pay for
it - a number of companies provide it. There's no difference here
between operating systems: there are volunteer forums for BSD, Linux,
Mac, Windows. And then there's paid support.

Businesses that want support for their operating systems (who don't
support their IT deployments internally), buy that support. That's how a
lot of the contributors here make a living. But this list is NOT paid
support.

> 
[...]
> 
> > Also one other thing that is important - if you don't get an answer
> > within a week or so, ask again, politely.
> 
> How do I ask after the second post with no reply?  On bended knee?
> 

Nobody here has any obligation to give you the time of day, let alone
help. Taking the line that other subscribers here somehow owe you a
living will alienate some of the people who might otherwise help you. Of
course, you're can do that if you want.

Peter.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Installation instructions for Firefox somewhere?

[Ted Mittelstaedt]

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Anthony
> Atkielski
> Sent: Tuesday, March 01, 2005 9:09 PM
> To: freebsd-questions@freebsd.org
> Subject: Re: Installation instructions for Firefox somewhere?
>
>
> Ted Mittelstaedt writes:
>
> > The AIC7880 stuff is in the "good" category of stuff from Adaptec,
> > not the "junk" category.
>
> Well, that's nice to hear.  I guess my $9000 wasn't entirely wasted.
>
> > The people that can answer questions don't always respond.
>
> Remember what I said about problems with FreeBSD support for
> mission-critical and large-scale deployments?
>

You get what you pay for.  If you want a response immediately then pay
money to
one of the many FreeBSD consultants/contractors.  I'll make you a deal,
even -
if you guarentee to pay me the same rate that Microsoft charges for tech
support on their products ($35 an incident) I will personally provide you
with an answer to any question you want to ask - at the $35 per question
rate, of course, and with the exact same disclaimers that Microsoft gives
you for their $35 incidents.  Oh and I almost forgot - since it's the
same
terms as the Microsoft support, that means you have to buy the copy of
FreeBSD from me - and I think my going rate on that is the same as
Windows
Server, which is something like $800 a copy. ;-)  (you have after all
said FreeBSD isn't a desktop OS) ;-)

> > Also, I don't generally answer questions that I have to do a lot of
> > digging on because the questioner didn't put in enough data.  Such as
> > your SCSI question.  You posted the dmesg but you still haven't
> > posted the model of HP server.
>
> I thought I had.  HP Vectra XU 6/200 D4352N/ABF.
>
> > This is assuming you are mixing interfaces, which is still to be
> > determined.
>
> I'm not.
>
> > Also one other thing that is important - if you don't get an answer
> > within a week or so, ask again, politely.
>
> How do I ask after the second post with no reply?  On bended knee?

Just keep asking periodically.  Or, you could e-mail the developer of
the SCSI device driver directly, it's not hard to read the source and
see who it is, and their e-mail addresses are on the FreeBSD website.

Ted

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[Anthony Atkielski]

Ted Mittelstaedt writes:

> The AIC7880 stuff is in the "good" category of stuff from Adaptec,
> not the "junk" category.

Well, that's nice to hear.  I guess my $9000 wasn't entirely wasted.

> The people that can answer questions don't always respond.

Remember what I said about problems with FreeBSD support for
mission-critical and large-scale deployments?

> Also, I don't generally answer questions that I have to do a lot of
> digging on because the questioner didn't put in enough data.  Such as
> your SCSI question.  You posted the dmesg but you still haven't
> posted the model of HP server.

I thought I had.  HP Vectra XU 6/200 D4352N/ABF.

> This is assuming you are mixing interfaces, which is still to be
> determined.

I'm not.

> Also one other thing that is important - if you don't get an answer
> within a week or so, ask again, politely.

How do I ask after the second post with no reply?  On bended knee?

-- 
Anthony


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[Anthony Atkielski]

Ted Mittelstaedt writes:

> It appears you have a narrow-SCSI max 10MB sync disk drive and a
> ultra -3 20MB sync disk drive on the same adapter card.
> Such a combination is iffy at best.

The configuration was the one recommended by HP.  I bought the second
drive from HP directly.  They both have the same type of SCSI interface,
approved by HP.

I'm tired of hearing why it's not FreeBSD's fault.  When you can tell me
exactly what theses messages mean, instead of guessing, let me know.
I'm not going to plug and unplug hardware all day based on your
speculations, particularly since I know this hardware configuration
works, and has worked for eight years.

As it stands now, all I know for sure is that FreeBSD apparently cannot
support what Windows can support, and nobody call tell me why.

-- 
Anthony


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Installation instructions for Firefox somewhere?

[Ted Mittelstaedt]

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Anthony
> Atkielski
> Sent: Tuesday, March 01, 2005 3:42 AM
> To: freebsd-questions@freebsd.org
> Subject: Re: Installation instructions for Firefox somewhere?
>
>
> Ted Mittelstaedt writes:
>
> > I have an Adaptec AAA-131 Ultra 2 card here that is just
> jumping up and
> > down to prove you wrong.
>
> This is an AIC7880.  When you have one of those, let me know.
>

The AIC7880 stuff is in the "good" category of stuff from Adaptec,
not the "junk" category.

> > However, I CAN tell you how to go about finding out what you need to
> > change.  Do you want to do this?  It might mean some effort
> on your part.
>
> I thought that asking questions here was supposed to help, and I posted
> all the information I have, but apparently nobody has a clue.
>

The people that can answer questions don't always respond.  A lot of
times
I will let questions go by that I know the answer to simply because it's
so easy that I know someone else is going to respond.

Also, I don't generally answer questions that I have to do a lot of
digging on because the questioner didn't put in enough data.  Such as
your SCSI question.  You posted the dmesg but you still haven't
posted the model of HP server.  More importantly, you didn't post
the overview data which if you had you would have got an answer to
at once.

For example if you had asked:

"I have a server that is giving errors on heavy disk load and I have
a narrow SCSI Seagate disk and a wide SCSI Quantum in it, make and
model #'s "

that would have got an immediate "don't do that your termination is
always screwed in such a scenario"

This is assuming you are mixing interfaces, which is still to be
determined.

Now granted you probably aren't aware of that, and I don't recall even
reading your original SCSI question anyway, I might have not got it.
I might have answered it anyway simply because I know that SCSI is
getting to be a lost art for many people and that a lot of people
here might have forgot about much of their institutional knowledge
on SCSI, even if I had to do the digging for it.

Also one other thing that is important - if you don't get an answer
within a week or so, ask again, politely.

Ted

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Installation instructions for Firefox somewhere?

[Ted Mittelstaedt]

Anthony,

  It appears you have a narrow-SCSI max 10MB sync disk drive and a
ultra -3 20MB sync disk drive on the same adapter card.
Such a combination is iffy at best.  Even worse is it's
different manufacturers - while SCSI is supposed to be
standard, the standard isn't completely followed by all
manufacturers.  It is not as bad as mixing IDE but it isn't the
best.

  Quantum (now Maxtor) does not have detailed specs as
to what exactly a Quantum XP34550S is, whether it's narrow
or wide or differential SCSI.  I can see it's an Atlas 2 drive
but there's both narrow and wide Atlas 2s  I would assume this
is a wide drive since it's synced at 20.000MB/s transfers
if so how are you attaching it to the adapter card?  Do you
have the narrow Seagate and the wide Quantum on
the same adapter card?  If so then your really asking for trouble.
And those 68-50 pin scsi adapters are bullshit if that is what
you are using.

  If the Quantum is a narrow drive, then going in to the Adaptec
card's BIOS and forcing negotiation on the Quantum to 10MB/s MIGHT fix
the trouble,
assuming FreeBSD picks up the 10MB.  But, from the looks of it you
have 2 SCSI adapters, one probably on motherboard, the other
on a card, the disks attached to the motherboard card (which has
no BIOS) and something else attached to the card (which does
have a BIOS)  Perhaps EISA-config could set it if this system
has EISA slots?

  Standard troubleshooting is to put in 1 drive, install FreeBSD
and work it out and see if it blows, then pull that drive and
put in the other, then install FreeBSD and work it and see if it blows.

  If you do that my guess is you will find FreeBSD doesen't blow
on either disk when they are separated.  Only when they are in
the same machine.

  Fortunately 4GB SCSI disks are cheap on the used market.  I've
never cared that much for Quantum SCSI, they were the OEM for
Apple for years and I never felt that the old Mac's obeyed the
SCSI standard completely, and that Quantum catered to this.  It
also speaks volumes that Quantum couldn't make a go of it in the
disk market and sold out to Maxtor.  As a result I run mostly
Seagate SCSI disks and I have never had a problem on Seagate<->Adaptec
combos.  If it was my machine I'd dig around for another Seagate SCSI
disk and jettison the Quantum, but I will admit this is personal
preference.

Ted

> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Anthony
> Atkielski
> Sent: Tuesday, March 01, 2005 4:05 AM
> To: freebsd-questions@freebsd.org
> Subject: Re: Installation instructions for Firefox somewhere?
>
>
> Chris Hodgins writes:
>
> > I might have missed it but I can't find any information
> about what SCSI
> > errors you are receiving.  Why don't you post the errors you
> are seeing
> > and/or perhaps your dmesg output as well and maybe someone can help
> > you.  Without more information noone can do more than guess.
>
> Here it is, again:
>
> I get constant streams of messages concerning my disks on the console
> whenever I have a lot of disk activity on my system (2x SCSI disks, no
> IDE or other disks). I'd very much like to know what's going
> on (there's
> nothing wrong with the hardware, so either it's a
> configuration problem,
> or it's a bug).
>
> There doesn't seem to be any data loss or corruption occurring.  I've
> had one or two panics, though (which may or may not have caused data
> loss--it's hard to tell).
>
> While recompiling the kernel, the system stalled periodically (at least
> anything involving disk I/O stalled) and generated several hundred
> kilobytes of messages looking like this:
>
> Feb 26 20:09:23 contactdish kernel: (da0:ahc0:0:0:0): Retrying Command
> Feb 26 20:09:23 contactdish kernel: (da0:ahc0:0:0:0): Request Requeued
> Feb 26 20:09:23 contactdish kernel: (da0:ahc0:0:0:0): Retrying Command
> Feb 26 20:09:23 contactdish kernel: (da0:ahc0:0:0:0): Queue Full
> Feb 26 20:09:23 contactdish kernel: (da0:ahc0:0:0:0): tagged
> openings now 64
> Feb 26 20:09:23 contactdish kernel: (da0:ahc0:0:0:0): Retrying Command
> Feb 26 20:09:24 contactdish kernel: (da0:ahc0:0:0:0): Queue Full
> Feb 26 20:09:24 contactdish kernel: (da0:ahc0:0:0:0): tagged
> openings now 63
> Feb 26 20:09:24 contactdish kernel: (da0:ahc0:0:0:0): Retrying Command
> Feb 26 20:09:26 contactdish kernel: (da1:ahc0:0:2:0): Request Requeued
> Feb 26 20:09:26 contactdish kernel: (da1:ahc0:0:2:0): Retrying Command
> Feb 26 20:09:26 contactdish kernel: (da1:ahc0:0:2:0): Queue Full
> Feb 26 20:09:26 contactdish kernel: (da1:ahc0:0:2:0): Retrying Command
>
> In addition, I sometimes get bursts of much longer messages, looking
> something like this:
>
> Feb 25 20

Re: Installation instructions for Firefox somewhere?

[Anthony Atkielski]

d
Feb 26 16:36:26 contactdish kernel: map[18]: type 1, range 32, base ffe0, 
size 20, enabled
Feb 26 16:36:26 contactdish kernel: found-> vendor=0x8086, dev=0x1229, 
revid=0x01
Feb 26 16:36:26 contactdish kernel: bus=0, slot=12, func=0
Feb 26 16:36:26 contactdish kernel: class=02-00-00, hdrtype=0x00, mfdev=0
Feb 26 16:36:26 contactdish kernel: cmdreg=0x0007, statreg=0x0280, cachelnsz=0 
(dwords)
Feb 26 16:36:26 contactdish kernel: lattimer=0xf8 (7440 ns), mingnt=0x08 (2000 
ns), maxlat=0x38 (14000 ns)
Feb 26 16:36:26 contactdish kernel: intpin=a, irq=11
Feb 26 16:36:26 contactdish kernel: map[10]: type 4, range 32, base fd00, 
size  8, enabled
Feb 26 16:36:26 contactdish kernel: map[14]: type 1, range 32, base fffbc000, 
size 12, enabled
Feb 26 16:36:26 contactdish kernel: found-> vendor=0x9004, dev=0x8178, 
revid=0x01
Feb 26 16:36:26 contactdish kernel: bus=0, slot=13, func=0
Feb 26 16:36:26 contactdish kernel: class=01-00-00, hdrtype=0x00, mfdev=0
Feb 26 16:36:26 contactdish kernel: cmdreg=0x0007, statreg=0x0290, cachelnsz=8 
(dwords)
Feb 26 16:36:26 contactdish kernel: lattimer=0xf8 (7440 ns), mingnt=0x08 (2000 
ns), maxlat=0x08 (2000 ns)
Feb 26 16:36:26 contactdish kernel: intpin=a, irq=11
Feb 26 16:36:26 contactdish kernel: powerspec 1  supports D0 D3  current D0
Feb 26 16:36:26 contactdish kernel: found-> vendor=0x8086, dev=0x84c5, 
revid=0x04
Feb 26 16:36:26 contactdish kernel: bus=0, slot=20, func=0
Feb 26 16:36:26 contactdish kernel: class=05-00-00, hdrtype=0x00, mfdev=0
Feb 26 16:36:26 contactdish kernel: cmdreg=0x, statreg=0x0080, cachelnsz=0 
(dwords)
Feb 26 16:36:26 contactdish kernel: lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), 
maxlat=0x00 (0 ns)
Feb 26 16:36:26 contactdish kernel: found-> vendor=0x8086, dev=0x84c4, 
revid=0x04
Feb 26 16:36:26 contactdish kernel: bus=0, slot=25, func=0
Feb 26 16:36:26 contactdish kernel: class=06-00-00, hdrtype=0x00, mfdev=0
Feb 26 16:36:26 contactdish kernel: cmdreg=0x0147, statreg=0x2200, cachelnsz=8 
(dwords)
Feb 26 16:36:26 contactdish kernel: lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), 
maxlat=0x00 (0 ns)
Feb 26 16:36:26 contactdish kernel: PCI-ISA bridge with incorrect subclass 0x0
Feb 26 16:36:26 contactdish kernel: PCI-ISA bridge with incorrect subclass 0x0
Feb 26 16:36:26 contactdish kernel: isab0:  at device 0.0 on 
pci0
Feb 26 16:36:26 contactdish kernel: isa0:  on isab0
Feb 26 16:36:26 contactdish kernel: atapci0:  port 
0xfff0-0x,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 irq 14 at device 1.0 on pci0
Feb 26 16:36:26 contactdish kernel: atapci0: Reserved 0x10 bytes for rid 0x20 
type 4 at 0xfff0
Feb 26 16:36:26 contactdish kernel: atapci0: [MPSAFE]
Feb 26 16:36:26 contactdish kernel: ata0: channel #0 on atapci0
Feb 26 16:36:26 contactdish kernel: atapci0: Reserved 0x8 bytes for rid 0x10 
type 4 at 0x1f0
Feb 26 16:36:26 contactdish kernel: atapci0: Reserved 0x1 bytes for rid 0x14 
type 4 at 0x3f6
Feb 26 16:36:26 contactdish kernel: ata0: reset tp1 mask=00 ostat0=ff ostat1=ff
Feb 26 16:36:26 contactdish kernel: ata0: [MPSAFE]
Feb 26 16:36:26 contactdish kernel: ata1: channel #1 on atapci0
Feb 26 16:36:26 contactdish kernel: atapci0: Reserved 0x8 bytes for rid 0x18 
type 4 at 0x170
Feb 26 16:36:26 contactdish kernel: atapci0: Reserved 0x1 bytes for rid 0x1c 
type 4 at 0x376
Feb 26 16:36:26 contactdish kernel: ata1: reset tp1 mask=01 ostat0=50 ostat1=ff
Feb 26 16:36:26 contactdish kernel: ata1-master: stat=0x00 err=0x01 lsb=0x14 
msb=0xeb
Feb 26 16:36:26 contactdish kernel: ata1: reset tp2 stat0=00 stat1=00 
devices=0x4
Feb 26 16:36:26 contactdish kernel: ata1: [MPSAFE]
Feb 26 16:36:26 contactdish kernel: ahc0:  
port 0xfe00-0xfeff mem 0xfffdc000-0xfffdcfff irq 10 at device 2.0 on pci0
Feb 26 16:36:26 contactdish kernel: ahc0: Defaulting to MEMIO off
Feb 26 16:36:26 contactdish kernel: ahc0: Reserved 0x100 bytes for rid 0x10 
type 4 at 0xfe00
Feb 26 16:36:26 contactdish kernel: ahc0: Reading SEEPROM...checksum error
Feb 26 16:36:26 contactdish kernel: ahc0: No SEEPROM available.
Feb 26 16:36:26 contactdish kernel: ahc0: Using left over BIOS settings
Feb 26 16:36:26 contactdish kernel: ahc0: Downloading Sequencer Program... 442 
instructions downloaded
Feb 26 16:36:26 contactdish kernel: ahc0: Features 0x10001, Bugs 0x25, Flags 
0x481460
Feb 26 16:36:26 contactdish kernel: ahc0: [GIANT-LOCKED]
Feb 26 16:36:26 contactdish kernel: aic7880: Ultra Single Channel A, SCSI Id=7, 
16/253 SCBs
Feb 26 16:36:26 contactdish kernel: pci0:  at device 11.0 (no 
driver attached)
Feb 26 16:36:26 contactdish kernel: fxp0:  port 
0xffc0-0xffdf mem 0xffe0-0xffef,0xfffcc000-0xfffccfff irq 11 at device
12.0 on pci0
Feb 26 16:36:26 contactdish kernel: fxp0: Reserved 0x1000 bytes for rid 0x10 
type 3 at 0xfffcc000
Feb 26 16:36:26 contactdish kernel: fxp0: using memory space register mapping
Feb 26 16:36:26 contactdish kernel: fxp0: PCI IDs: 8086 1229   0001
Feb 26 16:36:26 contactdish kernel: fxp0: Dynamic Standby mode is disabl

Re: Installation instructions for Firefox somewhere?

[Chris Hodgins]

Anthony Atkielski wrote:
Ted Mittelstaedt writes:

I have an Adaptec AAA-131 Ultra 2 card here that is just jumping up and
down to prove you wrong.

This is an AIC7880.  When you have one of those, let me know.

However, I CAN tell you how to go about finding out what you need to
change.  Do you want to do this?  It might mean some effort on your part.

I thought that asking questions here was supposed to help, and I posted
all the information I have, but apparently nobody has a clue.
Anthony,
I might have missed it but I can't find any information about what SCSI 
errors you are receiving.  Why don't you post the errors you are seeing 
 and/or perhaps your dmesg output as well and maybe someone can help 
you.  Without more information noone can do more than guess.

Chris
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[Anthony Atkielski]

Ted Mittelstaedt writes:

> I have an Adaptec AAA-131 Ultra 2 card here that is just jumping up and
> down to prove you wrong.

This is an AIC7880.  When you have one of those, let me know.

> However, I CAN tell you how to go about finding out what you need to
> change.  Do you want to do this?  It might mean some effort on your part.

I thought that asking questions here was supposed to help, and I posted
all the information I have, but apparently nobody has a clue.

-- 
Anthony


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Installation instructions for Firefox somewhere?

[Ted Mittelstaedt]

[EMAIL PROTECTED] wrote:
> Ted Mittelstaedt writes:
>
>> But that was under NT I understand, using NT drivers, right?
>
> Yes.
>
>> I wouldn't put it past the NT driver author of your SCSI card, in an
>> effort to avoid problems, to have written the NT driver so that ALL
>> transactions on the SCSI bus are asynchronous.
>
> I don't know.
>
>> Anyway, if this is it, you will not have been the first person with
>> iffy hardware that worked fine under Windows to have it break under
>> FreeBSD.
>
> I didn't know that Adaptec, Quantum, and Seagate were building such
> "iffy" hardware.
>

I have an Adaptec AAA-131 Ultra 2 card here that is just jumping up and
down to prove you wrong.

Adaptec has some great product.  Unfortunately they came out with
the great product early on, then decided once they got their reputation
that they could make a lot of money by hiding obscenities like the
AAA-131 card in amongst the decent hardware.

Adaptec was also total assholes about giving up the specs for the 2740
so that we could write a device driver for it.  The Linux people also
were affected as well.  This might have been a long time ago but Adaptec
still to this day rather ignores FreeBSD.

> This machine originally cost $9000.  HP did not skimp on the hardware.
>
>>  I just had a machine do this to me Friday - a Pentium Pro 150
>> - but I managed to guess at a change to a BIOS setting that fixed the
>> problem.
>
> Fine.  What do I change on my machine to fix the problem?

I can't tell you what to change.

However, I CAN tell you how to go about finding out what you need to
change.  Do you want to do this?  It might mean some effort on your part.

Ted

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[Anthony Atkielski]

Ted Mittelstaedt writes:

> But that was under NT I understand, using NT drivers, right?

Yes.

> I wouldn't put it past the NT driver author of your SCSI card, in an
> effort to avoid problems, to have written the NT driver so that ALL
> transactions on the SCSI bus are asynchronous.

I don't know.

> Anyway, if this is it, you will not have been the first person with
> iffy hardware that worked fine under Windows to have it break under
> FreeBSD.

I didn't know that Adaptec, Quantum, and Seagate were building such
"iffy" hardware.

This machine originally cost $9000.  HP did not skimp on the hardware.

>  I just had a machine do this to me Friday - a Pentium Pro 150
> - but I managed to guess at a change to a BIOS setting that fixed the
> problem.

Fine.  What do I change on my machine to fix the problem?

-- 
Anthony


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[Anthony Atkielski]

Robert Marella writes:

> Perhaps you could try a live CD. Knoppix or Freesbie and see if the
> trouble is gone.

This machine won't boot from a CD.

-- 
Anthony


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

RE: Installation instructions for Firefox somewhere?

[Ted Mittelstaedt]

[EMAIL PROTECTED] wrote:
> Ted Mittelstaedt writes:
>
>> I agree Ramiro, I've setup dozens and dozens of different SCSI
>> setups, and I think that his problem is hardware, such as incorrect
>> termination, a bad scsi cable, bad connectors on the cable, or an
>> incompatible SCSI/disk combination (which is rare, but it does
>> happen)
>
> No. The machine ran flawlessly for eight years with the
> current hardware
> configuration, no errors, no data loss, even under the heaviest loads.
> There's nothing wrong with the hardware.
>

But that was under NT I understand, using NT drivers, right?

The SCSI standard is pretty big and there's been a lot of go-fast
stuff added into it, and a lot of vendors have done lots of different
things to their adapter cards to make them go fast.  Such as adding
support for tagged commands.  It is entirely up to the writer of the
SCSI device driver whether or not he wants to support the extra go-fast
stuff.

FreeBSD because of it's nature in use as a server on high-quality
hardware, it's drivers tend to take advantage of every last scrap
of go-fast hardware available (unless such hardware is hopeless)
A great example is the ed0 driver and it's support for the 3com 3c503
card - this card can be run in either PIO mode or shared memory mode -
guess which mode the ed0 driver uses?  Even though the wd8013 and
3c503 are the only 2 cards out of the bazillions of ne2000 clones
that support this mode.  You get a gain of perhaps 5% so they go for
it.

I wouldn't put it past the NT driver author of your SCSI card, in an
effort
to avoid problems, to have written the NT driver so that ALL transactions
on the SCSI bus are asynchronous.  Sure this kills your throughput on the
SCSI bus - but with 4GB narrow scsi disks, who is going to notice?  It
greatly reduces support calls because async mode is so slow that even
badly terminated SCSI busses will work - thus nobody with a crapped up
SCSI cable is calling Microsoft and yelling because their server crashes.

Anyway, if this is it, you will not have been the first person with iffy
hardware that worked fine under Windows to have it break under FreeBSD.
I just had a machine do this to me Friday - a Pentium Pro 150 - but I
managed to guess at a change to a BIOS setting that fixed the problem.

Ted

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[Robert Marella]

On Mon, 2005-02-28 at 21:15 +0100, Anthony Atkielski wrote:
> RacerX writes:
> 
> > The hardware has ran for over 8 years - you don't think that after 8 years
> > its going to show wear and tear? I do/would.
> 
> It's not going to suddenly fail on the very day and hour that I install
> FreeBSD.
> 
> > We as humans are not perfect - so that means the things we make can't be
> > perfect either. They will break down, even die. I suspect that if you put
> > in new hardware, the issues will remove themselves.
> 
> No, they will not.  Unless someone can explain to me what the problem is
> with FreeBSD, the only way to resolve the issues is to reinstall Windows
> NT, which doesn't seem to have a problem with these SCSI drives.
> 
Perhaps you could try a live CD. Knoppix or Freesbie and see if the
trouble is gone.

Just a thought :)

Robert

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[Chris]

Anthony Atkielski wrote:
Chris writes:

So - it "could" be it. Never dismiss anything when it comes to hardware.
 Even the littlest thing can cause the greatest catastrophes.

It's illogical to dismiss the extremely high probability of a software
bug or configuration error while embracing the extremely low probability
of a hardware error.
Why not just admit that it's a software problem and try to get to the
bottom of it?
Well - mainly, you seem to be the only one with the issue. S...
--
Best regards,
Chris
If a scientist uncovers a publishable fact, it will
become central to his theory.
His theory, in turn, will become central to all
scientific truth.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[Anthony Atkielski]

Chris writes:

> So - it "could" be it. Never dismiss anything when it comes to hardware.
>   Even the littlest thing can cause the greatest catastrophes.

It's illogical to dismiss the extremely high probability of a software
bug or configuration error while embracing the extremely low probability
of a hardware error.

Why not just admit that it's a software problem and try to get to the
bottom of it?

-- 
Anthony


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[Chris]

Anthony Atkielski wrote:
The chance of these drives both failing _on the same day_ that I install
FreeBSD is less than one in 70 million.  So that's not it.
Umm, I think the odds were greater then that when you think of how we 
all got here - yanno, all the right elements at the right place, at the 
right temps, at the right time, created the Big Bang - and here we are.

So - it "could" be it. Never dismiss anything when it comes to hardware. 
 Even the littlest thing can cause the greatest catastrophes.

--
Best regards,
Chris
The first page the author turns to upon receiving an
advance copy will be the page containing the worst
error.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[Anthony Atkielski]

John writes:

> Have you considered the possibility that windows just didn't
> report the error?

Yes.  If that's true, and if no actual data loss is occurring, then I'm
not worried about the error ... although I'd like to know how to remove
the error messages, in that case.

FreeBSD actually stalls when the errors occur (or more precisely, the
process doing the I/O stalls--the rest of the OS keeps on running).

> Just because it is unreported under windows doesn't mean it's
> not happening...

True, but I'd need to establish that for certain; I'm not going to just
assume that it was happening and Windows ignored it.

> And just because it has been working for 8 years without a problem doesn't
> mean it will go working for a further 8, even if you change nothing..

The chance of these drives both failing _on the same day_ that I install
FreeBSD is less than one in 70 million.  So that's not it.

> Saying that, I do notice that sometimes, I do get scsi errors on boot,
> but then again I have modified the delay in probing the devices from
> 15000ms to 5000 in order to speed up boot. Probably unwise, given that
> the system has 2 scsi cards in, and as well as 5 drives, a scsi cdrom,
> it also has a scanner, which is slow to wake up.

I left the delay at 15 seconds for this reason (there's a second SCSI
controller on the system, although I haven't used that thus far), but
that doesn't seem to help.

> Saying *that*, on boot, one card always boots up fast. Sometimes the
> other card also boots up, sometimes it times out. But at the login
> prompt, everything on the system is up. This is prior to the boot
> loader loading, so it cannot possibly be FreeBSD.

Some SCSI hardware takes a long time to initialize.

> You haven't told us what you mean by scsi errors. Is it like I describe, or is
> it subsequent to bootup?

I've posted the errors in a previous message (it's a lot of text).

It occurs mostly during periods of high disk activity, especially when
I'm trying to download packages or something.  It doesn't seem to occur
at all on an idle system, which is logical, I guess.

Another problem is that the system simply refuses to boot from the SCSI
disk; I have to boot from the installation diskettes, then change the
current device in the loader program, point to the SCSI disk, and boot
again, which works perfectly (but it takes 15 minutes to go through the
whole process, and of course it cannot be automated).  Oddly enough, I
installed boot0cfg to put a boot selector out there, and the hardware
finds and runs that off the SCSI disk with no problem.  It even gives
the FreeBSD slice as a choice for boot.  But when I actually select the
FreeBSD slice, it freezes.  I'm sure this isn't hardware, either.
Something is wrong in the way the disks are set up, or there's a bug.

-- 
Anthony


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[John]

On Mon, 28 Feb 2005 22:35:54 +0100, Anthony Atkielski wrote
> Chris Hodgins writes:
> 
> > Sounds like the perfect time for them to go wrong.  They have been doing
> > the same thing for 8 years without problem.
> 
> They are still doing the same thing today.  There is no additional
> stress in changing operating systems.
> 
> > Suddenly you come along and give them a good old shake up...I would
> > imagine this would be the perfect occasion for this to happen.
> 
> I have no idea what you mean by this.  No "shake-up" is involved.  They
> do the same I/O they've always been doing.  They have no idea whether
> it's Windows NT starting the I/O or FreeBSD.  It all looks the same 
> to the drives.

Have you considered the possibility that windows just didn't report the error?
Just because it is unreported under windows doesn't mean it's not happening...

And just because it has been working for 8 years without a problem doesn't
mean it will go working for a further 8, even if you change nothing..

Saying that, I do notice that sometimes, I do get scsi errors on boot, but
then again I have modified the delay in probing the devices from 15000ms to
5000 in order to speed up boot. Probably unwise, given that the system has 2
scsi cards in, and as well as 5 drives, a scsi cdrom, it also has a scanner,
which is slow to wake up.

Saying *that*, on boot, one card always boots up fast. Sometimes the other
card also boots up, sometimes it times out. But at the login prompt,
everything on the system is up. This is prior to the boot loader loading, so
it cannot possibly be FreeBSD.

You haven't told us what you mean by scsi errors. Is it like I describe, or is
it subsequent to bootup?
--
[EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Installation instructions for Firefox somewhere?

[Anthony Atkielski]

Chris Hodgins writes:

> Sounds like the perfect time for them to go wrong.  They have been doing
> the same thing for 8 years without problem.

They are still doing the same thing today.  There is no additional
stress in changing operating systems.

> Suddenly you come along and give them a good old shake up...I would
> imagine this would be the perfect occasion for this to happen.

I have no idea what you mean by this.  No "shake-up" is involved.  They
do the same I/O they've always been doing.  They have no idea whether
it's Windows NT starting the I/O or FreeBSD.  It all looks the same to
the drives.

-- 
Anthony


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"