Re: printing with cups - gnome-office -solved

2004-10-10 Thread hoe-waa

On Wednesday, October 6, 2004 7:44 pm
I sent this query prematurely.

 
 # Aloha
 # On this past Sunday(10-3-4) I posted this question to freebsd-gnome.
 # I have not received any responses. Can anyone on this list help?
 # Thanks
 
 I am having a problem with CUPS and Gnome. I am running
 Gnome 2.6.2, Gnome-Office, and Xorg all installed via ports.
 
 I have a P4 2.6 with 1G of ram 
 
 %uname -a
 FreeBSD p4.hawaii.rr.com 5.2.1-RELEASE-p9 FreeBSD 
 5.2.1-RELEASE-p9 #9: Sun Oct  3 10:25:03 HST 2004 
 root at p4.hawaii.rr.com:/usr/obj/usr/src/sys/P4BSD1  i386
 
 I recently attached a HP 890C DeskJet printer. I installed
 Cups and gnome-cups-manager from ports. I am able to use the
 web interface and install the printer. The test page prints
 fine. I can also print a text file from gedit without trouble.
 
 # I can also print a test page from gnome-cups-manager
 
 The problem is with AbiWord2, gnumeric and the pdf files. The
 Print Preview screens show blank and when I click on file; print;
 and then the paper tab, the Paper size field is not bold and
 reads no options are defined. I did define the paper in the
 web setup of cups and these programs do show the 890C as the printer.
 
 Of course, I am unable to print from these programs.
 
 Here is a little info:
 
 %pkg_info | grep cups
 cups-1.1.20.0   The Common UNIX Printing System: Metaport to 
 install comple
 cups-base-1.1.20.0  The Common UNIX Printing System: headers, libs, 
  daemons
 cups-lpr-1.1.20.0   The CUPS BSD and system V compatibility 
 binaries (lp* comma
 cups-pstoraster-7.07_1 GNU Postscript interpreter for CUPS printing 
 to non-PS prin
 gnome-cups-manager-0.18_1,1 Admistration tool for cups
 libgnomecups-0.1.8,1 Support library for gnome cups admistration
 
 %cat /etc/printcap
 # This file was automatically generated by cupsd(8) from the
 # /usr/local/etc/cups/printers.conf file.  All changes to this file
 # will be lost.
 HP890C|HP890C:rm=p4.hawaii.rr.com:rp=HP890C:
 
 
 I have also done a portupgrade -f libgnomeprint-\* libgnomeprintui-
 \*to no avail.
 
 If anything else is needed I will be overjoyed to provide it.
 
 Please CC me as I do not subscribe to this list. Thanks for your time.
 
 Robert

I thought I had exhausted all the resources available to me but once
again I proved myself wrong. For the archives and all the newbies (me)
that have struggled with Cups. I found the simple answer here

http://www.csua.berkeley.edu/~ranga/notes/freebsd_cups.html

Specifically, I ran the following script in /usr/bin

#!/bin/sh
for i in lp* ; do mv $i $i.default ; ln -s /usr/local/bin/$i $i ; done

Sorry for the noise.
Robert

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


moving from 5.2.1 to 5.3Beta?

2004-10-07 Thread hoe-waa
Aloha

I have a quick question. I am going to upgrade 
one of my systems from 5.2.1P9 to 5.3Beta7.

I have cvsup'd the source and when checking 
UPDATING I came across this:

20041001:
The following libraries had their version number bumped up:
/lib/libm.so.2 - libm.so.3
/lib/libreadline.so.4 - libreadline.so.5
/usr/lib/libhistory.so.4 - libhistory.so.5
/usr/lib/libopie.so.2 - libopie.so.3
/usr/lib/libpcap.so.2 - libpcap.so.3
FreeBSD 4.10 versions of these libraries will be added to the
compat4x collection.  If you expect to be able to run old 4.X
executables you will need to remove the old versions of these
libraries.  However note that any 5.X executables you have built
will stop working once you remove those old libraries.  You should
have all your ports/packages rebuilt before removing the old
libraries.

I had seen some discussion rearding this on the list and had
made a note in my head. 

Am I reading this correct that before I build/install world,
I should do a portupgrade -a ???

All of my ports are the latest according to portversion.

I just wanted to check before I went any further.

Thank you
Robert

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


Re: moving from 5.2.1 to 5.3Beta?

2004-10-07 Thread hoe-waa
Thanks, I'll get right on it.

Robert
On Thu, Oct 07, 2004 at 05:10:43PM -1000, [EMAIL PROTECTED] wrote:
 Aloha
 
 I have a quick question. I am going to upgrade 
 one of my systems from 5.2.1P9 to 5.3Beta7.
 
 I have cvsup'd the source and when checking 
 UPDATING I came across this:
 
 20041001:
   The following libraries had their version number bumped up:
   /lib/libm.so.2 - libm.so.3
   /lib/libreadline.so.4 - libreadline.so.5
   /usr/lib/libhistory.so.4 - libhistory.so.5
   /usr/lib/libopie.so.2 - libopie.so.3
   /usr/lib/libpcap.so.2 - libpcap.so.3
   FreeBSD 4.10 versions of these libraries will be added to the
   compat4x collection.  If you expect to be able to run old 4.X
   executables you will need to remove the old versions of these
   libraries.  However note that any 5.X executables you have built
   will stop working once you remove those old libraries.  You should
   have all your ports/packages rebuilt before removing the old
   libraries.
 
 I had seen some discussion rearding this on the list and had
 made a note in my head. 
 
 Am I reading this correct that before I build/install world,
 I should do a portupgrade -a ???

No, that won't affect things.  After you installworld, you should add
the libmap entries as above, and then at your later convenience you
can portupgrade -af to rebuild all ports so you can remove the
mapping.

kris

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


printing with cups - gnome-office

2004-10-06 Thread hoe-waa

#   Aloha
#   On this past Sunday(10-3-4) I posted this question to freebsd-gnome.
#   I have not received any responses. Can anyone on this list help?
#   Thanks

I am having a problem with CUPS and Gnome. I am running
Gnome 2.6.2, Gnome-Office, and Xorg all installed via ports.

I have a P4 2.6 with 1G of ram 

%uname -a
FreeBSD p4.hawaii.rr.com 5.2.1-RELEASE-p9 FreeBSD 
5.2.1-RELEASE-p9 #9: Sun Oct  3 10:25:03 HST 2004 
root at p4.hawaii.rr.com:/usr/obj/usr/src/sys/P4BSD1  i386

I recently attached a HP 890C DeskJet printer. I installed
Cups and gnome-cups-manager from ports. I am able to use the
web interface and install the printer. The test page prints
fine. I can also print a text file from gedit without trouble.

#   I can also print a test page from gnome-cups-manager

The problem is with AbiWord2, gnumeric and the pdf files. The
Print Preview screens show blank and when I click on file; print;
and then the paper tab, the Paper size field is not bold and
reads no options are defined. I did define the paper in the
web setup of cups and these programs do show the 890C as the printer.

Of course, I am unable to print from these programs.

Here is a little info:

%pkg_info | grep cups
cups-1.1.20.0   The Common UNIX Printing System: Metaport to install comple
cups-base-1.1.20.0  The Common UNIX Printing System: headers, libs,  daemons
cups-lpr-1.1.20.0   The CUPS BSD and system V compatibility binaries (lp* comma
cups-pstoraster-7.07_1 GNU Postscript interpreter for CUPS printing to non-PS prin
gnome-cups-manager-0.18_1,1 Admistration tool for cups
libgnomecups-0.1.8,1 Support library for gnome cups admistration

%cat /etc/printcap
# This file was automatically generated by cupsd(8) from the
# /usr/local/etc/cups/printers.conf file.  All changes to this file
# will be lost.
HP890C|HP890C:rm=p4.hawaii.rr.com:rp=HP890C:


I have also done a portupgrade -f libgnomeprint-\* libgnomeprintui-\*
to no avail.

If anything else is needed I will be overjoyed to provide it.

Please CC me as I do not subscribe to this list. Thanks for your time.

Robert

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


Re: Is there a reverse Network Address Translation???

2004-09-30 Thread hoe-waa
On Thursday, September 30, 2004
stheg olloydson [EMAIL PROTECTED]
spoke as if he was talking about me.



snip
 
 Most certainly! I was taking into account the OP's relative newness to
 the unix world. While it may seem condescending, I find newer users
 tend to get overwhelmed when more experienced users try to supply an
 exhaustive answer. For example, bringing up PKI would almost certainly
 lead to a discussion of algorithm choice, etc. The result in these
 cases often is the new user drops out of the thread (and does 
 whatever)while the old hands bikeshed what must seem like (and 
 sometimes is) arcane minutiae. 

I have been using FreeBSD for about 10 months as a hobbyist/learning tool.
I lurk on the lists to pick up pointers and solve my own little problems. 
Because I am retired and am only a hobyist, I do exactly as Stheg has indicated
above. I will start reading a thread to learn something new or it may be
something on my list of features/programs in my future agenda. When it gets 
too deep for my knowledge level, I will drop out and try to make a mental 
note that it will always be in the archives.

In the time I started with FreeBSD, I have installed it on 4 desktops and
2 laptops. I am running 5.3betas on 3 boxes and 5.2.1P9 on the others. I have
solved many of my troubles by lurking and have asked the list a few questions.
I have always received polite, helpful responses even if they did not solve
my troubles. More times than not, I will solve the problems by research rather
than sending to questions.

One needs a strong base to build a large pyramid of knowledge. 

If I were allowed to issue karma points, I would give a couple of dozen to Stheg.

Just my 2 seashells

Robert

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


Re: xf86config for Toshiba satellite pro laptop

2004-08-29 Thread hoe-waa
Aloha Vaughan,


Vaughan Moore wrote:

I'm a complete newbie and I'm trying to set up X server on a Toshiba
Satellite pro 4620dvd laptop.  Everytime I run through xf86cfg or
xf86cfg -textmode I get the error message The XFree86 configuration process
seems to have failed.  Would you like to try again?  Obviously, this is a
bit frustrating.

Did you mean a 4260dvd?  I cannot find anything on a 4620dvd.

If you had a slight case of dyslexia or maybe a little fat fingering, :o) I may 
be of some help. I have FreeBSD 5.3Beta1 loaded on a HP Pavillion N5310.

I checked the specs on the Toshiba Pro 4260dvd (attached pdf) and it has the 
same video driver as my HP. i.e. s3 Savage IX.

So, FWIW, Here are the important bits from my xorg.conf

Section Monitor
HorizSync   31.5 - 80
VertRefresh 55 - 61

Section Device
Identifier  Card0
Driver  savage
VendorName  S3 Inc.
BoardName   86c270-294 Savage/IX-MV
BusID   PCI:1:1:0


Section Screen
DefaultDepth24

SubSection  Display
Viewport0 0
Depth   24
Modes   1024x768  800x600



I really hope this helps. At one time I had either Lindows (Linspire) or SuSE
loaded on this computer. That is where I found the horizontal and vertical data.

Plagarize whenever you can!

You might also try pciconf -lv to see if your board name and bus id are correct.

Best of luck

Robert



4260dvd-specs
Description: Binary data
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Microsoft Cordless Optical Mouse and 5.2

2004-08-28 Thread hoe-waa
From: Peter Leftwich [EMAIL PROTECTED]
Date: Saturday, August 28, 2004 10:49 am

 Doh!  My mouse (a Microsoft Cordless Optical Mouse) worked fine with
 Knoppix/Linux OS and with XP of course but does NOT work with 
 FreeBSD 5.2!
 
 I tried plugging it in as PS/2 but the little light does not come 
 on.  My
 /etc/rc.conf has /dev/sysmouse and type auto but still no go.  I am
 posting this in the hopes that it will partially dissuade those 
 consideringbuying this make and model mouse!  :\
 
 Will someone note this conflict or malfunction at:
 Title FreeBSD 5.2.1-RELEASE Hardware Notes
 Current URL   
 http://www.freebsd.org/releases/5.2.1R/hardware.htmlURL of current 
 anchor http://www.freebsd.org/releases/5.2.1R/hardware-i386.html
 
 ?
 
 --
 Peter Leftwich

I have the exact same mouse working on 5.2.1

Here is the section from XF86Config

Section InputDevice
Identifier  Mouse0
Driver  mouse
Option  Protocol auto
Option  Device /dev/sysmouse
Option  ZaxisMapping  4 5
EndSection


In /etc/rc.conf I have the line

moused_enable=YES

I am using the adapter that came with the mouse
and it is plugged into the PS2 port.

I find that the mouse is responsive and I really
like the feel. Now if only MS could do something 
with software.

Good Luck

Robert

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


Re: changing card in a reader (revisited)

2004-08-23 Thread hoe-waa
From: Anish Mistry [EMAIL PROTECTED]
Date: Monday, August 23, 2004 7:41 am

 I started to get this too, and just got an answer on the CURRENT 
 list.  What 
 you need to do the rescan the GEOM structure is:
 cat /dev/null  /dev/da0
 cat /dev/null  /dev/da1
 etc...
 This worked for me.  Apparently camcontrol was doing stuff before 
 is wasn't 
 supposed to.  Hope this helps.
 - -- 
 Anish Mistry


Aloha Anish and thanks for the info.

I was beginning to wonder if this was only my problem.

I still have an anomaly even with this procedure. Are
you running this as root?

Here is what I found.

I have a 32MB card in the reader. I start a terminal as a normal user
and verify permissions on the device. da2 and da2s1 are set perm in
/etc/devfs.conf

%pwd
/usr/home/robert
%ls -l /dev/da*
crw-r-  1 root  operator4,  30 Aug 23 16:50 /dev/da0
crw-r-  1 root  operator4,  31 Aug 23 16:50 /dev/da1
crw-rw  1 root  operator4,  32 Aug 23 16:50 /dev/da2
crw-rw  1 root  operator4,  34 Aug 23 16:50 /dev/da2s1
crw-r-  1 root  operator4,  33 Aug 23 16:50 /dev/da3
%
%mount_msdosfs /dev/da2s1 ~/camera
%ls -l camera/dcim/100olymp/
total 6752
-r-xr-xr-x  1 robert  robert  680523 Jan  1  2000 p1010074.jpg
-r-xr-xr-x  1 robert  robert  672166 Jun  5 07:19 p6050002.jpg
-r-xr-xr-x  1 robert  robert  677171 Jun  5 07:19 p6050003.jpg
-r-xr-xr-x  1 robert  robert  684658 Jun  5 07:23 p6050004.jpg
-r-xr-xr-x  1 robert  robert  664210 Jun  5 07:23 p6050005.jpg
-r-xr-xr-x  1 robert  robert  663849 Jun  5 07:24 p6050006.jpg
-r-xr-xr-x  1 robert  robert  689533 Jun  5 07:37 p6050009.jpg
-r-xr-xr-x  1 robert  robert  697084 Jun  5 07:37 p6050010.jpg
-r-xr-xr-x  1 robert  robert  691391 Jun  5 07:59 p6050011.jpg
-r-xr-xr-x  1 robert  robert  695390 Jun  5 07:59 p6050012.jpg
%
%umount camera

I can mount and display the photos so then I umount and change to 
a 128MB card.  After doing the folowing command as suggested, the 
permissions on da2s1 have changed.

%cat /dev/null  /dev/da2
%mount_msdosfs /dev/da2s1 ~/camera
mount_msdosfs: /dev/da2s1: Permission denied
%ls -l /dev/da*
crw-r-  1 root  operator4,  30 Aug 23 16:50 /dev/da0
crw-r-  1 root  operator4,  31 Aug 23 16:50 /dev/da1
crw-rw  1 root  operator4,  32 Aug 23 16:50 /dev/da2
crw-r-  1 root  operator4,  35 Aug 23 16:50 /dev/da2s1
crw-r-  1 root  operator4,  33 Aug 23 16:50 /dev/da3

I have to then su to root and change the permissions back to 660.
It then mounts fine.

%su
Password:
frankie# chmod 660 /dev/da2s1
frankie# exit
exit
%mount_msdosfs /dev/da2s1 ~/camera
%ls -l camera/dcim/100olymp/
total 2048
-rwxr-xr-x  1 robert  robert  684889 Jan  1  2000 p1010001.jpg
-rwxr-xr-x  1 robert  robert  687084 Jan  1  2000 p1010002.jpg
-rwxr-xr-x  1 robert  robert  712401 Jan  1  2000 p1010003.jpg
%

Is there something that I am missing? Why am I losing the w for
group operator?

Either way, this is better than unplugging the USB cable or running
fdisk -i on the slice.

Robert


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


Re: Mouse problems with KVM switch

2004-08-19 Thread hoe-waa

From: thrawn [EMAIL PROTECTED]
Date: Thursday, August 19, 2004 6:18 am

 Hi,
 
 I have just brought this KVM switch:
 http://www.level1.com/products3.php?sklop=20id=590430
 
 But Im having major problems with getting the mouse to work under 
 FreeBSD. Even the keyboard does not work sometimes. This KVM switch 
 has 
 support for hotkey and also supports emulation on both mouse and 
 keyboard.
 When I boot up my system and see the BIOS on the computer the 
 keyboard 
 works just fine. Then when it continues to boot and comes to the 
 loader, 
 it still works. And the it starts to load the kernel. But then when 
 i 
 get to the login prompt the keyboard does not work.
 
 And sometimes even thought I stay with the computer the hole boot 
 process I can't even use the keyboard. So I have to use ssh to 
 login to 
 the computer and make it reboot to regain the keyboard. I have also 
 tried to change the cables but I get the same results. And It works 
 with 
 no problems under Windows XP Pro.
 
 The system that im using is FreeBSD 5.2.1-p9, at least on this system.
 
 I  have also two other computers that Im running FreeBSD-stable on. 
 On 
 one of my FreeBSD-stable machines I have hade a working mouse under 
 X 
 Windows System (Xorg latest from ports).
 
 But then I rebooted the system and when I started xdm, it found the 
 mouse but when I move it around It didn't move like it should. It 
 took 
 some seconds before it moved and it did not move like it should, 
 jumps 
 several ramdom cm/inches on the screen (Perhaps in the direction 
 that I 
 move the mouse im not sure). Its on usable in other words.
 
 I have also tryied to use moused under FreeBSD but I get the same 
 fault/problem. I also have a problem if I do not have this machine 
 selected when I boot. Then when I switch to it when the boot of the 
 FreeBSD system has complete, The screen on the monitor just blinks.
 
 Still the keyboard works because I can press two times Left Ctrl 
 and 
 then 1 to 4 to change the computer Im controlling. This I can not 
 do 
 with the FreeBSD 5.2.1-p9 system I can only see the screen but have 
 to 
 change the computer im controlling by pressing the button on the 
 switch box.
 
 I have tried to remove the cables and put them back again. But that 
 does 
 not help, the only solution I can see is to reboot the system and 
 let it 
 boot with it selected. I have also booted up with the mouse 
 directly 
 connected to the computer. Then when the system boot was completed 
 I 
 moved the mouse around to see that it did work. After that I 
 plugged 
 back the cable from the switch in to the computers mouse port. And 
 the 
 plugged the mouse back in the switch box, that did not work either.
 
 I have also added flags to both psm0 and atkbd in my kernel config:
 
 # atkbdc0 controls both the keyboard and the PS/2 mouse
 device  atkbdc0 at isa? port IO_KBD
 device  atkbd0  at atkbdc? irq 1 flags 0x0
 device  psm0at atkbdc? irq 12 flags 0x0
 
 I have also tried with the flags set to 0x100 on both atkbd0 and 
 psm0, 
 but that doesn't seem to make any diffrance. I have done this on my 
 FreeBSD 5.2.1-p9 box as well. I have also changed it in:
 
 /boot/device.hints
 
 But I don't get it working correctly either by that.
 
 Does anybody have a clue or have hade any similar problems and/or 
 who 
 could shine some light on this problem?
 
 Mvh Mattias Björk


Aloha Mattias

This all sounds familiar. I too had a lot of trouble
with a KVM switch. Actually, I tried two with the same
problem you are alluding to.

I came to the conclusion that the mouse will not work
through the KVM switch using FBSD, or at least I never
got it to.

I have two computers that are both running 5.2.1

I have connected a mouse directly to each computer.
I still had to shutdown both computers and connect 
the cables for the monitor and keyboard from each to
the KVM. I also connected and old mouse to the output
of the KVM.

With all this connected, I then powered up both computers. All seems to work fine with 
the inconvenience
of having to use 2 meese. I seldom have to go into one
fo the computers, so I can live with it.

This is probably not the answer you were looking for
but you were also looking for others who had problems.

Best of Luck
Robert


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


Re: Mouse problems with KVM switch

2004-08-19 Thread hoe-waa

From: Mattias Björk [EMAIL PROTECTED]

 Hello,
 
 [EMAIL PROTECTED] wrote:
  From: thrawn [EMAIL PROTECTED]
  Date: Thursday, August 19, 2004 6:18 am

snip
 
 Does anybody have a clue or have hade any similar problems and/or 
 who 
 could shine some light on this problem?
 
 Mvh Mattias Björk
  
snip
  
  

 
 Does your KVM support hotkey? I have another KVM switch erlier that 
 did 
 work better but It didn't have support for hotkey. But It did not 
 work 
 perfectly but atleast the mouse worked mutch better if you compare 
 to this.

Yes, the hotkeys work as designed.

 
  I came to the conclusion that the mouse will not work
  through the KVM switch using FBSD, or at  Aloha Mattias
  
 Actually, I tried two with the same
  problem you are alluding to. least I never
  got it to.

I had bought one on the mainland last month. When I
couldn't get the mouse to work, I bought another here
on the Big Island. I acted the same so I returned it
and am using the original.

 Or perhaps the KVM  that I have been using are Crap or something in that direction.

Me Too!!
 

 
  I have connected a mouse directly to each computer.
Forgot to mention that both rodents are usb.

Then again its kind of dumb to have a KVM if you 
still have to use the mouse directly connected 
 to the computer.

At least I don't have to have 2 monitors and 2 keyboards
on the desk.


 What is the brand and model of your KVM?

Made in China

Robert


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


Changing cards in a reader (new info)

2004-07-29 Thread hoe-waa
Aloha

I have some additional information regarding this problem.

I was reading some of the man pages for the ump-teenth time and
I thought I would try something with fdisk.

I started with a 128MB card in the reader.

hp# mount_msdosfs /dev/da2s1 /mnt/olympus/
hp# ls -l /mnt/olympus/
hp# ls -l /mnt/olympus/dcim/100olymp/
total 6752
-r-xr-xr-x  1 root  wheel  680523 Jan  1  2000 p1010074.jpg
-r-xr-xr-x  1 root  wheel  672166 Jun  5 07:19 p6050002.jpg
-r-xr-xr-x  1 root  wheel  677171 Jun  5 07:19 p6050003.jpg
-r-xr-xr-x  1 root  wheel  684658 Jun  5 07:23 p6050004.jpg
-r-xr-xr-x  1 root  wheel  664210 Jun  5 07:23 p6050005.jpg
-r-xr-xr-x  1 root  wheel  663849 Jun  5 07:24 p6050006.jpg
-r-xr-xr-x  1 root  wheel  689533 Jun  5 07:37 p6050009.jpg
-r-xr-xr-x  1 root  wheel  697084 Jun  5 07:37 p6050010.jpg
-r-xr-xr-x  1 root  wheel  691391 Jun  5 07:59 p6050011.jpg
-r-xr-xr-x  1 root  wheel  695390 Jun  5 07:59 p6050012.jpg
hp#
hp# umount /mnt/olympus/

Replace the 128MB with a 8MB

hp# mount_msdosfs /dev/da2s1 /mnt/olympus/
mount_msdosfs: /dev/da2s1: Invalid argument

Fails to mount

hp# fdisk -i da2
*** Working on device /dev/da2 ***
parameters extracted from in-core disklabel are:
cylinders=7 heads=64 sectors/track=32 (2048 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=7 heads=64 sectors/track=32 (2048 blks/cyl)

Do you want to change our idea of what BIOS thinks ? [n]
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 1 (0x01),(Primary DOS with 12 bit FAT)
start 25, size 15975 (7 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 10;
end: cyl 249/ head 3/ sector 16
Do you want to change it? [n]
The data for partition 2 is:
UNUSED
Do you want to change it? [n]
The data for partition 3 is:
UNUSED
Do you want to change it? [n]
The data for partition 4 is:
UNUSED
Do you want to change it? [n]
Partition 1 is marked active
Do you want to change the active partition? [n]

We haven't changed the partition table yet.  This is your last chance.
parameters extracted from in-core disklabel are:
cylinders=7 heads=64 sectors/track=32 (2048 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=7 heads=64 sectors/track=32 (2048 blks/cyl)

Information from DOS bootblock is:
1: sysid 1 (0x01),(Primary DOS with 12 bit FAT)
start 25, size 15975 (7 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 10;
end: cyl 249/ head 3/ sector 16
2: UNUSED
3: UNUSED
4: UNUSED
Should we write new partition table? [n]
hp#

I answer no to all questions and then it mounts!!

hp# mount_msdosfs /dev/da2s1 /mnt/olympus/
hp# ls -l /mnt/olympus/dcim/100olymp/
total 680
-rwxr-xr-x  1 root  wheel  694158 Jul 12 18:27 p7120001.jpg
hp#

Of course this (fdisk) has to be done as root. If I want to mount 
and umount as a standard user I need to chmod 660 da2s1 each time
the card is changed and fdisk -i is run.

I hope this triggers some memory cells on all the experienced users
on this list. Is there a better way to do this?

I am sorry my posts always seem to run long but I want to include 
what I feel is important.

Thanks for all the help I have received and all the future help I 
hope I get :o)

Robert

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


Changing cards in a reader (next step??)

2004-07-26 Thread hoe-waa
Aloha

I need to know where to go next. I have originated two previous threads
regarding this problem. 

http://lists.freebsd.org/pipermail/freebsd-questions/2004-June/050819.html
http://lists.freebsd.org/pipermail/freebsd-questions/2004-July/053047.html

I have followed all suggestions and responded with the output of my attemps. 
The problem remains unresolved. I have also requested that if anyone has this
working *properly* to respond but no one did.

Can I *assume* that this is a bug? Is the next step filing a bug report?
Being a newbie, can someone steer me in the right direction to file a bug 
report. Is there something else I should do?

Any assistance would be appreciated.

Thank You
Robert

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


Re: Changing cards in a reader (next step??)

2004-07-26 Thread hoe-waa

From: David Kelly [EMAIL PROTECTED]
Date: Monday, July 26, 2004 7:47 am


 
 On Jul 26, 2004, at 12:26 PM, [EMAIL PROTECTED] wrote:
 
  I have followed all suggestions and responded with the output of 
 my 
  attemps. The problem remains unresolved. I have also requested that
  if anyone has this working *properly* to respond but no one did.
 
 Why not install /usr/ports/emulators/mtools/ and configure O: 
 drive 
 (O for Olympus) as /dev/da2s1 ?
 
Aloha and thanks for responding. I hadn't tried mtools so I did as you
reccommended. The results were less than satisfactory. The problem is
when I am changing to a different size card. 

I start with a 128MB SmartMedia card in the reader.

hp# mdir O:/dcim/100olymp
 Volume in drive O has no label
Directory for O:/dcim/100olymp

.DIR 05-30-2004  15:59
..   DIR 05-30-2004  15:59
p6050002 jpg672166 06-05-2004   7:19
p6050003 jpg677171 06-05-2004   7:19
p6050004 jpg684658 06-05-2004   7:23
p6050005 jpg664210 06-05-2004   7:23
p6050006 jpg663849 06-05-2004   7:24
p6050009 jpg689533 06-05-2004   7:37
p6050010 jpg697084 06-05-2004   7:37
p6050011 jpg691391 06-05-2004   7:59
p6050012 jpg695390 06-05-2004   7:59
p1010074 jpg680523 01-01-2000   0:00
   12 files   6 815 975 bytes
124 059 648 bytes free

Then I remove it and place a 8MB SM card in the reader.

hp# mdir O:/dcim/100olymp
init O: non DOS media
Cannot initialize 'O:'

If I unplug and replug the USB cable

hp# mdir O:/dcim/100olymp
 Volume in drive O has no label
Directory for O:/dcim/100olymp

.DIR 06-26-2004  14:24
..   DIR 06-26-2004  14:24
p7120001 jpg694158 07-12-2004  18:27
3 files 694 158 bytes
  7 446 528 bytes free

The display is different using mtools but the results are the
same.

Thanks again for the help. I hope you have another idea or two.

Robert

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


Re: changing card in a reader (revisited)

2004-07-22 Thread hoe-waa



From: [EMAIL PROTECTED]
Date: Tuesday, July 20, 2004 9:25 am

 From: [EMAIL PROTECTED]
 Date: Tuesday, July 20, 2004 8:58 am

  
  From: Dinesh Nair [EMAIL PROTECTED]
  Date: Tuesday, July 20, 2004 7:44 am
  
   
   what does '/sbin/fdisk da2' say ?
   
   Regards,   
  
  
  Aloha and Mahalo
  
  I do get something different displayed with fdisk.
  
  insert and mount 8MB card
  
  hp# mount_msdosfs /dev/da2s1 /mnt/olympus
  hp# /sbin/fdisk da2
  *** Working on device /dev/da2 ***
  parameters extracted from in-core disklabel are:
  cylinders=7 heads=64 sectors/track=32 (2048 blks/cyl)
  
  parameters to be used for BIOS calculations are:
  cylinders=7 heads=64 sectors/track=32 (2048 blks/cyl)
  
  Media sector size is 512
  Warning: BIOS sector numbering starts with sector 1
  Information from DOS bootblock is:
  The data for partition 1 is:
  sysid 1 (0x01),(Primary DOS with 12 bit FAT)
 start 25, size 15975 (7 Meg), flag 80 (active)
 beg: cyl 0/ head 1/ sector 10;
 end: cyl 249/ head 3/ sector 16
  The data for partition 2 is:
  UNUSED
  The data for partition 3 is:
  UNUSED
  The data for partition 4 is:
  UNUSED
  
  hp# umount /mnt/olympus
  
  change to 128MB card
  
  hp# mount_msdosfs /dev/da2s1 /mnt/olympus
  mount_msdosfs: /dev/da2s1: Invalid argument
  hp# /sbin/fdisk da2
  *** Working on device /dev/da2 ***
  parameters extracted from in-core disklabel are:
  cylinders=125 heads=64 sectors/track=32 (2048 blks/cyl)
  
  parameters to be used for BIOS calculations are:
  cylinders=125 heads=64 sectors/track=32 (2048 blks/cyl)
  
  Media sector size is 512
  Warning: BIOS sector numbering starts with sector 1
  Information from DOS bootblock is:
  The data for partition 1 is:
  sysid 6 (0x06),(Primary 'big' DOS (= 32MB))
 start 47, size 255953 (124 Meg), flag 80 (active)
 beg: cyl 0/ head 1/ sector 16;
 end: cyl 499/ head 15/ sector 32
  The data for partition 2 is:
  UNUSED
  The data for partition 3 is:
  UNUSED
  The data for partition 4 is:
  UNUSED
  hp#
  
  Is it the Primary 'big that's messing me up?
  
  Robert
  
 Forfeiting 6 karma points for responding to my own post.
 
 Being curious, I unplugged and replugged the USB cable.
 I then reran fdisk with the 128MB card mounted.
 
 hp# ls -l /dev/da*
 crw-r-  1 root  operator4,  27 Jul 19 06:19 /dev/da0
 crw-r-  1 root  operator4,  28 Jul 19 06:19 /dev/da1
 crw-r-  1 root  operator4,  29 Jul 19 06:19 /dev/da2
 crw-r-  1 root  operator4,  30 Jul 19 06:19 /dev/da2s1
 crw-r-  1 root  operator4,  31 Jul 19 06:19 /dev/da3
 crw-r-  1 root  operator4,  24 Jul 19 06:19 /dev/da4
 crw-rw  1 root  wheel   4,  26 Jul 19 06:19 /dev/da4s1
 hp# mount_msdosfs /dev/da2s1 /mnt/olympus
 hp# /sbin/fdisk da2
 *** Working on device /dev/da2 ***
 parameters extracted from in-core disklabel are:
 cylinders=125 heads=64 sectors/track=32 (2048 blks/cyl)
 
 parameters to be used for BIOS calculations are:
 cylinders=125 heads=64 sectors/track=32 (2048 blks/cyl)
 
 Media sector size is 512
 Warning: BIOS sector numbering starts with sector 1
 Information from DOS bootblock is:
 The data for partition 1 is:
 sysid 6 (0x06),(Primary 'big' DOS (= 32MB))
start 47, size 255953 (124 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 16;
end: cyl 499/ head 15/ sector 32
 The data for partition 2 is:
 UNUSED
 The data for partition 3 is:
 UNUSED
 The data for partition 4 is:
 UNUSED
 
 It looks the same!
 
 Robert
 

I guess I lost a lot more than 6 karma points! It's 
been two days since my last post and I haven't received
any more responses.

Please permit me to ask if there is anyone reading this
list who has this working. Specifically, the ability
to replace a card of a different size in a card reader
and be able to mount the new card.

If I have violated any Kapu or in any other way did a bad.
let me know and I will strive to do better in the future.

Mahalo
Robert




 

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


Re: changing card in a reader (revisited)

2004-07-22 Thread hoe-waa

From: Robert Storey [EMAIL PROTECTED]
Date: Friday, July 23, 2004 1:46 am


 I guess I missed your first post.
 
 One thing I don't see in your posts is any mention of whether or not
 you're running FBSD 4.x or 5.x. My experience with 4.x is that 
 cards of
 any type either don't work or work badly. I've had much better luck 
 with5.x. Aside from drivers, I believe this is due to the devfs 
 which 5.x
 uses. So if you're using 4.x, consider either upgrading or at least
 experimenting with the FreeSBIE livecd to see what happens.
 
 regards,
 Robert
 
Thanks for responding. As posted earlier

%uname -a
FreeBSD hp.hawaii.rr.com 5.2.1-RELEASE-p9 FreeBSD 
5.2.1-RELEASE-p9 #1: Tue Jul 20 17:01:49 HST 2004 [EMAIL 
PROTECTED]:/usr/obj/usr/src/sys/HPLAPTOP1  i386

Robert

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


Re: changing card in a reader (revisited)

2004-07-20 Thread hoe-waa



From: Dinesh Nair [EMAIL PROTECTED]
Date: Monday, July 19, 2004 11:39 pm

 
 On Mon, 19 Jul 2004 [EMAIL PROTECTED] wrote:
 
  I had tried camcontrol rescan 0:0:2 without success and I just tried
  camcontrol rescan all without success.
 
 on a particular Apacer multi-card reader, i needed to run camcontrol
 rescan on all devices off that one bus, (0:0:1, 0:0:2, 0:0:3 et al) to
 reset the reader when a new CF card was inserted. 'camcontrol 
 rescan all'
 didn't seem to do it then either. perhaps you could try this.
 
 Regards,   

Aloha Dinesh

I tried it but it doesn't help. Does this work for you?
Are you running 5.2.1?

Start with 8MB SM card in da2.
%su
Password:

hp# ls -l /dev/da*
crw-r-  1 rootoperator4,  20 Jul 19 06:19 /dev/da0
crw-r-  1 rootoperator4,  21 Jul 19 06:19 /dev/da1
crw-r-  1 rootoperator4,  22 Jul 19 06:19 /dev/da2
crw-rw  1 robert  robert  4,  25 Jul 19 06:19 /dev/da2s1
crw-r-  1 rootoperator4,  23 Jul 19 06:19 /dev/da3
crw-r-  1 rootoperator4,  24 Jul 19 06:19 /dev/da4
crw-rw  1 robert  robert  4,  26 Jul 19 06:19 /dev/da4s1


hp# mount_msdosfs /dev/da2s1 /mnt/olympus
hp# ls -l /mnt/olympus/dcim/100olymp
total 1352
-rwxr-xr-x  1 root  wheel  704002 Jan  1  2000 p1010001.jpg
-rwxr-xr-x  1 root  wheel  679720 Jan  1  2000 p1010002.jpg
hp# umount /mnt/olympus

remove 8MB SM card and insert 128MB card

hp# camcontrol rescan 0:0:0
Re-scan of 0:0:0 was successful
hp# camcontrol rescan 0:0:1
Re-scan of 0:0:1 was successful
hp# camcontrol rescan 0:0:2
Re-scan of 0:0:2 was successful
hp# camcontrol rescan 0:0:3
Re-scan of 0:0:3 was successful
hp# mount_msdosfs /dev/da2s1 /mnt/olympus
mount_msdosfs: /dev/da2s1: Invalid argument
hp#

For what it is worth, here are the most recent entries in /var/log/messages.
The same group of messages appear whenever I perform the mount command
whether I am mounting an 8MB or attempting a 128 MB card.

Jul 20 06:56:24 hp su: robert to root on /dev/ttyp0
Jul 20 06:57:29 hp kernel: (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0  0 0 
0 0 0 0
Jul 20 06:57:29 hp kernel: (da2:umass-sim0:0:0:2): CAM Status: SCSI Status Error
Jul 20 06:57:29 hp kernel: (da2:umass-sim0:0:0:2): SCSI Status: Check Condition
Jul 20 06:57:29 hp kernel: (da2:umass-sim0:0:0:2): UNIT ATTENTION asc:28,0
Jul 20 06:57:29 hp kernel: (da2:umass-sim0:0:0:2): Not ready to ready change, 
me dium may have changed
Jul 20 06:57:29 hp kernel: (da2:umass-sim0:0:0:2): Retrying Command (per Sense D ata)
Jul 20 06:59:16 hp kernel: (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0  0 0 
0 0 0 0
Jul 20 06:59:16 hp kernel: (da2:umass-sim0:0:0:2): CAM Status: SCSI Status Error
Jul 20 06:59:16 hp kernel: (da2:umass-sim0:0:0:2): SCSI Status: Check Condition
Jul 20 06:59:16 hp kernel: (da2:umass-sim0:0:0:2): UNIT ATTENTION asc:28,0
Jul 20 06:59:16 hp kernel: (da2:umass-sim0:0:0:2): Not ready to ready change, 
me dium may have changed
Jul 20 06:59:16 hp kernel: (da2:umass-sim0:0:0:2): Retrying Command (per Sense D ata)
Jul 20 07:01:17 hp kernel: (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0  0 0 
0 0 0 0
Jul 20 07:01:17 hp kernel: (da2:umass-sim0:0:0:2): CAM Status: SCSI Status Error
Jul 20 07:01:17 hp kernel: (da2:umass-sim0:0:0:2): SCSI Status: Check Condition
Jul 20 07:01:17 hp kernel: (da2:umass-sim0:0:0:2): UNIT ATTENTION asc:28,0
Jul 20 07:01:17 hp kernel: (da2:umass-sim0:0:0:2): Not ready to ready change, 
me dium may have changed
Jul 20 07:01:17 hp kernel: (da2:umass-sim0:0:0:2): Retrying Command (per Sense D ata)

Thnaks for your response and please let me know if there is any thing else
I can try.

Robert

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


Re: changing card in a reader (revisited)

2004-07-20 Thread hoe-waa



From: Dinesh Nair [EMAIL PROTECTED]
Date: Tuesday, July 20, 2004 7:44 am

 
 what does '/sbin/fdisk da2' say ?
 
 Regards,   


Aloha and Mahalo

I do get something different displayed with fdisk.

insert and mount 8MB card

hp# mount_msdosfs /dev/da2s1 /mnt/olympus
hp# /sbin/fdisk da2
*** Working on device /dev/da2 ***
parameters extracted from in-core disklabel are:
cylinders=7 heads=64 sectors/track=32 (2048 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=7 heads=64 sectors/track=32 (2048 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 1 (0x01),(Primary DOS with 12 bit FAT)
start 25, size 15975 (7 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 10;
end: cyl 249/ head 3/ sector 16
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED

hp# umount /mnt/olympus

change to 128MB card

hp# mount_msdosfs /dev/da2s1 /mnt/olympus
mount_msdosfs: /dev/da2s1: Invalid argument
hp# /sbin/fdisk da2
*** Working on device /dev/da2 ***
parameters extracted from in-core disklabel are:
cylinders=125 heads=64 sectors/track=32 (2048 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=125 heads=64 sectors/track=32 (2048 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 6 (0x06),(Primary 'big' DOS (= 32MB))
start 47, size 255953 (124 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 16;
end: cyl 499/ head 15/ sector 32
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED
hp#

Is it the Primary 'big that's messing me up?

Robert

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


Re: changing card in a reader (revisited)

2004-07-20 Thread hoe-waa


- Original Message -
From: [EMAIL PROTECTED]
Date: Tuesday, July 20, 2004 8:58 am
Subject: Re: changing card in a reader (revisited)

 
 
 
 From: Dinesh Nair [EMAIL PROTECTED]
 Date: Tuesday, July 20, 2004 7:44 am
 
  
  what does '/sbin/fdisk da2' say ?
  
  Regards,   
 
 
 Aloha and Mahalo
 
 I do get something different displayed with fdisk.
 
 insert and mount 8MB card
 
 hp# mount_msdosfs /dev/da2s1 /mnt/olympus
 hp# /sbin/fdisk da2
 *** Working on device /dev/da2 ***
 parameters extracted from in-core disklabel are:
 cylinders=7 heads=64 sectors/track=32 (2048 blks/cyl)
 
 parameters to be used for BIOS calculations are:
 cylinders=7 heads=64 sectors/track=32 (2048 blks/cyl)
 
 Media sector size is 512
 Warning: BIOS sector numbering starts with sector 1
 Information from DOS bootblock is:
 The data for partition 1 is:
 sysid 1 (0x01),(Primary DOS with 12 bit FAT)
start 25, size 15975 (7 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 10;
end: cyl 249/ head 3/ sector 16
 The data for partition 2 is:
 UNUSED
 The data for partition 3 is:
 UNUSED
 The data for partition 4 is:
 UNUSED
 
 hp# umount /mnt/olympus
 
 change to 128MB card
 
 hp# mount_msdosfs /dev/da2s1 /mnt/olympus
 mount_msdosfs: /dev/da2s1: Invalid argument
 hp# /sbin/fdisk da2
 *** Working on device /dev/da2 ***
 parameters extracted from in-core disklabel are:
 cylinders=125 heads=64 sectors/track=32 (2048 blks/cyl)
 
 parameters to be used for BIOS calculations are:
 cylinders=125 heads=64 sectors/track=32 (2048 blks/cyl)
 
 Media sector size is 512
 Warning: BIOS sector numbering starts with sector 1
 Information from DOS bootblock is:
 The data for partition 1 is:
 sysid 6 (0x06),(Primary 'big' DOS (= 32MB))
start 47, size 255953 (124 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 16;
end: cyl 499/ head 15/ sector 32
 The data for partition 2 is:
 UNUSED
 The data for partition 3 is:
 UNUSED
 The data for partition 4 is:
 UNUSED
 hp#
 
 Is it the Primary 'big that's messing me up?
 
 Robert
 
Forfeiting 6 karma points for responding to my own post.

Being curious, I unplugged and replugged the USB cable.
I then reran fdisk with the 128MB card mounted.

hp# ls -l /dev/da*
crw-r-  1 root  operator4,  27 Jul 19 06:19 /dev/da0
crw-r-  1 root  operator4,  28 Jul 19 06:19 /dev/da1
crw-r-  1 root  operator4,  29 Jul 19 06:19 /dev/da2
crw-r-  1 root  operator4,  30 Jul 19 06:19 /dev/da2s1
crw-r-  1 root  operator4,  31 Jul 19 06:19 /dev/da3
crw-r-  1 root  operator4,  24 Jul 19 06:19 /dev/da4
crw-rw  1 root  wheel   4,  26 Jul 19 06:19 /dev/da4s1
hp# mount_msdosfs /dev/da2s1 /mnt/olympus
hp# /sbin/fdisk da2
*** Working on device /dev/da2 ***
parameters extracted from in-core disklabel are:
cylinders=125 heads=64 sectors/track=32 (2048 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=125 heads=64 sectors/track=32 (2048 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 6 (0x06),(Primary 'big' DOS (= 32MB))
start 47, size 255953 (124 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 16;
end: cyl 499/ head 15/ sector 32
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED

It looks the same!

Robert

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


changing card in a reader (revisited)

2004-07-19 Thread hoe-waa
Aloha

I had previously started a thread with this problem and although I 
received several suggestions the problem was never solved.
http://lists.freebsd.org/pipermail/freebsd-questions/2004-June/050819.html

Below I have included more information. If I change an 8MB card for 
another 8MB card everything works as it should. If I try a different size
card it fails.

In addition, if I boot with no card in the slot, I cannot get a slice to
initiate in /dev. i.e. I will see /dev/da0 - /dev/da3. When I boot with
a card in the slot I see /dev/da2s1 as seen below. This problem has been
reported by others (found through google) but again there was no solution.
Is there a friend that I am unaware of?

I have tried various attempts with camcontrol without any good results. If 
I unplug and replug the USB cable both of the above problems are corrected.
I don't feel that is a viable solution. My wife has WXP on her computer and
it will update with the changing of a card. I really need a friend that will
rescan or update the USB connection.

Here are the related parts of dmesg.boot. da4 is a thumb drive and da1-3
are the 4 slots of my card reader. The SmartMedia card is in da2.

GEOM: create disk da0 dp=0xc2e44050
GEOM: create disk da1 dp=0xc2dacc50
GEOM: create disk da2 dp=0xc2e47450
GEOM: create disk da3 dp=0xc2e45850
GEOM: create disk da4 dp=0xc2e45450
da4 at umass-sim1 bus 1 target 0 lun 0
da4: Generic STORAGE DEVICE 1033 Removable Direct Access SCSI-0 device 
da4: 1.000MB/s transfers
da4: 250MB (512000 512 byte sectors: 64H 32S/T 250C)
da0 at umass-sim0 bus 0 target 0 lun 0
da0: USB2.0 CardReader CF RW 0814 Removable Direct Access SCSI-0 device 
da0: 1.000MB/s transfers
da0: Attempt to query device size failed: NOT READY, Medium not present
da1 at umass-sim0 bus 0 target 0 lun 1
da1: USB2.0 CardReader SD RW 0814 Removable Direct Access SCSI-0 device 
da1: 1.000MB/s transfers
da1: Attempt to query device size failed: NOT READY, Medium not present
da2 at umass-sim0 bus 0 target 0 lun 2
da2: USB2.0 CardReader SM RW 0814 Removable Direct Access SCSI-0 device 
da2: 1.000MB/s transfers
da2: 7MB (16000 512 byte sectors: 64H 32S/T 7C)
da3 at umass-sim0 bus 0 target 0 lun 3
da3: USB2.0 CardReader MS RW 0814 Removable Direct Access SCSI-0 device 
da3: 1.000MB/s transfers
da3: Attempt to query device size failed: NOT READY, Medium not present
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): NOT READY asc:3a,0
(da0:umass-sim0:0:0:0): Medium not present
(da0:umass-sim0:0:0:0): Unretryable error
Opened disk da0 - 6
(da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 
(da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
(da0:umass-sim0:0:0:0): SCSI Status: Check Condition
(da0:umass-sim0:0:0:0): NOT READY asc:3a,0
(da0:umass-sim0:0:0:0): Medium not present
(da0:umass-sim0:0:0:0): Unretryable error
Opened disk da0 - 6
(da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 
(da1:umass-sim0:0:0:1): CAM Status: SCSI Status Error
(da1:umass-sim0:0:0:1): SCSI Status: Check Condition
(da1:umass-sim0:0:0:1): NOT READY asc:3a,0
(da1:umass-sim0:0:0:1): Medium not present
(da1:umass-sim0:0:0:1): Unretryable error
Opened disk da1 - 6
(da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0 
(da1:umass-sim0:0:0:1): CAM Status: SCSI Status Error
(da1:umass-sim0:0:0:1): SCSI Status: Check Condition
(da1:umass-sim0:0:0:1): NOT READY asc:3a,0
(da1:umass-sim0:0:0:1): Medium not present
(da1:umass-sim0:0:0:1): Unretryable error
Opened disk da1 - 6
(da3:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 
(da3:umass-sim0:0:0:3): CAM Status: SCSI Status Error
(da3:umass-sim0:0:0:3): SCSI Status: Check Condition
(da3:umass-sim0:0:0:3): NOT READY asc:3a,0
(da3:umass-sim0:0:0:3): Medium not present
(da3:umass-sim0:0:0:3): Unretryable error
Opened disk da3 - 6
(da3:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0 
(da3:umass-sim0:0:0:3): CAM Status: SCSI Status Error
(da3:umass-sim0:0:0:3): SCSI Status: Check Condition
(da3:umass-sim0:0:0:3): NOT READY asc:3a,0
(da3:umass-sim0:0:0:3): Medium not present
(da3:umass-sim0:0:0:3): Unretryable error
Opened disk da3 - 6



%su
Password:
hp# ls -l /dev/da*
crw-r-  1 rootoperator4,  20 Jul 19 06:19 /dev/da0
crw-r-  1 rootoperator4,  21 Jul 19 06:19 /dev/da1
crw-r-  1 rootoperator4,  22 Jul 19 06:19 /dev/da2
crw-rw  1 robert  robert  4,  25 Jul 19 06:19 /dev/da2s1
crw-r-  1 rootoperator4,  23 Jul 19 06:19 /dev/da3
crw-r-  1 rootoperator4,  24 Jul 19 06:19 /dev/da4
crw-rw  1 robert  robert  4,  26 Jul 19 06:19 /dev/da4s1
hp#


hp# mount_msdosfs /dev/da2s1 /mnt/olympus

hp# ls -l /mnt/olympus/dcim/100olymp
total 680
-rwxr-xr-x  1 root  wheel  694158 Jul 12 18:27 p7120001.jpg
hp#
hp# umount /mnt/olympus

here I change the SM card with 

Re: changing card in a reader (revisited)

2004-07-19 Thread hoe-waa


From: Anish Mistry [EMAIL PROTECTED]
Date: Monday, July 19, 2004 2:29 pm

 
 On Monday 19 July 2004 05:10 pm, [EMAIL PROTECTED] wrote:
  Aloha
 
  I had previously started a thread with this problem and although I
  received several suggestions the problem was never solved.
  http://lists.freebsd.org/pipermail/freebsd-questions/2004-
 June/050819.html
  Below I have included more information. If I change an 8MB card for
  another 8MB card everything works as it should. If I try a 
 different size
  card it fails.
 
  In addition, if I boot with no card in the slot, I cannot get a 
 slice to
  initiate in /dev. i.e. I will see /dev/da0 - /dev/da3. When I 
 boot with
  a card in the slot I see /dev/da2s1 as seen below. This problem 
 has been
  reported by others (found through google) but again there was no 
 solution. Is there a friend that I am unaware of?
 
  I have tried various attempts with camcontrol without any good 
 results. If
  I unplug and replug the USB cable both of the above problems are 
 corrected. I don't feel that is a viable solution. My wife has 
 WXP on her computer and
  it will update with the changing of a card. I really need a 
 friend that
  will rescan or update the USB connection.
 
  Here are the related parts of dmesg.boot. da4 is a thumb drive 
 and da1-3
  are the 4 slots of my card reader. The SmartMedia card is in da2.
 
  GEOM: create disk da0 dp=0xc2e44050
  GEOM: create disk da1 dp=0xc2dacc50
  GEOM: create disk da2 dp=0xc2e47450
  GEOM: create disk da3 dp=0xc2e45850
  GEOM: create disk da4 dp=0xc2e45450
  da4 at umass-sim1 bus 1 target 0 lun 0
  da4: Generic STORAGE DEVICE 1033 Removable Direct Access SCSI-
 0 device
  da4: 1.000MB/s transfers
  da4: 250MB (512000 512 byte sectors: 64H 32S/T 250C)
  da0 at umass-sim0 bus 0 target 0 lun 0
  da0: USB2.0 CardReader CF RW 0814 Removable Direct Access SCSI-
 0 device
  da0: 1.000MB/s transfers
  da0: Attempt to query device size failed: NOT READY, Medium not 
 present da1 at umass-sim0 bus 0 target 0 lun 1
  da1: USB2.0 CardReader SD RW 0814 Removable Direct Access SCSI-
 0 device
  da1: 1.000MB/s transfers
  da1: Attempt to query device size failed: NOT READY, Medium not 
 present da2 at umass-sim0 bus 0 target 0 lun 2
  da2: USB2.0 CardReader SM RW 0814 Removable Direct Access SCSI-
 0 device
  da2: 1.000MB/s transfers
  da2: 7MB (16000 512 byte sectors: 64H 32S/T 7C)
  da3 at umass-sim0 bus 0 target 0 lun 3
  da3: USB2.0 CardReader MS RW 0814 Removable Direct Access SCSI-
 0 device
  da3: 1.000MB/s transfers
  da3: Attempt to query device size failed: NOT READY, Medium not 
 present (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 
 0 0 0 0
  (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
  (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
  (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
  (da0:umass-sim0:0:0:0): Medium not present
  (da0:umass-sim0:0:0:0): Unretryable error
  Opened disk da0 - 6
  (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0
  (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error
  (da0:umass-sim0:0:0:0): SCSI Status: Check Condition
  (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
  (da0:umass-sim0:0:0:0): Medium not present
  (da0:umass-sim0:0:0:0): Unretryable error
  Opened disk da0 - 6
  (da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0
  (da1:umass-sim0:0:0:1): CAM Status: SCSI Status Error
  (da1:umass-sim0:0:0:1): SCSI Status: Check Condition
  (da1:umass-sim0:0:0:1): NOT READY asc:3a,0
  (da1:umass-sim0:0:0:1): Medium not present
  (da1:umass-sim0:0:0:1): Unretryable error
  Opened disk da1 - 6
  (da1:umass-sim0:0:0:1): READ CAPACITY. CDB: 25 20 0 0 0 0 0 0 0 0
  (da1:umass-sim0:0:0:1): CAM Status: SCSI Status Error
  (da1:umass-sim0:0:0:1): SCSI Status: Check Condition
  (da1:umass-sim0:0:0:1): NOT READY asc:3a,0
  (da1:umass-sim0:0:0:1): Medium not present
  (da1:umass-sim0:0:0:1): Unretryable error
  Opened disk da1 - 6
  (da3:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0
  (da3:umass-sim0:0:0:3): CAM Status: SCSI Status Error
  (da3:umass-sim0:0:0:3): SCSI Status: Check Condition
  (da3:umass-sim0:0:0:3): NOT READY asc:3a,0
  (da3:umass-sim0:0:0:3): Medium not present
  (da3:umass-sim0:0:0:3): Unretryable error
  Opened disk da3 - 6
  (da3:umass-sim0:0:0:3): READ CAPACITY. CDB: 25 60 0 0 0 0 0 0 0 0
  (da3:umass-sim0:0:0:3): CAM Status: SCSI Status Error
  (da3:umass-sim0:0:0:3): SCSI Status: Check Condition
  (da3:umass-sim0:0:0:3): NOT READY asc:3a,0
  (da3:umass-sim0:0:0:3): Medium not present
  (da3:umass-sim0:0:0:3): Unretryable error
  Opened disk da3 - 6
 
 
 
  %su
  Password:
  hp# ls -l /dev/da*
  crw-r-  1 rootoperator4,  20 Jul 19 06:19 /dev/da0
  crw-r-  1 rootoperator4,  21 Jul 19 06:19 /dev/da1
  crw-r-  1 rootoperator4,  22 Jul 19 06:19 /dev/da2
  crw-rw  1 robert  robert  4,  25 Jul 19 06:19 /dev/da2s1
  crw-r-  1 rootoperator4,  23 Jul 19 06:19 /dev/da3
 

Re: Card reader problems (was: changing card in a reader (revisited))

2004-07-19 Thread hoe-waa



From: Martin [EMAIL PROTECTED]
Date: Monday, July 19, 2004 12:10 pm


 
 Hi,
 
 Sorry to disturb, but do you get panics with your card reader?
 I see someone posting about such device for the first time here
 (except me). What kernel are you using?
 
 I have a 4-slot reader/writer too and each time I plug it in,
 I get a panic instantly on CURRENT. I've always thought that it
 is because of four devices attaching at once, but it seems to
 work fine for you.
 
 Martin
 
Aloha Martin

I do not get any panics. I was running current but then
I went back to 5.2.1. I had current running to try
ndis but I am not where I can use that card so I
went back to see if there was any difference with
the card reader. Alas, they work the same way.

%uname -a
FreeBSD hp.hawaii.rr.com 5.2.1-RELEASE-p9 FreeBSD 
5.2.1-RELEASE-p9 #0: Thu Jul 15 10:14:33 HST 2004  
   [EMAIL PROTECTED]:/usr/obj/usr/src/sys/HPLAPTOP1  i386
%

Good luck
Robert

 

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


Re: changing cards in a reader

2004-06-28 Thread hoe-waa
Scott Mitchell wrote

Hi Robert,

Weird - that's what works for me, so I don't know how much more help I can
offer, but here are a few suggestions that might help us figure out what's
going on...

 Boot with 128MB card installed.

 hp# ls -l /dev/da*
 crw-r-  1 root  operator4,  20 Jun 26 18:50 /dev/da0
 crw-r-  1 root  operator4,  21 Jun 26 18:50 /dev/da1
 crw-r-  1 root  operator4,  22 Jun 26 18:50 /dev/da2
 crw-r-  1 root  operator4,  24 Jun 26 18:50 /dev/da2s1
 crw-r-  1 root  operator4,  23 Jun 26 18:50 /dev/da3

Ah... you're running FreeBSD 5 - it was pretty late when I wrote that first
reply, so I didn't notice that immediately.  Unlike FreeBSD 4, where stuff
in /dev/ had to be created manually, FreeBSD 5 uses devfs to create the
device nodes as needed, when devices come and go.  I haven't actually used
my card reader on 5 yet, so I could be missing something obvious here...

 Remove 128MB card and insert 8MB card

 hp# camcontrol rescan 0:0:2
 Re-scan of 0:0:2 was successful

What does 'fdisk da2' give you at this point?
Do you get anything in /var/log/messages when you insert the new card?

It might be worth doing a 'camcontrol start' after the rescan, just in
case, but I don't really think that will make any difference.

Since you're running FreeBSD 5, it might be worth re-porting your question
to the freebsd-current mailing list, to see if anyone there can shed some
light on this.

Sorry I can't be more help,

Scott


Aloha and mahalo Scott
I had tried the camcontrol start before but I tried again without any good stuff.
Fdisk seems to show the correct readings but I could use some help interpreting
the output of /var/log/messages.
 
I am traveling now so I am using my laptop which is running current. When I return
to Kona (7-6) I will try on one of my desktops that are running 5.2.1

Thanks again for helping.
Robert

hp# ls -l /mnt/olympus
total 16
drwxr-xr-x  1 root  wheel  8192 Jun 26 14:24 dcim
drwxr-xr-x  1 root  wheel  8192 Jan  1  1980 imolym
hp# umount /mnt/olympus
hp# camcontrol eject 0:0:2
Unit stopped successfully, Media ejected

Remove 8MB card and insert 128MB card

hp# camcontrol rescan 0:0:2
Re-scan of 0:0:2 was successful
hp# fdisk da2
*** Working on device /dev/da2 ***
parameters extracted from in-core disklabel are:
cylinders=125 heads=64 sectors/track=32 (2048 blks/cyl)

parameters to be used for BIOS calculations are:
cylinders=125 heads=64 sectors/track=32 (2048 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 6 (0x06),(Primary 'big' DOS (= 32MB))
start 47, size 255953 (124 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 16;
end: cyl 499/ head 15/ sector 32
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED


Jun 27 09:01:13 hp su: robert to root on /dev/ttyp0
Jun 27 09:03:01 hp kernel: (da2:umass-sim0:0:0:2): READ CAPACITY. CDB: 25 40 0 0 0 0 0 
0 0 0
Jun 27 09:03:01 hp kernel: (da2:umass-sim0:0:0:2): CAM Status: SCSI Status Error
Jun 27 09:03:01 hp kernel: (da2:umass-sim0:0:0:2): SCSI Status: Check Condition
Jun 27 09:03:01 hp kernel: (da2:umass-sim0:0:0:2): UNIT ATTENTION asc:28,0
Jun 27 09:03:01 hp kernel: (da2:umass-sim0:0:0:2): Not ready to ready change, medium 
may have changed
Jun 27 09:03:01 hp kernel: (da2:umass-sim0:0:0:2): Retrying Command (per Sense Data)
hp#

hp# camcontrol start 0:0:2
Unit started successfully
hp# mount_msdosfs /dev/da2s1 /mnt/olympus
mount_msdosfs: /dev/da2s1: Invalid argument
hp#


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


changing cards in a reader

2004-06-26 Thread hoe-waa
Aloha

Hopefully this is a simple question. FreeBSD does not support my 
Olympus C-3000 Zoom camera so I bought a card reader (usb). It has
4 slots and when I boot or just plug it in I get 4 drives 
(da0, da1, da2,  da3). If I have a SmartMedia card installed I 
also see da2s1.

da2s1 mounts fine and I am able to see and use all of the photo files.

I have additional SM cards and would like to change the installed card at 
will. If I do a umount and replace the card and try to mount again I
get an error  mount_msdosfs: /dev/da2s1: Invalid argument. I should
say that the cards are different sizes. In order to mount another card
I have to unplug the usb cable and re-plug it in with the new card in 
the slot.

I have read man camcontrol and do not see an option I can use.

Is there a way to do this without unplugging and re-plugging the cable?

hp# uname -a
FreeBSD hp.hawaii.rr.com 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Thu Jun 10 12:39:40 
HST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386

Thank You

Robert


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


Re: changing cards in a reader

2004-06-26 Thread hoe-waa
On Saturday, June 26, 2004 12:56 pm Scott Mitchell [EMAIL PROTECTED] 
responded thusly

 On Sat, Jun 26, 2004 at 11:39:25AM -1000, [EMAIL PROTECTED] wrote:
  Aloha
  
  Hopefully this is a simple question. FreeBSD does not support my 
  Olympus C-3000 Zoom camera so I bought a card reader (usb). It has
  4 slots and when I boot or just plug it in I get 4 drives 
  (da0, da1, da2,  da3). If I have a SmartMedia card installed I 
  also see da2s1.
  
  da2s1 mounts fine and I am able to see and use all of the photo 
 files. 
  I have additional SM cards and would like to change the installed 
 card at 
  will. If I do a umount and replace the card and try to mount 
 again I
  get an error  mount_msdosfs: /dev/da2s1: Invalid argument. I 
 should say that the cards are different sizes. In order to mount 
 another card
  I have to unplug the usb cable and re-plug it in with the new 
 card in 
  the slot.
  
  I have read man camcontrol and do not see an option I can use.
  
  Is there a way to do this without unplugging and re-plugging the 
 cable?
 Try this (as root):
 
 # camcontrol devlist
 
 to find out which CAM device da2 belongs to.  On this machine I get:
 
 337 COMB at scbus1 target 0 lun 0 
 (pass0,da2)DMI MultiFlash 3.00  at scbus2 target 0 
 lun 0 (pass1,da4)
 DMI MultiFlash 3.00  at scbus2 target 0 lun 1 
 (da5,pass2)DMI MultiFlash 3.00  at scbus2 target 0 
 lun 2 (da6,pass3)
 DMI MultiFlash 3.00  at scbus2 target 0 lun 3 
 (da7,pass4)
 My SmartMedia slot happens to be da5, which is device 2:0:1.  After
 unmounting the card, you should be able to:
 
 # camcontrol eject 2:0:1
 
 using the appropriate device number for your system, of course.  
 Then swap
 cards and do:
 
 # camcontrol rescan 2:0:1
 
 which should generate some lines in /var/log/messages telling you 
 about the
 size of the new card.
 
 You might want to look into setting up the automounter to do the 
 rescan and
 eject automatically when cards are mounted and unmounted, 
 respectively.
 Cheers,
 
   Scott
 
Aloha Scott and thanks for staying awake and responding.

I thought I had tried all of that camcontrol stuff
before I posted but I am getting old so I tried what
you suggested. Alas, it did not seem to help. Here is
the output of the attempt:

Boot with 128MB card installed.

hp# ls -l /dev/da*
crw-r-  1 root  operator4,  20 Jun 26 18:50 /dev/da0
crw-r-  1 root  operator4,  21 Jun 26 18:50 /dev/da1
crw-r-  1 root  operator4,  22 Jun 26 18:50 /dev/da2
crw-r-  1 root  operator4,  24 Jun 26 18:50 /dev/da2s1
crw-r-  1 root  operator4,  23 Jun 26 18:50 /dev/da3

hp# mount_msdosfs /dev/da2s1 /mnt/olympus
hp# ls -l /mnt/olympus
total 16
drwxr-xr-x  1 root  wheel  16384 Jan 13  2003 dcim

hp# camcontrol devlist
USB2.0 CardReader CF RW 0814 at scbus0 target 0 lun 0 (da0,pass0)
USB2.0 CardReader SD RW 0814 at scbus0 target 0 lun 1 (da1,pass1)
USB2.0 CardReader SM RW 0814 at scbus0 target 0 lun 2 (da2,pass2)
USB2.0 CardReader MS RW 0814 at scbus0 target 0 lun 3 (da3,pass3)


hp# umount /mnt/olympus
hp# camcontrol eject 0:0:2
Unit stopped successfully, Media ejected

Remove 128MB card and insert 8MB card

hp# camcontrol rescan 0:0:2
Re-scan of 0:0:2 was successful
hp# mount_msdosfs /dev/da2s1 /mnt/olympus
mount_msdosfs: /dev/da2s1: Invalid argument

Unplug and replug usb cable and then

hp# ls -l /mnt/olympus
total 16
drwxr-xr-x  1 root  wheel  8192 Jun 26 14:24 dcim
drwxr-xr-x  1 root  wheel  8192 Jan  1  1980 imolym

Any other suggestions. (I hope :o))

Robert



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


Re: FreeBSD weakness

2004-06-21 Thread hoe-waa

On 2004-06-21 01:42, Lloyd Hayes [EMAIL PROTECTED] wrote:
 I'll repeat this so there is no misunderstanding. The people here have
 been great in their response to help! But there is also no getting
 around the fact that I am much older (54) and less able to absorb new
 ideas as fast

ALoha Lloyd

Age and cunning will beat youth and speed most of the time. (IIRC) ;o)

begin horn blowing
I am 57 and installed my first linux distro about a year ago. Sice then I have
tried 5 different linux distros and was unsatisfied with each for various reasons.
Mostly because I didn't have total control over what is being installed from the iso
or from the packages. Gentoo does better than most by emulating FBSD.

In January I installed FreeBSD for the first time. Actually, I installed it about a 
dozen
times for the first time. I read the handbook and lurked on forums and subscribed to
the mailing lists (-newbies  -questions). 

I kept acquiring old systems and improving them. I now have FBSD installed on 4 
frankenputers
and my laptop. I still have so much to learn and to do. I have a lot planned and 
will try
to do it myself with the aid of books/howtos and lurking. I also know that when I am
stuck, I can send to -questions and get quality (and quantity) answers.
end horn blowing

I agree with you. The people on this list and their responses are fantastic! I for one 
hope you stick with it. Keep your mind active and the ability to absorb will not 
diminish.

Robert

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


Re: FreeBSD Commands

2004-06-16 Thread hoe-waa
Aloha
I am always happy to help. I am a real newbie to FBSD
I have been using it for about 6 months. In the early 
80's I used cli on Unix V when I worked for the Death
Star company. I was then forced to migrate to Dos and
then to Windows because all the clients needed any
correspondence or proposals in word or excel.
Now that I am retired (the only way to live) I have
played around with linux and have now migrated to FBSD.

I have learned quite a bit in 6 months by lurking and
installing and re-installing and re-installing on 4 
different systems that I have pieced together. 
Read, study, take notes, lurk and most of all try it out. there is no substitute for 
doing. 
There is so much to learn that this hobby is getting 
in the way of my beach time.

Don't be afraid to ask questions and always provide
as much info as possible. Better to be verbose rather
than brief.

With that said, be sure to cc the list when answering
questions or giving info. There are a lot of us lurking out
there and are waiting for the answer.

When you use the linux page, make sure you check the
options against the man pages on your system. There are
differrences and they will bite!

Have fun
Robert

- Original Message -
From: Lloyd Hayes [EMAIL PROTECTED]
Date: Tuesday, June 15, 2004 5:04 pm
Subject: Re: FreeBSD Commands

 Thanks for the link and the Welcome. In looking at the website, it 
 appears to be what the doctor ordered.
 
 For the record, I have been looking at the UNIX type software and 
 operating system for some time now. Obviously not at the details of 
 the 
 line commands and setup, but at the software that it runs, and it's 
 stability related to older equipment. This older Gateway that I am 
 installing FreeBSD on is a good example. I think that I bought it 
 around 
 February 1998. I special ordered it at the time from Gateway. It 
 serves 
 as my backup computer now, and recently served as my primary 
 computer 
 while my main laptop was in the shop. There is nothing wrong with 
 the 
 old Gateway and it works fine. I'm an owner/operator truck driver. 
 The 
 entire trucking industry revolves around computers and has for many 
 years. Putting this a different way, without a computer I would be 
 out 
 of business. I get my loads over the Internet. My logbook is a 
 computer 
 program. I scan and email paperwork into the office, and receive 
 paperwork the same way.
 
 FreeBSD has been around longer then any of the Linux distributions, 
 although I have considered some of them. My brother has a MAC that 
 he 
 thinks is great. MacIntosh runs a version of FreeBSD.  Plus I 
 figured 
 that there was more support for FreeBSD then any other operating 
 system 
 outside of Windows. Also in very limited ways, it appears that 
 FreeBSD 
 is ahead of Linux in the development curve. Ways that keep older 
 equipment in use. (Simply buying new equipment every few months to 
 keep 
 up with Mr. Gates is for the birds)
 
 Thanks for the Welcome.
 
 (I'll work on everyone's suggestions later in the week and see if I 
 can 
 figure things out. It appears that my xf86config file has a bug in 
 it.)
 Lloyd Hayes
 
 Email: [EMAIL PROTECTED]
 URL: http://TalkingStaff.bravehost.com 
 E-FAX Number: (208) 248-6590
 Web Journal: http://lloyd_hayes.bravejournal.com/
 
 
 
 [EMAIL PROTECTED] wrote:
 
 Since Giorgos crossed the line to linux :)
 here is a site that has all of the man pages
 at your fingertips. For someone new to *nix,
 knowing what to ask is harder than asking.
 
 http://jamesthornton.com/linux/man/
 
 Welcome to FreeBSD. It is the best.
 
 Robert
 


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


Re: FreeBSD Commands

2004-06-15 Thread hoe-waa
Since Giorgos crossed the line to linux :)
here is a site that has all of the man pages
at your fingertips. For someone new to *nix,
knowing what to ask is harder than asking.

http://jamesthornton.com/linux/man/

Welcome to FreeBSD. It is the best.

Robert

On Tuesday, June 15, 2004 10:10 am, Giorgos Keramidas broke it open 


 On 2004-06-15 12:40, Lloyd Hayes [EMAIL PROTECTED] wrote:
  I have the FreeBSD Handbook on a computer hard drive. There isn't 
 any mention of the line commands that FreeBSD uses or recognizes 
 in the
  handbook. Where do I find these?
 
 Hi Lloyd,
 
 Others have already mentioned the Basics section of the Handbook.
 I just wanted to add two more references that might be handy to get
 you started:
 
 1. Anderson, Annelise.  For People New to Both FreeBSD and 
 UNIX(TM).http://www.FreeBSD.org/doc/en_US.ISO8859-
 1/articles/new-users/
 
 2. Gonzato, Guido.  From DOS/Windows to Linux HOWTO.
http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-
 formats/html_single/DOS-Win-to-Linux-HOWTO.html
 
 It might intrigue some and seem curious to others that I---a long time
 FreeBSD user and advocate---would point to a Linux HOWTO.  The 
 truth is
 that most of the tips that apply for getting people acquainted with
 Linux are also good advice for using *any* UNIX system.
 
 Welcome to FreeBSD then,
 
 - Giorgos
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-
 [EMAIL PROTECTED]Aloha



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


Re: Wireless Microsoft USB G adapter drivers

2004-06-03 Thread hoe-waa
For what it's worth, I check with Project Evil and 
found this bad news. Looks like a AMF-YOYO

What doesn't Project Evil do:

- Provide support for USB network devices (this would require
  emulating portions of USBD.SYS and portitions of the Windows
  I/O model outside of the NDIS API).
- Support Winows modem drivers (this would mean duplicating
  big parts of ntoskrnl.exe).

Robert


From: Kevin Coles [EMAIL PROTECTED]

Subject: Wireless Microsoft USB G adapter drivers

 I am using Freebsd 5.2 and trying to use a Microsoft wireless G 
 usb 
 network adapter. I have searched the web and asked some friends 
 and I 
 cannot find drivers for this hardware. If anyone knows of a 
 solution, 
 please reply. It would be really helpful.
 
 Thanks for your time,
 
 Kevin
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-
 [EMAIL PROTECTED]

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


Re: Don't know what else to do with DHCP...help??

2004-05-31 Thread hoe-waa
Aloha
This sounds a whole lot like my DHCP problem. It was being 
discussed on this list earlier last week. I have attached my thread for your perusal.

I have the same ethernet card as you. There is a 
workaround in the attachment that I am using (I also
created a script to do it) but if someone comes up 
with a real fix it would be muck better.

Read through my attachment and see if you think we 
have the same problem.

Robert

- Original Message -
From: Don [EMAIL PROTECTED]
Date: Monday, May 31, 2004 1:56 am
Subject: Re: Don't know what else to do with DHCP...help??

 
 --- Rob [EMAIL PROTECTED] wrote:
  What is the last entry in /var/db/dhclient.leases ?
  If there's something, does that make sense ?
  
  Anything dhclient related in /var/log/messages ?
  
  And how about running dhclient manually in the
  foreground ?
  As root, kill the running dhclient pid first, and
  then start:
  
  # dhclient -d rl0
  
  where you should replace rl0 by your own network
  card.
  Does that tell you something useful?
  
  Rob.
 
 There was nothing in the /var/db/dhclient.leases and
 the only relevant thing I found in the
 /var/log/messages was this
 
 May 31 05:02:10  kernel: skc0: 3Com 3C940 Gigabit
 Ethernet port 0xd800-0xd8ff mem 0xe580-0xe5803fff
 irq 18 at device 9.0 on pci0
 May 31 05:02:10  kernel: skc0: 3Com Gigabit LOM
 (3C940)
 May 31 05:02:10  kernel: sk0: Marvell Semiconductor,
 Inc. Yukon on skc0
 May 31 05:02:10  kernel: sk0: Ethernet address:
 00:0e:a6:46:f4:d9
 May 31 05:02:10  kernel: e1000phy0: Marvell 88E1000
 Gigabit PHY on miibus0
 May 31 05:02:10  kernel: e1000phy0:  10baseT,
 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX-FDX,
 auto
 
 and
 
 May 31 05:02:34  dhclient: Can't bind to dhcp address:
 Address already in use
 May 31 05:02:34  dhclient: Please make sure there is
 no other dhcp server
 May 31 05:02:34  dhclient: running and that there's no
 entry for dhcp or
 May 31 05:02:34  dhclient: bootp in /etc/inetd.conf.  
 Also make sure you
 May 31 05:02:34  dhclient: are not running HP JetAdmin
 software, which
 May 31 05:02:34  dhclient: includes a bootp server.
 
 so it looks like the kernel is definitely identifying
 my NIC correctly (I guessed this seeing how I was able
 to install over FTP) but for whatever reason the
 dchlient is no longer working
 
 I killed the dhclient pid and reran it...both as just
 dhclient and dhclinet -d sk0 both times the
 computer would just sit there with nothing
 happening...no messages no nothing (I let them sit
 there for 10-15 minutes before I killed it)
 
 Don
 
 
   
   
 __
 Do you Yahoo!?
 Friends.  Fun.  Try the all-new Yahoo! Messenger.
 http://messenger.yahoo.com/ 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-
 [EMAIL PROTECTED]


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


Re: Don't know what else to do with DHCP...help??

2004-05-31 Thread hoe-waa
Aloha Don
I am very happy I was able to help. 

One question for you before I answer yours. I still 
have to kill dhclient and netstart after a reboot.

Did you imply that after wiping out the hostname in 
rc.conf you can reboot and your dhcp is up?

Now for your question. I have not had any problems starting x before or after. I was 
always redoing the 
/stand/sysinstall to get the dhcp up and then startx 
so that I had a network. Have you checked your /etc/hosts for the correct hostname? 
When I did not 
have that set properly, I had x complaining, but not just
a grey screen.

Good Luck
Robert

- Original Message -
From: Don [EMAIL PROTECTED]
Date: Monday, May 31, 2004 11:52 am
Subject: Re: Don't know what else to do with DHCP...help??

 [EMAIL PROTECTED]
 --- [EMAIL PROTECTED] wrote:
  Aloha
  This sounds a whole lot like my DHCP problem. It was
  being 
  discussed on this list earlier last week. I have
  attached my thread for your perusal.
  
  I have the same ethernet card as you. There is a 
  workaround in the attachment that I am using (I also
  created a script to do it) but if someone comes up 
  with a real fix it would be muck better.
  
  Read through my attachment and see if you think we 
  have the same problem.
  
  Robert
  
 Thanks for the helpI killed any open dhclients and
 then did the netstartit still wasn't working until
 I took a peek at my rc.conf and deleted the hostname
 line and made sure ifconfig_sk0=DHCP and the appends
 were deleted...I then rebooted and viola!!! it
 works
 
 HOWEVER lol I now can't seem to get into XIt
 worked before I got my NIC working correctly and now
 when I startx it gets to the dark grey sceen where the
 pointer looks like an X and sits there. I'll play
 around with it some when I get back from my folks
 house but did you have that problem after you got your
 NIC working? 
 
 Thanks again for ppinting me to your earlier
 conversation. It was a tremendous help
 
 Don
 
 
   
   
 __
 Do you Yahoo!?
 Friends.  Fun.  Try the all-new Yahoo! Messenger.
 http://messenger.yahoo.com/ 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-
 [EMAIL PROTECTED]

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


Re: Don't know what else to do with DHCP...help??

2004-05-31 Thread hoe-waa
I think I'll leave mine as is until I or someone 
(hint, hint) comes up with the real fix. I don't 
reboot this machine very often and my script file 
seems to work fine.

If you are interested, here it is

$ cat /root/scripts/start-sk0.sh
#! /bin/sh
killall -9 dhclient
sh /etc/netstart
ifconfig -a

If I ever have to reboot, I log in as root and execute 
this script and the network comes up fine.  I then 
exit and log in as my normal user and startx. It 
was never more than an annoyance to me, so I can 
live like this.

Robert


 Yes...what I did was completely delete the hostname
 line from my /etc/rc.conf and had my
 inconfig_sk0=DHCP
 
 though this does seem somewhat problematic...every now
 and then I will boot up and it won't work...then I
 just reboot and all of a sudden it works *shrug*
 
 I fogured out what was wrong with starting X and you
 will probably have the same problem when you delete
 your hostname line from your rc.conf
 
 I googled it and found that a way to fix this problem
 isto simply delete the old .Xauthority fileI did
 that and now have my network and X back = D there
 may be (and probably is) a better way to accomplish
 this but this was just one way I found to get it to
 work...if someone has a better suggestion on how to do
 this I would be more than happy to hear about it = )
 
 Thanks for all your help and good luck with getting
 your network to work at boot = )
 
 Don
 --- [EMAIL PROTECTED] wrote:
  Aloha Don
  I am very happy I was able to help. 
  
  One question for you before I answer yours. I still 
  have to kill dhclient and netstart after a reboot.
  
  Did you imply that after wiping out the hostname in 
  rc.conf you can reboot and your dhcp is up?
  
  Now for your question. I have not had any problems
  starting x before or after. I was always redoing the
  
  /stand/sysinstall to get the dhcp up and then startx
  
  so that I had a network. Have you checked your
  /etc/hosts for the correct hostname? When I did not 
  have that set properly, I had x complaining, but not
  just
  a grey screen.
  
  Good Luck
  Robert
  
  
 
 
   
   
 __
 Do you Yahoo!?
 Friends.  Fun.  Try the all-new Yahoo! Messenger.
 http://messenger.yahoo.com/ 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-
 [EMAIL PROTECTED]

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


Re: RE: ethernet card not coming up on reboot

2004-05-26 Thread hoe-waa
Aloha Eric and Luke

I am aware that sysinstall will append to rc.conf.
I went ahead and deleted all of the appends and rebooted.
The ethernet did not come up on reboot. I had to use
sysinstall to get an ip. And yes, it did append to 
rc.conf again.

I will look into setting a static ip but I would like
to know why this is happening. I have 3 other boxes
that have FreeBSD on them and they don't have this problem.

Robert

- Original Message -
From: Eric Crist [EMAIL PROTECTED]
Date: Tuesday, May 25, 2004 7:30 pm
Subject: RE: ethernet card not coming up on reboot

 I have also noticed this issue, but if I have only once instance of 
 theentry in rc.conf, everything works fine.  Why not statically 
 define the
 IP, though?  That would be the best situation, IMHO.
 
 HTH
 
 Eric F Crist
 President
 AdTech Integrated Systems, Inc
 (612) 998-3588
 
 
 
 -Original Message-
 From: [EMAIL PROTECTED]
 [EMAIL PROTECTED] On Behalf Of Luke Kearney
 Sent: Tuesday, May 25, 2004 11:42 PM
 To: [EMAIL PROTECTED]
 Cc: [EMAIL PROTECTED]
 Subject: Re: ethernet card not coming up on reboot
 
 
 
 On Tue, 25 May 2004 17:58:04 -1000
 [EMAIL PROTECTED] spake thus:
 
  Aloha
 
  I have a little annoyance on one of my boxes. The box has an Asus
  P4P800 mobo with a 2.6GHz P4 and 1GB of DDR-400 Ram. I have FreeBSD
  5.2-RC1 loaded on a 120Gig SATA Hard disk. My ouput of uname -a:
 
  p4# uname -a
  FreeBSD p4.hawaii.rr.com 5.2-RC1 FreeBSD 5.2-RC1 #0: Sun Dec  7
 22:15:14
  GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
 i386
 
 
  The mobo has an onboard 3COM 3C940 Gbit LAN controller. This device
  is recognised during boot as sk0 and uses the SysKonnectPCI driver.
 
  The problem is that after a reboot a DHCP address is not assigned to
  sk0. Here is ifconfig -a after a reboot.
 
  p4# ifconfig -a
  sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
  inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1
  ether 00:0c:6e:91:de:a6
  media: Ethernet autoselect (100baseTX
 full-duplex,flag0,flag1)
  status: active
  plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500
  lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
  inet 127.0.0.1 netmask 0xff00
  inet6 ::1 prefixlen 128
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
 
  Here is the output of resolv.conf and rc.conf
 
  p4# cat /etc/resolv.conf
  search hawaii.rr.com
  nameserver 24.25.227.66
  nameserver 24.25.227.33
  nameserver 24.25.227.64
 
  p4# cat /etc/rc.conf
 
  # -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004 #
  Created: Thu May 20 10:05:35 2004 # Enable network daemons for user
  convenience. # Please make all changes to this file, not to
  /etc/defaults/rc.conf. # This file now contains just the overrides
  from /etc/defaults/rc.conf. hostname=p4.hawaii.rr.com
  ifconfig_sk0=DHCP
  linux_enable=YES
  nfs_client_enable=YES
  sshd_enable=YES
  usbd_enable=YES
  # This file now contains just the overrides from
 /etc/defaults/rc.conf.
  # Please make all changes to this file, not to 
 /etc/defaults/rc.conf.
  # Enable network daemons for user convenience.
  # Created: Thu May 20 20:27:06 2004
  # -- sysinstall generated deltas -- # Thu May 20 20:27:06 2004
  ifconfig_sk0=DHCP hostname=p4.hawaii.rr.com
  # This file now contains just the overrides from
 /etc/defaults/rc.conf.
  # Please make all changes to this file, not to 
 /etc/defaults/rc.conf.
  # Enable network daemons for user convenience.
 
  Notice that there is a second entry in rc.conf relating to sk0.
 
  If I enter /stand/sysinstall and choose configure then networking 
 and then
  interfaces and then chooses DHCP, the fields are all populated with
 the
  correct information. I can then exit back to the # and when I then
  look at ifconfig -a I get some good stuff!
 
  p4# ifconfig -a
  sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
  inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1
  inet 192.168.1.103 netmask 0xff00 broadcast 
 192.168.1.255 ether 00:0c:6e:91:de:a6
  media: Ethernet autoselect (100baseTX
 full-duplex,flag0,flag1)
  status: active
  plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500
  lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
  inet 127.0.0.1 netmask 0xff00
  inet6 ::1 prefixlen 128
  inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3
 
  Notice I now have an inet line populated with an IP address.
 
  If I now look at rc.conf I get this
 
  p4# cat /etc/rc.conf
 
  # -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004 #
  Created: Thu May 20 10:05:35 2004 # Enable network daemons for user
  convenience. # Please make all changes to this file, not to
  /etc/defaults/rc.conf. # This file now contains just the overrides
  from /etc/defaults/rc.conf. hostname=p4.hawaii.rr.com
  ifconfig_sk0=DHCP
  linux_enable=YES
  nfs_client_enable=YES
  

Re: ethernet card not coming up on reboot

2004-05-26 Thread hoe-waa

Subject: Re: ethernet card not coming up on reboot

 
 On Tue, 25 May 2004 20:00:12 -1000
 [EMAIL PROTECTED] spake thus:
 
  Aloha Eric and Luke
  
  I am aware that sysinstall will append to rc.conf.
  I went ahead and deleted all of the appends and rebooted.
  The ethernet did not come up on reboot. I had to use
  sysinstall to get an ip. And yes, it did append to 
  rc.conf again.
  
  I will look into setting a static ip but I would like
  to know why this is happening. I have 3 other boxes
  that have FreeBSD on them and they don't have this problem.
  
  Robert
  
  - Original Message -
SNIP

On Tuesday, May 25, 2004 8:15 pm
Luke Kearney [EMAIL PROTECTED] wrote:

 When you used /stand/sysinstall again did you reboot to get the IP or
 did you bring up the interface by hand? I am wondering if having only
 one config line in rc.conf gives you no IP upon boot whether or not
 having booted and go no address can you get one by using netstart 
 or not?
 eg
 
 #sh /etc/netstart
 
 This should re-read your rc.conf file and execute the network related
 cmds.

After sh /etc/netstart I get :

hw.bus.devctl_disable: 1- 1
 (then the lo0 printou)
dhclient already running? (pid-221)

and ifconfig -a unchanged. have to use sysinsstall.

 
 One more shot in the dark and believe me this is a shot in the 
 dark, try
 changing the line in rc.conf to ifconfig_sk0=UP and then through
 rc.local run dhclient as a separate script. The net effect being that
 you start the interface before trying to get an IP as a separate 
 process. 

I tried this but it didn't change anything...if I did it right?
I edited rc.conf and changed the line
[ifconfig_sk0=DHCP] to [ifconfig_sk0=UP] and created
/usr/local/etc/rc.d/rc.local to read
ifconfig_sk0=DHCP

When I did this I could never i initialize DHCP. Even sysinstall failed.

as a side note, during boot, the sequence delays for over a minute during
starting DHClient. It can't initialize sk0 but sysinstall can. Go figure?

 
 
 Just out of curiousity, your other three machines that don't have this
 problem, are they all identical to the machine that does? Somehow I
 think they are probably all unique in which case we can continue to
 focus on the machine at hand. 

You are absolutely right! My other boxes are all frankenputers.

Robert
 
 HTH
 
 LukeK
 
 -- 
 Luke Kearney [EMAIL PROTECTED]

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


Re: RE: ethernet card not coming up on reboot

2004-05-26 Thread hoe-waa
Aloha and Mahalo
Okay, that works. I dropped out of gnome and  logged 
ina s root. I deleted all the append data in rc.conf 
and I deleted /usr/local/etc/rc.d/rc.local.
I then rebooted. When I came back up ifconfig showed  
no ip address. I then did the killall -9 dhclient 
and the sh /etc/netstart. After that completed ifconfig
showed the ip address.
So, what's happening? Is there a sequence problem or 
do I need to have a script run to kill dhclient and 
then run netstart?

Thanks for your time helping with this problem.
Robert

- Original Message -
From: Eric Crist [EMAIL PROTECTED]
Date: Wednesday, May 26, 2004 12:53 pm
Subject: RE: ethernet card not coming up on reboot

 Before you run the netstart command, you need to kill all processes
 named dhclient.  You can accomplish this with a:
 
 #killall -9 dhclient
 
 And then, #sh /etc/netstart
 
 Eric F Crist
 President
 AdTech Integrated Systems, Inc
 (612) 998-3588
 
 
 
 -Original Message-
 From: [EMAIL PROTECTED] [EMAIL PROTECTED]
 Sent: Wednesday, May 26, 2004 12:45 PM
 To: Luke Kearney
 Cc: Eric Crist; [EMAIL PROTECTED]
 Subject: Re: ethernet card not coming up on reboot
 
 
 
 Subject: Re: ethernet card not coming up on reboot
 
 
  On Tue, 25 May 2004 20:00:12 -1000
  [EMAIL PROTECTED] spake thus:
 
   Aloha Eric and Luke
  
   I am aware that sysinstall will append to rc.conf.
   I went ahead and deleted all of the appends and rebooted. The
   ethernet did not come up on reboot. I had to use sysinstall to get
   an ip. And yes, it did append to rc.conf again.
  
   I will look into setting a static ip but I would like
   to know why this is happening. I have 3 other boxes
   that have FreeBSD on them and they don't have this problem.
  
   Robert
  
   - Original Message -
 SNIP
 
 On Tuesday, May 25, 2004 8:15 pm
 Luke Kearney [EMAIL PROTECTED] wrote:
 
  When you used /stand/sysinstall again did you reboot to get the 
 IP or
  did you bring up the interface by hand? I am wondering if having 
 only one config line in rc.conf gives you no IP upon boot whether 
 or not
  having booted and go no address can you get one by using netstart or
  not? eg
 
  #sh /etc/netstart
 
  This should re-read your rc.conf file and execute the network 
 related cmds.
 
 After sh /etc/netstart I get :
 
 hw.bus.devctl_disable: 1- 1
 (then the lo0 printou)
 dhclient already running? (pid-221)
 
 and ifconfig -a unchanged. have to use sysinsstall.
 
 
  One more shot in the dark and believe me this is a shot in the
  dark, try
  changing the line in rc.conf to ifconfig_sk0=UP and then through
  rc.local run dhclient as a separate script. The net effect being 
 that you start the interface before trying to get an IP as a separate
  process.
 
 I tried this but it didn't change anything...if I did it right? I 
 editedrc.conf and changed the line [ifconfig_sk0=DHCP] to
 [ifconfig_sk0=UP] and created /usr/local/etc/rc.d/rc.local to read
 ifconfig_sk0=DHCP
 
 When I did this I could never i initialize DHCP. Even sysinstall 
 failed.
 as a side note, during boot, the sequence delays for over a minute
 during starting DHClient. It can't initialize sk0 but sysinstall 
 can. Go
 figure?
 
 
 
  Just out of curiousity, your other three machines that don't have 
 this
  problem, are they all identical to the machine that does? Somehow I
  think they are probably all unique in which case we can continue to
  focus on the machine at hand.
 
 You are absolutely right! My other boxes are all frankenputers.
 
 Robert
 
  HTH
 
  LukeK
 
  --
  Luke Kearney [EMAIL PROTECTED]
 
 
 

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


ethernet card not coming up on reboot

2004-05-25 Thread hoe-waa
Aloha

I have a little annoyance on one of my boxes. The box has an Asus 
P4P800 mobo with a 2.6GHz P4 and 1GB of DDR-400 Ram. I have FreeBSD 
5.2-RC1 loaded on a 120Gig SATA Hard disk. My ouput of uname -a:

p4# uname -a
FreeBSD p4.hawaii.rr.com 5.2-RC1 FreeBSD 5.2-RC1 #0: Sun Dec  7 22:15:14 
GMT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386


The mobo has an onboard 3COM 3C940 Gbit LAN controller. This device 
is recognised during boot as sk0 and uses the SysKonnectPCI driver.

The problem is that after a reboot a DHCP address is not assigned to 
sk0. Here is ifconfig -a after a reboot.

p4# ifconfig -a
sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1
ether 00:0c:6e:91:de:a6
media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1)
status: active
plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3

Here is the output of resolv.conf and rc.conf

p4# cat /etc/resolv.conf
search hawaii.rr.com
nameserver 24.25.227.66
nameserver 24.25.227.33
nameserver 24.25.227.64

p4# cat /etc/rc.conf

# -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004
# Created: Thu May 20 10:05:35 2004
# Enable network daemons for user convenience.
# Please make all changes to this file, not to /etc/defaults/rc.conf.
# This file now contains just the overrides from /etc/defaults/rc.conf.
hostname=p4.hawaii.rr.com
ifconfig_sk0=DHCP
linux_enable=YES
nfs_client_enable=YES
sshd_enable=YES
usbd_enable=YES
# This file now contains just the overrides from /etc/defaults/rc.conf.
# Please make all changes to this file, not to /etc/defaults/rc.conf.

# Enable network daemons for user convenience.
# Created: Thu May 20 20:27:06 2004
# -- sysinstall generated deltas -- # Thu May 20 20:27:06 2004
ifconfig_sk0=DHCP
hostname=p4.hawaii.rr.com
# This file now contains just the overrides from /etc/defaults/rc.conf.
# Please make all changes to this file, not to /etc/defaults/rc.conf.

# Enable network daemons for user convenience.

Notice that there is a second entry in rc.conf relating to sk0. 

If I enter /stand/sysinstall and choose configure then networking and then 
interfaces and then chooses DHCP, the fields are all populated with the 
correct information. I can then exit back to the # and when I then
look at ifconfig -a I get some good stuff! 

p4# ifconfig -a
sk0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
inet6 fe80::20c:6eff:fe91:dea6%sk0 prefixlen 64 scopeid 0x1
inet 192.168.1.103 netmask 0xff00 broadcast 192.168.1.255
ether 00:0c:6e:91:de:a6
media: Ethernet autoselect (100baseTX full-duplex,flag0,flag1)
status: active
plip0: flags=8810POINTOPOINT,SIMPLEX,MULTICAST mtu 1500
lo0: flags=8049UP,LOOPBACK,RUNNING,MULTICAST mtu 16384
inet 127.0.0.1 netmask 0xff00
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3

Notice I now have an inet line populated with an IP address.

If I now look at rc.conf I get this

p4# cat /etc/rc.conf

# -- sysinstall generated deltas -- # Thu May 20 10:05:35 2004
# Created: Thu May 20 10:05:35 2004
# Enable network daemons for user convenience.
# Please make all changes to this file, not to /etc/defaults/rc.conf.
# This file now contains just the overrides from /etc/defaults/rc.conf.
hostname=p4.hawaii.rr.com
ifconfig_sk0=DHCP
linux_enable=YES
nfs_client_enable=YES
sshd_enable=YES
usbd_enable=YES
# This file now contains just the overrides from /etc/defaults/rc.conf.
# Please make all changes to this file, not to /etc/defaults/rc.conf.

# Enable network daemons for user convenience.
# Created: Thu May 20 20:27:06 2004
# -- sysinstall generated deltas -- # Thu May 20 20:27:06 2004
ifconfig_sk0=DHCP
hostname=p4.hawaii.rr.com
# This file now contains just the overrides from /etc/defaults/rc.conf.
# Please make all changes to this file, not to /etc/defaults/rc.conf.

# Enable network daemons for user convenience.
# Created: Tue May 25 16:17:31 2004
# This file now contains just the overrides from /etc/defaults/rc.conf.
# Please make all changes to this file, not to /etc/defaults/rc.conf.

# Enable network daemons for user convenience.
# Created: Tue May 25 17:28:40 2004
# This file now contains just the overrides from /etc/defaults/rc.conf.
# Please make all changes to this file, not to /etc/defaults/rc.conf.

# Enable network daemons for user convenience.
# Created: Tue May 25 17:31:13 2004
# -- sysinstall generated deltas -- # Tue May 25 17:31:13 2004
ifconfig_sk0=DHCP
hostname=p4.hawaii.rr.com

Still another entry for sk0!!

As I stated at the begimming of this epic, this is merely an annoyance. I 
don't reboot all that often and when I do I usually log in as a normal user. 
Of course, at that time, 

Re: can't startx after upgrade

2004-05-24 Thread hoe-waa
Thanks for responding Jason.

Yes, I used the script from gnome.
This is the 3rd box I have upgraded and the 
first problem of this nature.

Robert

- Original Message -
From: jason [EMAIL PROTECTED]
Date: Sunday, May 23, 2004 4:55 pm
Subject: Re: can't startx after upgrade

 [EMAIL PROTECTED] wrote:
 
 Aloha
 
 I have just successfully upgrade gnome 2.4 to gnome 2.6. At least
 that's the message I received after running the upgrade script. :)
 
 Before the upgrade all was working well. After the upgrade 
 I have some problems. I cannot startx from a regular user login.
 
 When trying, I get the following errors:
 
 $startx
 xauth: timeout in locking authority file /home/robert/.Xauthority
 xauth: timeout in locking authority file /home/robert/.Xauthority
 xauth: timeout in locking authority file /home/robert/.Xauthority
 xauth: timeout in locking authority file /home/robert/.Xauthority
 
 Fatal server error:
 Cannot move old logfile /var/log/XFree86.0.log.old
 
 When reporting a problem (blah, blah)
 
 
 giving up.
 xinit: No such file or directory (errno 2): unable to connect to X 
 serverxinit: No such process (errno 3): Server error.
 xauth: timeout in locking authority file /home/robert/.Xauthority
 $
 
 If I startx from a root login, I get to gnome but it seems to load 
 veryslow. 
 
 I also am not able to su from a normal login to root. 
 
 $su
 Password:
 May 22 06:48:27 bsd-desktop su: BAD SU robert to root on /dev/ttyv0
 su: Sorry
 $
 
 I am running FreeBSD 5.2RC. 
 
 TIA
 Robert
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-
 [EMAIL PROTECTED]
   
 
 There was a big problem with updating gnome if you did not check 
 freebsd/org/gnome first.  You have to download a script and run it 
 first.  If you did not, np, just follow the instructions and all 
 will be 
 good once more.
 
 Jason
 

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


can't startx from user after upgrade

2004-05-23 Thread hoe-waa
Hello

I have just successfully upgrade gnome 2.4 to gnome 2.6.
Well, at least that's the message on the screen after upgrade. :)

Before the upgrade all was working well. After the upgrade 
I have some problems. I cannot startx from a regular user login.

When trying, I get the following errors:

$startx
xauth: timeout in locking authority file /home/robert/.Xauthority
xauth: timeout in locking authority file /home/robert/.Xauthority
xauth: timeout in locking authority file /home/robert/.Xauthority
xauth: timeout in locking authority file /home/robert/.Xauthority

Fatal server error:
Cannot move old logfile /var/log/XFree86.0.log.old

When reporting a problem (blah, blah)


giving up.
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error.
xauth: timeout in locking authority file /home/robert/.Xauthority
$

If I startx from a root login, I get to gnome but it seems to load very
slow. 

I also am not able to su from a normal login to root. 

$su
Password:
May 22 06:48:27 bsd-desktop su: BAD SU robert to root on /dev/ttyv0
su: Sorry
$

I am running FreeBSD 5.2RC. 

TIA
Robert

P.S. If this message was duplicated, I apologize. 
I received a message from my mail admin that it 
could not be sent. So I am sending again.

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


Re: can't startx from user after upgrade

2004-05-23 Thread hoe-waa



From: arden [EMAIL PROTECTED]

 this may sound strange but is your disc full? 
 Ive had similar probs on Linux boxes when the disc is all but full 
 
 arden 
 

Aloha Arden
Funny you should ask Here is the output of df

bsd-desktop# df
Filesystem  1K-blocksUsed   Avail Capacity  Mounted on/dev/da1s2a253678   
75244  15814032%/
devfs   1   1   0   100%/dev/dev/da1s2e253678 208  
233176 0%/tmp/dev/da1s2d253678   55926  17745824%/var/dev/da1s4f   
4347996 2273842 172631657%/usrbsd-desktop#

If you notice, /usr is on a different slice. The 
upgrade had failed earlier because of lack of space 
where /usr was. I then set up a larger slice and 
moved /usr there. The upgrade then completed
so to speak.

So, isn't it curious that /home actually resides in 
/usr/home and it is the regular login accts that can't 
get to gnome. 

After receiving your email, I ran fsck on /usr and 
all was well.

Anything else I can try?

Robert


P.S. I did read the FAQ and I read it again. I checked 
the localhost stuff and the FAM stuff. All is well 
but it still takes root about 50 seconds to load 
gnome.



 On Sun, 2004-05-23 at 07:41, [EMAIL PROTECTED] wrote:
  Hello
  
  I have just successfully upgrade gnome 2.4 to gnome 2.6.
  Well, at least that's the message on the screen after upgrade. :)
  
  Before the upgrade all was working well. After the upgrade 
  I have some problems. I cannot startx from a regular user login.
  
  When trying, I get the following errors:
  
  $startx
  xauth: timeout in locking authority file /home/robert/.Xauthority
  xauth: timeout in locking authority file /home/robert/.Xauthority
  xauth: timeout in locking authority file /home/robert/.Xauthority
  xauth: timeout in locking authority file /home/robert/.Xauthority
  
  Fatal server error:
  Cannot move old logfile /var/log/XFree86.0.log.old
  
  When reporting a problem (blah, blah)
  
  
  giving up.
  xinit: No such file or directory (errno 2): unable to connect to 
 X server
  xinit: No such process (errno 3): Server error.
  xauth: timeout in locking authority file /home/robert/.Xauthority
  $
  
  If I startx from a root login, I get to gnome but it seems to 
 load very
  slow. 
  
  I also am not able to su from a normal login to root. 
  
  $su
  Password:
  May 22 06:48:27 bsd-desktop su: BAD SU robert to root on /dev/ttyv0
  su: Sorry
  $
  
  I am running FreeBSD 5.2RC. 
  
  TIA
  Robert
  
  P.S. If this message was duplicated, I apologize. 
  I received a message from my mail admin that it 
  could not be sent. So I am sending again.
  
  ___
  [EMAIL PROTECTED] mailing list
  http://lists.freebsd.org/mailman/listinfo/freebsd-questions
  To unsubscribe, send any mail to freebsd-questions-
 [EMAIL PROTECTED] 
 
 

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


can't startx after upgrade

2004-05-22 Thread hoe-waa
Aloha

I have just successfully upgrade gnome 2.4 to gnome 2.6. At least
that's the message I received after running the upgrade script. :)

Before the upgrade all was working well. After the upgrade 
I have some problems. I cannot startx from a regular user login.

When trying, I get the following errors:

$startx
xauth: timeout in locking authority file /home/robert/.Xauthority
xauth: timeout in locking authority file /home/robert/.Xauthority
xauth: timeout in locking authority file /home/robert/.Xauthority
xauth: timeout in locking authority file /home/robert/.Xauthority

Fatal server error:
Cannot move old logfile /var/log/XFree86.0.log.old

When reporting a problem (blah, blah)


giving up.
xinit: No such file or directory (errno 2): unable to connect to X server
xinit: No such process (errno 3): Server error.
xauth: timeout in locking authority file /home/robert/.Xauthority
$

If I startx from a root login, I get to gnome but it seems to load very
slow. 

I also am not able to su from a normal login to root. 

$su
Password:
May 22 06:48:27 bsd-desktop su: BAD SU robert to root on /dev/ttyv0
su: Sorry
$

I am running FreeBSD 5.2RC. 

TIA
Robert

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


Re: /usr out of space

2004-05-20 Thread hoe-waa
Aloha Nicholas
Thanks for responding. I had just received a hint
about growfs and while reading that I found out 
about newfs. I have indeed performed the newfs and 
can now mount /dev/da1s4f.
Would it be possible to use growfs to add the new 
slice to /usr?
If not, I will follow your instructions in this 
email.
Thanks again.
Robert


 On Wednesday 19 May 2004 08:17 pm, [EMAIL PROTECTED] wrote:
 
  When I tried using bsdlabel without any options I got an error.
  So I then did a bsdlabel -w da1s4 and the a bsdlabel -e da1s4
  and edited what I believe are the correct numbers for this slice.
  Now when I do the bsdlabel da1s4 with no options, I get
 
  # /dev/da1s4:
  8 partitions:
  #size   offsetfstype   [fsize bsize bps/cpg]
c:  89803350unused0 0 # raw 
 part, don't edit f:  8980319   164.2BSD 2048 16384 28552
 
 
  I still get the above error when trying to mount this slice.
 
  To sum it up.
 
  Is it possible to mount, copy and change the /usr partition?
 
  If so, how do I correct the super block problem so I can mount?
 
  Or, is there a much easier way and I have been spinning my wheels 
 for the last 6 hours?
 
   Perhaps I've missed a step, but it seems that you never did a 
 newfs /
 dev/da1s4f. If not, that would be an obvious explanation for the 
 incorrect super block error.
   At any rate, it is pretty easy to copy data from usr to a new 
 slice and 
 change fstab. I do it on occasion. I would recommend making a copy 
 of 
 fstab that has the da1s4f as the /usr partition. 
   I do a tunefs -n enable on the new filesystem device. Then, I boot 
 into 
 single user mode, mount -ro /usr and mount -rw /newusr (and I even 
 mount /var if I need to do editing with vi.) I then tar or copy the 
 files over (dump works, too). After all that's done, umount /usr 
 and 
 umount /newusr. Copy the new version of fstab to /etc/fstab, and 
 try a 
 mount /usr or mount -a. If there are no errors, you should be able 
 to 
 hit control-d and finish the boot procedure. 
 
 
 Nicholas
 
 
 
  TIA
 
  Robert
 
  P.S. Here's what bsdlabel on da1s2 looks like;
 
  bsd-desktop# bsdlabel da1s2
 

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


Re: /usr out of space

2004-05-20 Thread hoe-waa



 On Thursday 20 May 2004 02:19 am, [EMAIL PROTECTED] wrote:
  Aloha Nicholas
  Thanks for responding. I had just received a hint
  about growfs and while reading that I found out
  about newfs. I have indeed performed the newfs and
  can now mount /dev/da1s4f.
  Would it be possible to use growfs to add the new
  slice to /usr?
 It is possible to use growfs, but in your case - more complicated, 
 as 
 you have /usr and the new /usr in two different slices.  You'd have 
 to 
 resize the slice with fdisk, then use disklabel and growfs. 

I'm aware of that as I have been studying growfs 
and fdisk for the last half an hour. I wasn't 
wanting to waste that 2.3 Gig in the middle of 
slice 2 but now I think I'll use it for /home 
after I get /usr moved.

Thanks again and wish me luck because here I go!

Robert

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


Re: /usr out of space - FIXED

2004-05-20 Thread hoe-waa
Mahalo nui loa to all who responded. The solution provided by Nicholas 
worked. I now have adequate space on /usr.

Thanks again.

Robert

 
  On Thursday 20 May 2004 02:19 am, [EMAIL PROTECTED] wrote:
   Aloha Nicholas
   Thanks for responding. I had just received a hint
   about growfs and while reading that I found out
   about newfs. I have indeed performed the newfs and
   can now mount /dev/da1s4f.
   Would it be possible to use growfs to add the new
   slice to /usr?
  It is possible to use growfs, but in your case - more 
 complicated, 
  as 
  you have /usr and the new /usr in two different slices.  You'd 
 have 
  to 
  resize the slice with fdisk, then use disklabel and growfs. 
 
 I'm aware of that as I have been studying growfs 
 and fdisk for the last half an hour. I wasn't 
 wanting to waste that 2.3 Gig in the middle of 
 slice 2 but now I think I'll use it for /home 
 after I get /usr moved.
 
 Thanks again and wish me luck because here I go!
 
 Robert
 
 ___
 [EMAIL PROTECTED] mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to freebsd-questions-
 [EMAIL PROTECTED]

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


/usr out of space

2004-05-19 Thread hoe-waa
Aloha
I'm looking for a little direction (instructions or reading) that
could point me the right way. 

I have a box with an 18G scsi hd that has win98 loaded on slice 1,
FreeBSD 5.2RC loaded on slice 2 and I had a couple of linux distros
loaded in extended partitions. I had blown away one of the linux 
distros a while back. and that partition is idle.

Here is my problem. I ran out of space in /usr. 

Filesystem  1K-blocksUsed   Avail Capacity  Mounted on
/dev/da1s2a253678   75170  15821432%/
devfs   1   1   0   100%/dev
/dev/da1s2e253678 202  233182 0%/tmp
/dev/da1s2f   2421616 2419590 -191702   109%/usr
/dev/da1s2d253678   32722  20066214%/var
/dev/fd0 1424   91415 1%/tmp/floppy


My thoughts were to redo that idle slice (4.5Gig) to a UFS 
and cp usr to it. Then I could change my /etc/fstab to find 
/usr on the new slice. Is this possible?

I've been doing a lot of research (handbook, man bsdlabel, man ccd, 
etc.) and I haven't had much luck.

I first used sysinstall to fdisk the idle slice to a primary slice 
and set it as a type 165. I used the disk label editor in sysinstall
to try to create a single file system as FS and /usr. When trying to 
write this I got an error but the handbook says to ignore any errors.

After reboot, ls -l /dev/da* shows my new slice as da1s4f;

crw-r-  1 root  operator4,  12 May 19 12:59 /dev/da0
crw-r-  1 root  operator4,  14 May 19 12:59 /dev/da0s4
crw-r-  1 root  operator4,  13 May 19 12:59 /dev/da1
crw-r-  1 root  operator4,  15 May 19 12:59 /dev/da1s1
crw-r-  1 root  operator4,  16 May 19 12:59 /dev/da1s2
crw-r-  1 root  operator4,  19 May 19 02:59 /dev/da1s2a
crw-r-  1 root  operator4,  20 May 19 12:59 /dev/da1s2b
crw-r-  1 root  operator4,  21 May 19 12:59 /dev/da1s2c
crw-r-  1 root  operator4,  22 May 19 02:59 /dev/da1s2d
crw-r-  1 root  operator4,  23 May 19 02:59 /dev/da1s2e
crw-r-  1 root  operator4,  24 May 19 02:59 /dev/da1s2f
crw-r-  1 root  operator4,  17 May 19 12:59 /dev/da1s3
crw-r-  1 root  operator4,  18 May 19 12:59 /dev/da1s4
crw-r-  1 root  operator4,  27 May 19 12:59 /dev/da1s4c
crw-r-  1 root  operator4,  28 May 19 12:59 /dev/da1s4f
crw-r-  1 root  operator4,  25 May 19 12:59 /dev/da1s5
crw-r-  1 root  operator4,  26 May 19 12:59 /dev/da1s6

And doing an fdisk shows this

** Working on device /dev/da1 ***
parameters extracted from in-core disklabel are:
cylinders=2213 heads=255 sectors/track=63 (16065 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2213 heads=255 sectors/track=63 (16065 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 11 (0x0b),(DOS or Windows 95 with 32 bit FAT)
start 63, size 4883697 (2384 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 303/ head 254/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 4883760, size 8594775 (4196 Meg), flag 80 (active)
beg: cyl 304/ head 0/ sector 1;
end: cyl 838/ head 254/ sector 63
The data for partition 3 is:
sysid 5 (0x05),(Extended DOS)
start 22458870, size 13092975 (6393 Meg), flag 0
beg: cyl 1023/ head 254/ sector 63;
end: cyl 1023/ head 254/ sector 63
The data for partition 4 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 13478535, size 8980335 (4384 Meg), flag 0
beg: cyl 839/ head 0/ sector 1;
end: cyl 1023/ head 254/ sector 63

but when trying mount /dev/da1s4f /tmp/foo I get;

bsd-desktop# mount /dev/da1s4f /tmp/foo
mount: /dev/da1s4f on /tmp/foo: incorrect super block

When I tried using bsdlabel without any options I got an error.
So I then did a bsdlabel -w da1s4 and the a bsdlabel -e da1s4 
and edited what I believe are the correct numbers for this slice. 
Now when I do the bsdlabel da1s4 with no options, I get

# /dev/da1s4:
8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
  c:  89803350unused0 0 # raw part, don't edit
  f:  8980319   164.2BSD 2048 16384 28552 


I still get the above error when trying to mount this slice.

To sum it up. 

Is it possible to mount, copy and change the /usr partition?

If so, how do I correct the super block problem so I can mount?

Or, is there a much easier way and I have been spinning my wheels for 
the last 6 hours? 

TIA

Robert

P.S. Here's what bsdlabel on da1s2 looks like;

bsd-desktop# bsdlabel da1s2
# /dev/da1s2:
8 partitions:
#size   offsetfstype   [fsize bsize bps/cpg]
  a:   52428804.2BSD 2048 16384 32776
  b:  2012752   524288  swap
  c:  85947750unused0 0 # raw 

Re: mount_msdosfs anomaly

2004-05-16 Thread hoe-waa
ALoha Malcolm
I apologize, I should of answered yesterday.


- Original Message -
From: Malcolm Kay [EMAIL PROTECTED]
Date: Friday, May 14, 2004 5:14 pm
Subject: Re: mount_msdosfs anomaly

 On Saturday 15 May 2004 12:04, [EMAIL PROTECTED] wrote:
  -
 
   On Saturday 15 May 2004 08:59, [EMAIL PROTECTED] wrote:
Aloha Again
   
Okay, I had some time and since I had just installed 
 Slackware, I
  
   didn't mind blowing it away.
  
Using cfdisk from the Slackware CD, I re-partitioned  slices 3
  
   and up. I
  
now have a fat32 3Gig slice in primary partition/slice ad0s3. I
  
   then have
  
four 12 Gig slices (5 - 8) set up as linux partitions. Finally
  
   slice 9
  
(ad0s9/hda9) is linux swap.
  
   Do you still have Fat32 in slice 1?
  
   It is my impression that MS will not allow more than 1 MS primary
   slice. It
   will force 2nd and subsequent MS file systems into extended
   partitions. Of
   course if you created and formatted the slice outside of MS then
   the
   comment is irrelevant.
  
   Posting the output of fdisk (on FreeBSD) might help.
  
   Malcolm
 
  Aloha Malcolm
 
  Thanks for responding. Here is the output of fdisk when ran from 
 FBSD: frankie# fdisk
  *** Working on device /dev/ad0 ***
  parameters extracted from in-core disklabel are:
  cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl)
 
  Figures below won't work with BIOS for partitions not in cyl 1
  parameters to be used for BIOS calculations are:
  cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl)
 
  Media sector size is 512
  Warning: BIOS sector numbering starts with sector 1
  Information from DOS bootblock is:
  The data for partition 1 is:
  sysid 11 (0x0b),(DOS or Windows 95 with 32 bit FAT)
  start 63, size 10249407 (5004 Meg), flag 0
  beg: cyl 0/ head 1/ sector 1;
  end: cyl 637/ head 254/ sector 63
  The data for partition 2 is:
  sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
  start 10249470, size 40949685 (19994 Meg), flag 80 (active)
  beg: cyl 638/ head 0/ sector 1;
  end: cyl 1023/ head 254/ sector 63
  The data for partition 3 is:
  sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA))
  start 51199155, size 5863725 (2863 Meg), flag 0
  beg: cyl 1023/ head 254/ sector 63;
  end: cyl 1023/ head 254/ sector 63
  The data for partition 4 is:
  sysid 5 (0x05),(Extended DOS)
  start 57062880, size 99233505 (48453 Meg), flag 0
  beg: cyl 1023/ head 254/ sector 63;
  end: cyl 1023/ head 254/ sector 63
  frankie#
  As you can see, I still have 98SE on partition 1 and partition 3 
 shows as
  fat32. Slackware was re-installed and is working on P-8 with 
 linux-swap 0n
  P-9.
 
  Is this weird that I cannot mount ad0s3?
 
 
 OK, this has moved beyond my ken; but it has aroused my curiosity.
 
 What is the precise message when trying to mount ad0s3?
 

$ su
Password:
frankie# mount_msdosfs /dev/ad0s3 /shared
mount_msdosfs: /dev/ad0s3: Invalid argument
frankie#

 You do have a device /dev/ad0s3 revealed by ls?
 

Yes

frankie# ls -l /dev/ad*
crw-r-  1 root  operator4,  10 May 14 12:54 /dev/ad0
crw-r-  1 root  operator4,  11 May 14 12:54 /dev/ad0s1
crw-r-  1 root  operator4,  12 May 14 12:54 /dev/ad0s2
crw-r-  1 root  operator4,  16 May 14 02:54 /dev/ad0s2a
crw-r-  1 root  operator4,  17 May 14 12:54 /dev/ad0s2b
crw-r-  1 root  operator4,  18 May 14 12:54 /dev/ad0s2c
crw-r-  1 root  operator4,  19 May 14 02:54 /dev/ad0s2d
crw-r-  1 root  operator4,  20 May 14 02:54 /dev/ad0s2e
crw-r-  1 root  operator4,  21 May 14 02:54 /dev/ad0s2f
crw-r-  1 root  operator4,  13 May 14 12:54 /dev/ad0s3
crw-r-  1 root  operator4,  14 May 14 12:54 /dev/ad0s4
crw-r-  1 root  operator4,  22 May 14 12:54 /dev/ad0s5
crw-r-  1 root  operator4,  23 May 14 12:54 /dev/ad0s6
crw-r-  1 root  operator4,  24 May 14 12:54 /dev/ad0s7
crw-r-  1 root  operator4,  25 May 14 12:54 /dev/ad0s8
crw-r-  1 root  operator4,  26 May 14 12:54 /dev/ad0s9
frankie#

 Can you mount slice3 under slackware?
 
No. But I don't receive any error. Also, I have fstab in Slack supposedly auto 
mounting hda3 but it doesn't happen. curiouser and curiouser!

 You say MS reports the slice as FAT32, but has it actually been 
 formatted?Can you write to it?
 
Yes and Yes. In win98se I formated what appears as drive D: and then did a full scan 
disk. I have written 2 jpeg files and 1 text file to the drive for test purposes.

 Have you tried mounting the Slackware slice under FreeBSD?
 
Unfortunately, Slck is installed as reiserfs.

 Does someone out there know the significance of sysid 12 versus 
 sysid 11?
 
 I incidently I've found you can see inside an extended partition by 
 targeting 
 the extended partition/slice with fdisk instead of the entire 
 physical disk.
 (Which is probably quite irrelenent to your 

Re: mount_msdosfs anomaly

2004-05-15 Thread hoe-waa


- Original Message -
From: Mark Ovens [EMAIL PROTECTED]
Date: Saturday, May 15, 2004 2:18 am
Subject: Re: mount_msdosfs anomaly

Aloha Mark and thanks for responding. I'm sorry I wasn't able to get back to you 
sooner. I was in Kawaihae paddling in and outrigger canoe race. Alas, we didn't do 
very well. But, there's always next week.

 Malcolm Kay wrote:
 
  On Saturday 15 May 2004 12:04, [EMAIL PROTECTED] wrote:
  
  Here is the output of fdisk when ran from FBSD:
  frankie# fdisk
  *** Working on device /dev/ad0 ***
  parameters extracted from in-core disklabel are:
  cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl)
 
  Figures below won't work with BIOS for partitions not in cyl 1
  parameters to be used for BIOS calculations are:
  cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl)
 
  Media sector size is 512
  Warning: BIOS sector numbering starts with sector 1
  Information from DOS bootblock is:
  The data for partition 1 is:
  sysid 11 (0x0b),(DOS or Windows 95 with 32 bit FAT)
  start 63, size 10249407 (5004 Meg), flag 0
  beg: cyl 0/ head 1/ sector 1;
  end: cyl 637/ head 254/ sector 63
  The data for partition 2 is:
  sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
  start 10249470, size 40949685 (19994 Meg), flag 80 (active)
  beg: cyl 638/ head 0/ sector 1;
  end: cyl 1023/ head 254/ sector 63
  The data for partition 3 is:
  sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA))
  start 51199155, size 5863725 (2863 Meg), flag 0
  beg: cyl 1023/ head 254/ sector 63;
  end: cyl 1023/ head 254/ sector 63
  The data for partition 4 is:
  sysid 5 (0x05),(Extended DOS)
  start 57062880, size 99233505 (48453 Meg), flag 0
  beg: cyl 1023/ head 254/ sector 63;
  end: cyl 1023/ head 254/ sector 63
  frankie#
  As you can see, I still have 98SE on partition 1 and partition 3 
 shows as
  fat32. Slackware was re-installed and is working on P-8 with 
 linux-swap 0n
  P-9.
 
  Is this weird that I cannot mount ad0s3?
 
  
  Does someone out there know the significance of sysid 12 versus 
 sysid 11?
  
 
 According to the fdisk output sysid 11 is
  DOS or Windows 95 with 32 bit FAT
 and sysid 12 is
  DOS or Windows 95 with 32 bit FAT (LBA)
 
 The difference is LBA although I thought that if you needed to use 
 LBA 
 then the _whole disk_ was LBA but since slice 3 is visible in Win98 
 I 
 guess it's correct (probably just a case of FreeBSD reporting 
 _accurately_ what's on the disk).
 
 It's a few years since I messed with FAT so I may not have 
 remembered 
 this correctly, but originally DOS could only support a single 
 _active_ 
 primary partition (which is why extended was invented). Somewhere 
 in the 
 Win9x line that changed; the OS still had to be on the first 
 primary 
 partition but other primary partitions were visible in the OS.
 
 The OP says that Win98 can see /dev/ados3 and write to it but, if 
 you 
 look at the fdisk output only slice 1 is flagged 'active'.
 
 The last time I had a machine with multiple OSes (Win98, W2K, and 
 FreeBSD) I used BootMagic that comes with PartitionMagic which had 
 a 
 config option to choose which partitions/slices each OS could see. 
 With 
 FreeBSD the default setting hid _all_ the FAT  NTFS slices (I got 
 the 
 same problem you have) so I had to change the settings. The first 
 one or 
 two bytes in each entry in the partition table determine whether 
 the 
 partition is 'active' (i.e. the one that is booted from) but also 
 whether the partition is visible or hidden. When you choose an OS 
 from 
 BM's menu it edits the PT on the fly (which will set the BIOS 
 boot 
 sector anit-virus alarm off if it's enabled) and then continues the 
 boot 
 process.
 
 IIRC Win9x can see adso3 (in this case) by simply ignoring the 
 visible 
 flag, i.e. a kludge, in typical MS fashion.
 
 As to how to resolve it, if you are really brave you can edit the 
 partition table flags directly but the changes may not hold (I have 
 a 
 feeling that Win98 may fix them next time you boot Win98) or 
 install a 
 boot manager like BM that allows you to set the visibility.
 

I'm plenty brave as this is not a mission critical box!  :)

 If you run this
 
 # dd if=/dev/ad0 of=/tmp/foo bs=512 count=1
 # hd /tmp/foo  /tmp/foo.hd
 
 and post the last 6 lines of foo.hd it will help identify which 
 byte is 
 set wrong; I've a load of notes here about partition tables so I'll 
 dig 
 them out.

Here are the last few lines. I'm glad you know what we are looking at.

0180  cd 13 73 0f 4d 74 09 31  c0 cd 13 61 eb f1 b4 40  |..s.Mt.1...a...@|
0190  e9 46 ff 88 64 1f 8d 64  10 61 c3 c1 c0 04 e8 03  |.F..d..d.a..|
01a0  00 c1 c0 04 24 0f 27 04  f0 14 40 60 bb 07 00 b4  |$.'[EMAIL PROTECTED]|
01b0  0e cd 10 61 c3 00 00 00  b3 12 b0 3d cf c9 00 01  |...a...=|
01c0  01 00 0b fe bf 7d 3f 00  00 00 bf 64 9c 00 80 00  |.}?d|

Re: mount_msdosfs anomaly

2004-05-14 Thread hoe-waa
Aloha Again

Okay, I had some time and since I had just installed Slackware, I didn't mind blowing 
it away.

Using cfdisk from the Slackware CD, I re-partitioned  slices 3 and up. I now have a 
fat32 3Gig slice in primary partition/slice ad0s3. I then have four 12 Gig slices (5 - 
8) set up as linux partitions. Finally slice 9 (ad0s9/hda9) is linux swap.

I still have the same error when trying to mount_msdosfs /dev/ad0s3 /shared or 
mount -t msdos /dev/ad0s3 /shared

I know it is seen as a fat32 partition in Win98 because I format it and run scandisk 
on it and can write to it.

So, I don't think the problem was a primary/logical partition problem. I need to swap 
data between the OS's and this should be the easiest way.:)

Robert



  
  Aloha
  I first used a win98 boot disk to set slice 1(partition 1) a 5 
 Gig for 
  my win98 slice. After installing win98, I used the freebsd 5.2.1 
 CD to 
  set up the freebsd slice 2 at 20 Gig. 
 
 OK.  I haven't had time (or a spare machine) to play with 5.xxx 
 yet.

I have a spare frankenputer if you can get to Kona, I'll loan it to you :)
  
 
  After installing freebsd I used Slackware 9.1 CD and the cfdisk 
 program 
  on it to partition the rest of the disk. Slice/partition3 is a 
 primary. 
  Slice 4 is extended with logical slices/partitions 5 through 10. 
 I 
  installed Slackware on slice 8 with a linux swap on slice 9 and a 
 2.7Gig 
  fat32 on slice 10.
 
 Well, that (using Slackware and being logical partitions within
 an extended ) explains some things about how you got those slices. 
 
 I believe FreeBSD is quite limited in its ability to talk to 
 MS extended partitions.
 
  
snip

 
 When I attempt to mount slice 10 with mount_msdosfs 
 /dev/ad0s10/shared I get the following error:
 
 mount_msdosfs: /dev/ad0s10: invalid argument.
 
 Slice 10 was formatted in win98 and scan disk was run. I 
 have a
snip

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


Re: mount_msdosfs anomaly

2004-05-14 Thread hoe-waa


-

 On Saturday 15 May 2004 08:59, [EMAIL PROTECTED] wrote:
  Aloha Again
 
  Okay, I had some time and since I had just installed Slackware, I 
 didn't mind blowing it away.
 
  Using cfdisk from the Slackware CD, I re-partitioned  slices 3 
 and up. I
  now have a fat32 3Gig slice in primary partition/slice ad0s3. I 
 then have
  four 12 Gig slices (5 - 8) set up as linux partitions. Finally 
 slice 9
  (ad0s9/hda9) is linux swap.
 
 
 Do you still have Fat32 in slice 1?
 
 It is my impression that MS will not allow more than 1 MS primary 
 slice. It
 will force 2nd and subsequent MS file systems into extended 
 partitions. Of 
 course if you created and formatted the slice outside of MS then 
 the 
 comment is irrelevant.
 
 Posting the output of fdisk (on FreeBSD) might help.
 
 Malcolm
 
Aloha Malcolm

Thanks for responding. Here is the output of fdisk when ran from FBSD:
frankie# fdisk
*** Working on device /dev/ad0 ***
parameters extracted from in-core disklabel are:
cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl)

Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl)

Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 11 (0x0b),(DOS or Windows 95 with 32 bit FAT)
start 63, size 10249407 (5004 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 637/ head 254/ sector 63
The data for partition 2 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 10249470, size 40949685 (19994 Meg), flag 80 (active)
beg: cyl 638/ head 0/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
sysid 12 (0x0c),(DOS or Windows 95 with 32 bit FAT (LBA))
start 51199155, size 5863725 (2863 Meg), flag 0
beg: cyl 1023/ head 254/ sector 63;
end: cyl 1023/ head 254/ sector 63
The data for partition 4 is:
sysid 5 (0x05),(Extended DOS)
start 57062880, size 99233505 (48453 Meg), flag 0
beg: cyl 1023/ head 254/ sector 63;
end: cyl 1023/ head 254/ sector 63
frankie#
As you can see, I still have 98SE on partition 1 and partition 3 shows as fat32. 
Slackware was re-installed and is working on P-8 with linux-swap 0n P-9.

Is this weird that I cannot mount ad0s3?

Robert
 

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


mount_msdosfs anomaly

2004-05-12 Thread hoe-waa
Aloha

I have a 80 gig hard drive that I have sliced up for multiple distros of linux and 
freebsd. I have win98 on slice 1 and freebsd on slice 2. On slice 10 I have a 2.7 Gig 
slice formatted as fat32 for data sharing between all distros.

When logged into frebsd (5.2.1) i can mount the win98 slice with mount_msdosfs 
/dev/ad0s1 /win98 without any trouble.

When I attempt to mount slice 10 with mount_msdosfs /dev/ad0s10 /shared I get the 
following error:

mount_msdosfs: /dev/ad0s10: invalid argument.

Slice 10 was formatted in win98 and scan disk was run. I have a text file and two jpeg 
photos in the slice. 

Any help will be appreciated.

Thanks

Robert

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