Kodak C195 digital camera appears to affect WD on usb
I know you'll think I'm crazy, but I'm pretty sure I've only started seeing these errors since plugging in this camera. Mar 22 01:06:22 laptop2 kernel: umass0: on usbus4 Mar 22 01:06:22 laptop2 kernel: Root mount waiting for: usbus4 Mar 22 01:06:22 laptop2 kernel: da0 at umass-sim0 bus 0 scbus0 target 0 lun 0 Mar 22 01:06:22 laptop2 kernel: da0: Fixed Direct Access SCSI-4 device Mar 22 01:06:22 laptop2 kernel: da0: 40.000MB/s transfers Mar 22 01:06:22 laptop2 kernel: da0: 476940MB (976773168 512 byte sectors: 255H 63S/T 60801C) Mar 22 01:10:24 laptop2 root: Unknown USB device: vendor 0x040a product 0x0600 bus uhub2 Mar 22 01:10:24 laptop2 kernel: ugen2.2: at usbus2 Mar 22 01:10:24 laptop2 kernel: umass1: on usbus2 Mar 22 01:10:26 laptop2 kernel: (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 Mar 22 01:10:26 laptop2 kernel: (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error Mar 22 01:10:26 laptop2 kernel: (probe0:umass-sim1:1:0:0): SCSI status: Check Condition Mar 22 01:10:26 laptop2 kernel: (probe0:umass-sim1:1:0:0): SCSI sense: NOT READY asc:3a,2 (Medium not present - tray open) Mar 22 01:11:32 laptop2 wpa_supplicant[413]: CTRL-EVENT-SCAN-RESULTS Mar 22 01:12:06 laptop2 login: 2 LOGIN FAILURES ON ttyv0 Mar 22 01:12:09 laptop2 login: ROOT LOGIN (root) ON ttyv0 Mar 22 01:12:19 laptop2 kernel: ugen2.2: at usbus2 (disconnected) Mar 22 01:12:19 laptop2 kernel: umass1: at uhub2, port 1, addr 2 (disconnected) I believe these next two were caused by the camera on umass-sim1 Mar 22 01:12:21 laptop2 kernel: (da0:umass-sim0:0:0:0): AutoSense failed Mar 22 01:12:21 laptop2 kernel: g_vfs_done():da0s1f[WRITE(offset=5780930560, length=16384)]error = 5 Here's a little config info: dmesg when plugging in camera ugen2.2: at usbus2 umass1: on usbus2 (probe0:umass-sim1:1:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error (probe0:umass-sim1:1:0:0): SCSI status: Check Condition (probe0:umass-sim1:1:0:0): SCSI sense: NOT READY asc:3a,2 (Medium not present - tray open) usbconfig ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=SAVE ugen4.1: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen4.2: at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen3.2: at usbus3, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen2.2: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON - System Name: laptop2.StevenFriedrich.org Window Manager(s): kde4-4.5.5_1 X Window System: xorg-7.5.1X.Org X Server 1.7.7 OS version: FreeBSD 8.2-RELEASE i386 (5.2 MB kernel) Platform:HP pavilion zd8000 (zd8215us) CPU: 2.80GHz Intel Pentium 4 (HTT) with 2 GB memory - FreeBSD Audio Driver (newpcm: 32bit 2009061500/i386) Installed devices: pcm0: (play/rec) default ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Mobile hard disk does not respond
Hi, On Tuesday 22 March 2011 10:04:42 xinyou yan wrote: > I have i mobile hard disk 320g . this is not of very much help. > > However ,frebsd can't respond to it > > ls dev/ > > have no message da0 for it Can you enlight us with information from dmesg and usbconfig? Maybe with and without the disk plugged in. FreeBSD does not recognise all USB/AT bridges properly. Maybe, you have bad luck. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Mobile hard disk does not respond
I have i mobile hard disk 320g . However ,frebsd can't respond to it ls dev/ have no message da0 for it ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
linux_compat libcups
Hi guys. Another minor issue is getting printers recognised in linux programs. For user functionality cups is the key- so avoiding it is impossible. I dumped libcups.so.2 from a F10 rpm, but this didn't work; aside from the fact it was an older library which I wasn't entirely sure would be a close enough hack. Do I need to install a complete cups client to make this work? Does the library need to match the client? The latter I ask because the programs appear to create a system call to lp/lpr, so I would assume the libraries don't need to be an exact match. The libraries seem to only query cups for available printers. Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Minimum system requirements
On 20 March 2011 03:52, aaron van caster wrote: > Just would like to know what are the minimum system/hardware requirements to > run 8.2 OS and do to have a simple video showing installation? > The absolute minimum to run sysinstall is something like 24MB on an 80486. I believe that once installed you can run with 16MB. 80386 support was taken out of GENERIC some time ago (6.x, maybe?). I don't know if those chips are supported at all, any more. Hard drive space is MUCH larger in a default install than 4,5,&6.x, but if you are creative you can get a whole system on a 350MB HDD. The embedded guys would have a lot better notion than I do. As a beginner, you should really consider 4GB to be a practical minimum. I don't know what to think of this: http://www.youtube.com/watch?v=perc0_7n52I I usually try to save my dancing until /after/ the install. -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
VMware fusion / USB 2.0 issues.
Good afternoon, I'm having a problem with a FreeBSD virtual machine on VMware fusion v3.1.2. Basically I get no USB 2.0 functionality. When I plug in a USB 2.0 mass storage device I get: uhub_reattach_port: port 1 reset failed, error=USB_ERR_TIMEOUT uhub_reattach_port: device problem (USB_ERR_TIMEOUT), disabling port 1 With some devices I can fix the problem by reconfiguring VMware Fusion for USB 1.0 / 1.1 only. With others the device appears unwilling to negotiate with a USB 1.1 root hub and this is unusable altogether. I'm running FreeBSD 8.2 PRERELEASE based on the 2011/01 snapshot. If anyone else has seen this can come up with a work around I'd appreciate any assistance they could provide. Thanks -- Chris "There will be an answer, Let it be." e: chris -at- vindaloo -dot- com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: gkrellm2 GnuTLS and OpenSSL, conky doesn't work :(
On Mon, Mar 21, 2011 at 2:08 PM, Daniel C. Dowse wrote: > On Mon, 21 Mar 2011 12:45:40 -0500, Antonio Olivares > > wrote: > [snip] >>On the other hand with conky, I get error >> >>[olivares@grullahighschool ~]$ conky -C > ~/.conkyrc >>[olivares@grullahighschool ~]$ conky >>Conky: Xft not enabled at compile time >>Conky: desktop window (143) is subwindow of root window (12b) >>Conky: window type - desktop >>Conky: drawing to created window (0x1e1) >>Conky: drawing to single buffer >>Segmentation fault: 11 (core dumped) >>[olivares@grullahighschool ~]$ conky >>Conky: Xft not enabled at compile time >>Conky: desktop window (143) is subwindow of root window (12b) >>Conky: window type - desktop >>Conky: drawing to created window (0x1e1) >>Conky: drawing to single buffer >> >> >>It starts up find, but then crashes. But I have gkrellm working so I >>am happy :) > [snap] > > Hi, > > you probably have to enable XFT support with make config in sysutils/conky > and > select that option. If this doesn't help to prevent conky from crashing, i > don't know either. I use Conky 1.8.1 on 8.1-RELEASE-p2 with no problems except > with some memory leak after a few days. With conky -v you can see the selected > options your conky was compiled with. > > cheers > > Daniel > > -- Daniel, gkrellm is working, tried to recompile conky with XFT support and it still crashes :( [olivares@grullahighschool ~]$ conky Conky: desktop window (143) is subwindow of root window (12b) Conky: window type - desktop Conky: drawing to created window (0x221) Conky: drawing to single buffer Segmentation fault: 11 (core dumped) For the moment I will stick to gkrellm :) Thanks for helping. Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: gkrellm2 GnuTLS and OpenSSL, conky doesn't work :(
On Mon, 21 Mar 2011 12:45:40 -0500, Antonio Olivares wrote: [snip] >On the other hand with conky, I get error > >[olivares@grullahighschool ~]$ conky -C > ~/.conkyrc >[olivares@grullahighschool ~]$ conky >Conky: Xft not enabled at compile time >Conky: desktop window (143) is subwindow of root window (12b) >Conky: window type - desktop >Conky: drawing to created window (0x1e1) >Conky: drawing to single buffer >Segmentation fault: 11 (core dumped) >[olivares@grullahighschool ~]$ conky >Conky: Xft not enabled at compile time >Conky: desktop window (143) is subwindow of root window (12b) >Conky: window type - desktop >Conky: drawing to created window (0x1e1) >Conky: drawing to single buffer > > >It starts up find, but then crashes. But I have gkrellm working so I >am happy :) [snap] Hi, you probably have to enable XFT support with make config in sysutils/conky and select that option. If this doesn't help to prevent conky from crashing, i don't know either. I use Conky 1.8.1 on 8.1-RELEASE-p2 with no problems except with some memory leak after a few days. With conky -v you can see the selected options your conky was compiled with. cheers Daniel -- \\|// (o o) ---ooO-(_)-Ooo--- - »Der vernünftige Mensch passt sich der Welt an; - - der unvernünftige Mensch versucht, die Welt seinem Wesen - - anzupassen. Deshalb kommt jeglicher Fortschritt - - vom unvernünftigen Menschen.« George Bernhard Shaw- - - Please send plain ASCII text only.- - Please reply below quoted text section. - - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Soekris net4801 running 8.2-R-p1 crashdumps
On 21-3-2011 16:30, Esa Karkkainen wrote: > Hi, > > My pf firewall running on net4801 has crashed twice this year. > > When the net4801 is handling more than 10Mbit/s of network > traffic, the box seems to crash. > That's not only for 8.2, I had M0n0 installed on my 4801, and it would totally lockup at 12Mbit/s, and in some instances crash also. I always thought it was related to the hardware (and especially the NICs). I solved that by buying a 5501. Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: gkrellm2 GnuTLS and OpenSSL, conky doesn't work :(
On 21/03/2011 18:45, Antonio Olivares wrote: On Mon, Mar 21, 2011 at 12:27 PM, David Demelier wrote: On 21/03/2011 16:57, Antonio Olivares wrote: Dear FreeBSD experts, I wanted to install gkrellm2 and I get the following error. grullahighschool# cd /usr/ports/sysutils/ grullahighschool# cd gkrellm2 grullahighschool# pwd /usr/ports/sysutils/gkrellm2 grullahighschool# make install clean ===> gkrellm-2.3.4_3 is marked as broken: GnuTLS and OpenSSL is mutually exclusive.. *** Error code 1 I think this is an error easy to understand for people that speak a little english. You can't install gkrellm2 with both GNUTLS and OPENSSL options at the same time! Do make config and disable GNUTLS (it's the default thus I assume you probably enabled it) Stop in /usr/ports/sysutils/gkrellm2. I then thought to myself conky can do the job too, so I tried to install it and it succeeded, but when I try to run it, I get the following: [olivares@grullahighschool ~]$ conky Conky: no readable personal or system-wide config file found You may need to write a ~/.conkyrc to run properly conky. Please read conky. It's easy to understand or search for conky examples on the web. I am running 8.1 freebsd [olivares@grullahighschool ~]$ uname -a FreeBSD grullahighschool.rgccisd.org 8.1-RELEASE-p0 FreeBSD 8.1-RELEASE-p0 #0: Mon Jul 26 08:26:45 UTC 2010 r...@hybrid.freebsdgr.org:/usr/obj/usr/src/sys/GENERIC amd64 Thanks for any pointers as to how to solve at least one of the two. If I can get conky to work, I'd be happy or get gkrellm running XFCE as the desktop. Cheers, -- David, Thank you very much for your help :) I have run # make config and disabled the bad guy and now I am in business with gkrellm. I did not know how to go back and make changes, and with your guidance I overcame the problem. On the other hand with conky, I get error [olivares@grullahighschool ~]$ conky -C> ~/.conkyrc [olivares@grullahighschool ~]$ conky Conky: Xft not enabled at compile time Conky: desktop window (143) is subwindow of root window (12b) Conky: window type - desktop Conky: drawing to created window (0x1e1) Conky: drawing to single buffer Segmentation fault: 11 (core dumped) [olivares@grullahighschool ~]$ conky Conky: Xft not enabled at compile time Conky: desktop window (143) is subwindow of root window (12b) Conky: window type - desktop Conky: drawing to created window (0x1e1) Conky: drawing to single buffer It starts up find, but then crashes. But I have gkrellm working so I am happy :) sorry I don't use conky anymore, it crashes and leave a core dump or not ? Some window manager does not handle well conky and may redraw the root over the conky that's why sometime the conky output may disappear. If this is your case take a look at the own_window or window_type settings (I don't know exactly sorry). Regards, Antonio Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: gkrellm2 GnuTLS and OpenSSL, conky doesn't work :(
On Mon, Mar 21, 2011 at 12:27 PM, David Demelier wrote: > On 21/03/2011 16:57, Antonio Olivares wrote: >> >> Dear FreeBSD experts, >> >> I wanted to install gkrellm2 and I get the following error. >> >> grullahighschool# cd /usr/ports/sysutils/ >> grullahighschool# cd gkrellm2 >> grullahighschool# pwd >> /usr/ports/sysutils/gkrellm2 >> grullahighschool# make install clean >> ===> gkrellm-2.3.4_3 is marked as broken: GnuTLS and OpenSSL is >> mutually exclusive.. >> *** Error code 1 >> > > I think this is an error easy to understand for people that speak a little > english. > > You can't install gkrellm2 with both GNUTLS and OPENSSL options at the same > time! > > Do make config and disable GNUTLS (it's the default thus I assume you > probably enabled it) > >> Stop in /usr/ports/sysutils/gkrellm2. >> >> >> I then thought to myself conky can do the job too, so I tried to >> install it and it succeeded, but when I try to run it, I get the >> following: >> >> [olivares@grullahighschool ~]$ conky >> Conky: no readable personal or system-wide config file found >> > > You may need to write a ~/.conkyrc to run properly conky. Please read conky. > It's easy to understand or search for conky examples on the web. > >> I am running 8.1 freebsd >> >> [olivares@grullahighschool ~]$ uname -a >> FreeBSD grullahighschool.rgccisd.org 8.1-RELEASE-p0 FreeBSD >> 8.1-RELEASE-p0 #0: Mon Jul 26 08:26:45 UTC 2010 >> r...@hybrid.freebsdgr.org:/usr/obj/usr/src/sys/GENERIC amd64 >> >> Thanks for any pointers as to how to solve at least one of the two. >> If I can get conky to work, I'd be happy or get gkrellm running XFCE >> as the desktop. >> > Cheers, > > -- David, Thank you very much for your help :) I have run # make config and disabled the bad guy and now I am in business with gkrellm. I did not know how to go back and make changes, and with your guidance I overcame the problem. On the other hand with conky, I get error [olivares@grullahighschool ~]$ conky -C > ~/.conkyrc [olivares@grullahighschool ~]$ conky Conky: Xft not enabled at compile time Conky: desktop window (143) is subwindow of root window (12b) Conky: window type - desktop Conky: drawing to created window (0x1e1) Conky: drawing to single buffer Segmentation fault: 11 (core dumped) [olivares@grullahighschool ~]$ conky Conky: Xft not enabled at compile time Conky: desktop window (143) is subwindow of root window (12b) Conky: window type - desktop Conky: drawing to created window (0x1e1) Conky: drawing to single buffer It starts up find, but then crashes. But I have gkrellm working so I am happy :) Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: gkrellm2 GnuTLS and OpenSSL, conky doesn't work :(
On 21/03/2011 16:57, Antonio Olivares wrote: Dear FreeBSD experts, I wanted to install gkrellm2 and I get the following error. grullahighschool# cd /usr/ports/sysutils/ grullahighschool# cd gkrellm2 grullahighschool# pwd /usr/ports/sysutils/gkrellm2 grullahighschool# make install clean ===> gkrellm-2.3.4_3 is marked as broken: GnuTLS and OpenSSL is mutually exclusive.. *** Error code 1 I think this is an error easy to understand for people that speak a little english. You can't install gkrellm2 with both GNUTLS and OPENSSL options at the same time! Do make config and disable GNUTLS (it's the default thus I assume you probably enabled it) Stop in /usr/ports/sysutils/gkrellm2. I then thought to myself conky can do the job too, so I tried to install it and it succeeded, but when I try to run it, I get the following: [olivares@grullahighschool ~]$ conky Conky: no readable personal or system-wide config file found You may need to write a ~/.conkyrc to run properly conky. Please read conky. It's easy to understand or search for conky examples on the web. I am running 8.1 freebsd [olivares@grullahighschool ~]$ uname -a FreeBSD grullahighschool.rgccisd.org 8.1-RELEASE-p0 FreeBSD 8.1-RELEASE-p0 #0: Mon Jul 26 08:26:45 UTC 2010 r...@hybrid.freebsdgr.org:/usr/obj/usr/src/sys/GENERIC amd64 Thanks for any pointers as to how to solve at least one of the two. If I can get conky to work, I'd be happy or get gkrellm running XFCE as the desktop. Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Character shortcuts
On Sat, Mar 12, 2011 at 5:24 PM, Chad Perrin wrote: > On Sat, Mar 12, 2011 at 02:07:59PM -0600, Antonio Olivares wrote: >> Dear FreeBSD experts, >> >> There has been something that I find hard to do, I would like to find >> a CTRL + KEY combination, or ALT + KEY combination to input special >> characters like (ñ) [ALT + 164 or ALT + 0241 in Mr. Gates OS]. >> >> http://www.forlang.wsu.edu/help/keyboards.asp >> >> accents other symbols like copyright, euro, etc. I would like to do >> the same(have a special key combination) to get the characters in >> FreeBSD too, but googling have not found something that works. I even >> tried to run a litte program in the shell to generate the characters >> to use for cutting + pasting to no avial. > > I wrote this about setting up a Compose key a while back: > > entering special characters in Xorg > http://sob.apotheon.org/?p=814 > > -- > Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] > Chad & all, using the command $ setxkbmap -option compose:ralt works very well :) Thank you all for the help provided. using the ALT key + SHIFT (TILDE ~) + n gives : ñ , accents and other special characters are easy to do now thanks to the much easier to follow than Mr. Gates OS :) Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
gkrellm2 GnuTLS and OpenSSL, conky doesn't work :(
Dear FreeBSD experts, I wanted to install gkrellm2 and I get the following error. grullahighschool# cd /usr/ports/sysutils/ grullahighschool# cd gkrellm2 grullahighschool# pwd /usr/ports/sysutils/gkrellm2 grullahighschool# make install clean ===> gkrellm-2.3.4_3 is marked as broken: GnuTLS and OpenSSL is mutually exclusive.. *** Error code 1 Stop in /usr/ports/sysutils/gkrellm2. I then thought to myself conky can do the job too, so I tried to install it and it succeeded, but when I try to run it, I get the following: [olivares@grullahighschool ~]$ conky Conky: no readable personal or system-wide config file found I am running 8.1 freebsd [olivares@grullahighschool ~]$ uname -a FreeBSD grullahighschool.rgccisd.org 8.1-RELEASE-p0 FreeBSD 8.1-RELEASE-p0 #0: Mon Jul 26 08:26:45 UTC 2010 r...@hybrid.freebsdgr.org:/usr/obj/usr/src/sys/GENERIC amd64 Thanks for any pointers as to how to solve at least one of the two. If I can get conky to work, I'd be happy or get gkrellm running XFCE as the desktop. Regards, Antonio ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Soekris net4801 running 8.2-R-p1 crashdumps
Hi, My pf firewall running on net4801 has crashed twice this year. When the net4801 is handling more than 10Mbit/s of network traffic, the box seems to crash. I have two crashdumps. I'll paste backtrace from the first one below. The backtrace from the second seems to be quite identical. #0 doadump () at pcpu.h:246 246 pcpu.h: No such file or directory. in pcpu.h (kgdb) #0 doadump () at pcpu.h:246 #1 0xc0572033 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:416 #2 0xc057223e in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:590 #3 0xc052e3e3 in hardclock (usermode=-1, pc=3229071867) at /usr/src/sys/kern/kern_clock.c:765 #4 0xc078db81 in hardclockintr (frame=0xc13a8828) at /usr/src/sys/i386/isa/clock.c:138 #5 0xc078dd77 in clkintr (frame=0xc13a8828) at /usr/src/sys/i386/isa/clock.c:198 #6 0xc054bc15 in intr_event_handle (ie=0xc1423a80, frame=0xc13a8828) at /usr/src/sys/kern/kern_intr.c:1378 #7 0xc0779909 in intr_execute_handlers (isrc=0xc0825d60, frame=0xc13a8828) at /usr/src/sys/i386/i386/intr_machdep.c:251 #8 0xc078d5d7 in atpic_handle_intr (vector=0, frame=0xc13a8828) at /usr/src/sys/i386/isa/atpic.c:595 #9 0xc0775251 in Xatpic_intr0 () at atpic_vector.s:62 #10 0xc077b9fb in spinlock_exit () at cpufunc.h:348 #11 0xc078d85f in getit () at /usr/src/sys/i386/isa/clock.c:329 #12 0xc078e0b5 in DELAY (n=10) at /usr/src/sys/i386/isa/clock.c:424 #13 0xc05716d2 in shutdown_panic (junk=0x0, howto=260) at /usr/src/sys/kern/kern_shutdown.c:464 #14 0xc05720b3 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:419 #15 0xc057223e in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:590 #16 0xc0789cbc in trap_fatal (frame=0xc13a8a38, eva=12) at /usr/src/sys/i386/i386/trap.c:938 #17 0xc0789f40 in trap_pfault (frame=0xc13a8a38, usermode=0, eva=12) at /usr/src/sys/i386/i386/trap.c:851 #18 0xc078a855 in trap (frame=0xc13a8a38) at /usr/src/sys/i386/i386/trap.c:533 #19 0xc07751ab in calltrap () at /usr/src/sys/i386/i386/exception.s:165 #20 0xc05c2118 in m_copydata (m=0x0, off=0, len=12, cp=0xc1cc086c "") at /usr/src/sys/kern/uipc_mbuf.c:819 #21 0xc0638345 in ip_forward (m=0xc1bf7e00, srcrt=1) at /usr/src/sys/netinet/ip_input.c:1471 #22 0xc0639c09 in ip_input (m=0xc1bf7e00) at /usr/src/sys/netinet/ip_input.c:735 #23 0xc061d319 in netisr_dispatch_src (proto=1, source=0, m=0xc1bf7e00) at /usr/src/sys/net/netisr.c:917 #24 0xc061d5b0 in netisr_dispatch (proto=1, m=0xc1bf7e00) at /usr/src/sys/net/netisr.c:1004 #25 0xc061852a in ether_demux (ifp=0xc1418400, m=0xc1bf7e00) at /usr/src/sys/net/if_ethersubr.c:901 #26 0xc0618a83 in ether_input (ifp=0xc1418400, m=0xc1bf7e00) at /usr/src/sys/net/if_ethersubr.c:760 #27 0xc04fc088 in sis_rxeof (sc=0xc1475600) at /usr/src/sys/dev/sis/if_sis.c:1477 #28 0xc04fcb93 in sis_poll (ifp=0xc1418400, cmd=POLL_ONLY, count=5) at /usr/src/sys/dev/sis/if_sis.c:1605 #29 0xc056480b in netisr_poll () at /usr/src/sys/kern/kern_poll.c:448 #30 0xc061d961 in swi_net (arg=0xc0c25800) at /usr/src/sys/net/netisr.c:748 #31 0xc054ac8b in intr_event_execute_handlers (p=0xc14267f8, ie=0xc143b400) at /usr/src/sys/kern/kern_intr.c:1220 #32 0xc054c2da in ithread_loop (arg=0xc1407b40) at /usr/src/sys/kern/kern_intr.c:1233 #33 0xc0548a00 in fork_exit (callout=0xc054c270 , arg=0xc1407b40, frame=0xc13a8d38) at /usr/src/sys/kern/kern_fork.c:844 #34 0xc0775220 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:270 -- "In the beginning the Universe was created. This has made a lot of people very angry and been widely regarded as a bad move." -- Douglas Adams 1952 - 2001 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD Boot
You can use "fdisk -B" to install non-interactive boot manager. Or you can use -t in boot0cfg to make timeout equals to zero. If after it you STILL have "F1" -- you probably boot from another drive: not da0 but da1. How many drives do you have? Check your BIOS settings to find which drive you boot from. Ilya. On Mon, Mar 21, 2011 at 3:48 PM, Michael Klapheke wrote: > Hi. I know this subject has been addressed in other posts, but I cannot > seem to get it to work. I have inherited a FreeBSD server and I cannot get > it to boot properly. I read the articles on avoiding having to press the F1 > key, and I tried to follow the suggestions (note, my disks are labeled > "da0s1" etc. instead of "ad0") as in the following: > > boot0cfg -B -b /boot/boot0 /dev/da0 > > or even > > fdisk -B -b /boot/boot0 /dev/da0 > > Neither of these prevents the user from having to press the F1 key. > > I also read the tutorial on how FreeBSD boots, but I cannot find anything > that helps. > > Any assistance is appreciated. > > Thanks > > Mike > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscr...@freebsd.org" > ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD Boot
On 21/03/2011 13:48, Michael Klapheke wrote:
Hi. I know this subject has been addressed in other posts, but I cannot seem to get it to work. I
have inherited a FreeBSD server and I cannot get it to boot properly. I read the articles on
avoiding having to press the F1 key, and I tried to follow the suggestions (note, my disks are
labeled "da0s1" etc. instead of "ad0") as in the following:
boot0cfg -B -b /boot/boot0 /dev/da0
or even
fdisk -B -b /boot/boot0 /dev/da0
Neither of these prevents the user from having to press the F1 key.
It's not a configurable parameter of the boot loader, you need a
different boot loader ("default").
However, why is that a problem? The user doesn't *have* to press the F1
key, he can just wait 5 seconds or so and the boot will proceed with the
last boot choice.
I also read the tutorial on how FreeBSD boots, but I cannot find anything that
helps.
T think the relevant lines from boot0cfg(8) are:
To go back to non-interactive booting, use fdisk(8) to install the
default MBR:
fdisk -B ad0
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: FreeBSD Boot
Hi, you have a bootmanager installed. On Monday 21 March 2011 19:48:27 Michael Klapheke wrote: > Hi. I know this subject has been addressed in other posts, but I cannot seem > to get it to work. I have inherited a FreeBSD server and I cannot get it to > boot properly. I read the articles on avoiding having to press the F1 key, > and I tried to follow the suggestions (note, my disks are labeled "da0s1" > etc. instead of "ad0") as in the following: > da are SCSI disks, ad are ATA disks. > boot0cfg -B -b /boot/boot0 /dev/da0 > > or even > > fdisk -B -b /boot/boot0 /dev/da0 > Just start sysinstall and write a plain mbr without a boot manager. > Neither of these prevents the user from having to press the F1 key. Of course not. Erich ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
FreeBSD Boot
Hi. I know this subject has been addressed in other posts, but I cannot seem to get it to work. I have inherited a FreeBSD server and I cannot get it to boot properly. I read the articles on avoiding having to press the F1 key, and I tried to follow the suggestions (note, my disks are labeled "da0s1" etc. instead of "ad0") as in the following: boot0cfg -B -b /boot/boot0 /dev/da0 or even fdisk -B -b /boot/boot0 /dev/da0 Neither of these prevents the user from having to press the F1 key. I also read the tutorial on how FreeBSD boots, but I cannot find anything that helps. Any assistance is appreciated. Thanks Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
RE: sguil-client startup problem
Paul, No worries, I had to deinstall tclX, ictl , iwidgets and sguil-client and reinstall them in the same order to make things work. Not touching the tcl8.5 installation. On the server side, Barnyard2 required an extra addition in the Makefile, referencing the --with-tcllib= location (after the mysql reference). Followed by a deinstall and install , resulting in a working snort -> barnyard2 -> sguil environment. Thanks for your time. Met vriendelijke groet / Kind regards, Danny van der Schaft -Oorspronkelijk bericht- Van: Paul Schmehl [mailto:pschmehl_li...@tx.rr.com] Verzonden: vrijdag 18 maart 2011 20:14 Aan: Schaft van der, D (Danny); freebsd-questions@freebsd.org Onderwerp: Re: sguil-client startup problem --On March 17, 2011 4:30:31 PM +0100 d.sch...@rn.rabobank.nl wrote: > I have a question regarding the installation and startup of sguil-client > on a 8.2 Generic OS. It seems that my installation requires an iwidget > extension when run with tclsh8.4 and receives an error when running > wish8.4: > > Error in startup script: can't read "0": no such variable while executing > Exec /usr/local/bin/wish8.4 "$0" "$@" line 5. > > I have all the required packages , I suppose > (tclX-8.4,tcl-8.4,tcllib,tcltls,tk8.4,ictl-3), also the iwidget extension > is installed... Strangely enough also version 8.5 is present on the > system, could that be a problem. Hopefully , there is someone who has > experienced the same or better yet, has an answer to my problem... > Apparently the default tcl install is now 8.5. Looks like I'm going to have to update the ports. You *may* be able to fix your problem by editing the sguil.tk file, although I'm not sure what other impacts that might have. The script calls wish8.4 explicitly, but that probably doesn't exist on your system. Change it to 8.5 and see if that fixes the problem. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell == Rabobank disclaimer: http://www.rabobank.nl/disclaimer ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: devd started with single-user mode?
On 21/03/2011 12:11, Polytropon wrote: On Mon, 21 Mar 2011 11:45:06 +0100, David Demelier wrote: By the way why is kbdmux needed for an usb keyboard? Should not be managed by ukbd only? I don't understand .. But thanks for the patch. Basically, the kbdmux option "wires keyboards in parallel", so you can use both keyboards (assume they are physically present) at the same time, like "one keyboard for each hand". If this option was not present, you would have to use "kbdcontrol -k" to switch from one keyboard (the currently active one) to the other (not usable). Problems may occur if your mainboard does provide an AT style keyboard (usually with PS/2 connector) as atkbdc0 and adkbd0 (controller and keyboard) even if there is no physical keyboard attached. This would then usually become the primary keyboard. A USB keyboard, detected later on as ukbd0, would not automatically be activated (or switched over to by a "kbdcontrol -k" command issued by devd) and can therefore not be used, even if physically present (in opposite to the "phantom" keyboard atkbd0). The kbdmux option makes _all_ keyboards available for input (without using "kbdcontrol -k" and without dependency of devd) so the USB keyboard will be used, the AT "phantom" keyboard will be ignored (which is good when it's not even present). So basically, kbdmux means "use all of them", while its absence means "use this or that". Thanks for this information :-) I understood. I hope the patch proposed will be MFC to -STABLE then. Kind regards, -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: devd started with single-user mode?
On Mon, 21 Mar 2011 11:45:06 +0100, David Demelier wrote: > By the way why is kbdmux needed for an usb keyboard? Should not be > managed by ukbd only? > > I don't understand .. But thanks for the patch. Basically, the kbdmux option "wires keyboards in parallel", so you can use both keyboards (assume they are physically present) at the same time, like "one keyboard for each hand". If this option was not present, you would have to use "kbdcontrol -k" to switch from one keyboard (the currently active one) to the other (not usable). Problems may occur if your mainboard does provide an AT style keyboard (usually with PS/2 connector) as atkbdc0 and adkbd0 (controller and keyboard) even if there is no physical keyboard attached. This would then usually become the primary keyboard. A USB keyboard, detected later on as ukbd0, would not automatically be activated (or switched over to by a "kbdcontrol -k" command issued by devd) and can therefore not be used, even if physically present (in opposite to the "phantom" keyboard atkbd0). The kbdmux option makes _all_ keyboards available for input (without using "kbdcontrol -k" and without dependency of devd) so the USB keyboard will be used, the AT "phantom" keyboard will be ignored (which is good when it's not even present). So basically, kbdmux means "use all of them", while its absence means "use this or that". -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Wireless always getting down/up
Hello,
In my university there is a special WPA-EAP access point used for safety.
I can't get a connection alive 15 minutes without being deconnected..
I noticed these messages when the problem appears :
Mar 21 11:58:42 Melon wpa_supplicant[351]: CTRL-EVENT-EAP-STARTED EAP
authentication started
Mar 21 11:58:42 Melon wpa_supplicant[351]: CTRL-EVENT-EAP-METHOD EAP
vendor 0 method 21 (TTLS) selected
Mar 21 11:58:42 Melon wpa_supplicant[351]: OpenSSL:
tls_connection_handshake - Failed to read possible Application Data
error::lib(0):func(0):reason(0)
Is this a wpa_supplicant/openssl trouble ?
This is the following configuration I must use (provided by my university)
network={
priority=10
ssid="eduroam"
proto=WPA2 WPA
scan_ssid=1
key_mgmt=WPA-EAP
pairwise=TKIP
group=TKIP
eap=TTLS
ca_cert="/etc/iut-cert.pem"
anonymous_identity="anonym...@u-strasbg.fr"
phase2="auth=PAP"
identity="myusername"
password="mypasssword"
}
Disabling ca_cert or enabling does not solve.
Cheers,
--
David Demelier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: glabel causes "GEOM: ada1: media size does not match label" messages
On Mon, 21 Mar 2011 06:40:51 -0400, Maxim Khitrov wrote: > I've been using 'dangerously dedicated' partitioning for years without > any issues. What problems have been reported by others? I think those "problems" originate from some operating systems not able to work with disks that do not come with a DOS-style partition table. This may be restricted to DOS-related operating systems (which I personally do not have to care about). For my needs, there has never been a problem booting from such a layout or accessing it. If you just have one slice (a.k.a. "DOS primary partition") and no other operating systems on the disk, there is _no_ particular requirement to create a slice, as far as I could experience. However, it may be needed in multi-boot constellations. The word "dangerous" (deserving the quotes) is, in my opinion, used to emphasize that there is the "danger" that *OTHER* operating systems can't deal with it. Those systems are traditionally located in MICROS~1 land. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: devd started with single-user mode?
On 21/03/2011 10:51, Pan Tsu wrote: David Demelier writes: The problem when you're using directly kbdmux in the kernel config, the ATKBD_DFLT_KEYMAP and UKBD_DFLT_KEYMAP are ineffective, you can't set these both together ... For me I added these both to use uk.iso but in single user mode I still have the standard us layout. Can you try the patch in kern/153459 ? It adds KBDMUX_DFLT_KEYMAP which allows using non-default layout in single user mode or ddb. By the way why is kbdmux needed for an usb keyboard? Should not be managed by ukbd only? I don't understand .. But thanks for the patch. Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: devd started with single-user mode?
On Mon, 21 Mar 2011 08:01:27 +0100, David Demelier wrote: > The problem when you're using directly kbdmux in the kernel config, the > ATKBD_DFLT_KEYMAP and UKBD_DFLT_KEYMAP are ineffective, you can't set > these both together ... Thanks for the pointer. Really! I know that it worked in the past (as you've noticed, I did define german keyboard settings), and it stopped working with FreeBSD 7. Of course I didn't use kbdmux prior to that. Good to know about that. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: glabel causes "GEOM: ada1: media size does not match label" messages
On Mon, Mar 21, 2011 at 12:30 AM, Carl Johnson wrote: > Maxim Khitrov writes: > >> On Sun, Mar 20, 2011 at 4:38 PM, Maxim Khitrov wrote: >>> Hi all, >>> >>> Executing the following commands on any valid storage device seems to >>> cause "media size does not match label" kernel messages (FreeBSD 8.2 >>> amd64). I understand why they happen - glabel metadata occupies the >>> last sector, so bsdlabel sees a device that is 1 sector smaller than >>> what the kernel sees. The question is whether there is some simple way >>> of suppressing these messages, since they come up every time the >>> system is booted or the partition is mounted/unmounted: >>> >>> # glabel label vol0 ada1 >>> # bsdlabel -w /dev/label/vol0 >>> GEOM: ada1: media size does not match label. >>> # newfs /dev/label/vol0a >>> # mount /dev/label/vol0a /mnt >>> GEOM: ada1: media size does not match label. >>> # umount /mnt >>> GEOM: ada1: media size does not match label. >>> >>> As you can see, I'm not using MBR or GPT partitioning schemes. I try >>> to avoid those unless I plan on sharing the media with another OS. >>> Even if using gpart would get rid of these errors (not sure, since >>> then you'll just have a partition whose size doesn't match), I would >>> still prefer to find some other way to suppress them. >>> >>> - Max > > I am not an expert, but that looks correct as you have it, so I would > expect some other problem. You are using vol0 as the partition for > newfs and its size should be correctly sized to allow for the last > sector of ada1 being used by glabel. I have heard comments that there > problems in what some call 'dangerously dedicated' partitions, so you > might want to create a single slice covering the whole disk and > partition that. I've been using 'dangerously dedicated' partitioning for years without any issues. What problems have been reported by others? > If you just want volume names for a filesystem, you might want to try > the -L option for either newfs or tunefs. The last example of the > glabel manpage shows using a ufs label to contrast it with glabel. I > use ufs labels for all of my filesystems and just use glabel for swap, > and I suspect that swapon wouldn't catch the type of problem that you > are seeing. I do use UFS labels where necessary. In this case, I'm writing a script that needs to access all bsdlabel partitions through a common name. >> Heh... In the process of searching for a solution to this, I decided >> to see what would happen if I used bsdlabel on ada1 rather than vol0 >> (in my example above), and created a 1-sector partition at the very >> end of the disk. So the layout would be something like this: >> >> # /dev/ada1: >> 8 partitions: >> # size offset fstype [fsize bsize bps/cpg] >> a: * * 4.2BSD >> c: * 0 unused >> h: 1 * unused >> >> The 'c' partition now covers the entire disk, which stops the kernel >> from complaining about media size not matching the label. At the same >> time, the 'h' partition will protect the last sector, which contains >> glabel metadata. >> >> The problem now is that the label is technically invalid for the vol0 >> device, which is what I'll be mounting. Indeed, bsdlabel complains >> when I run it for /dev/label/vol0: >> >> # /dev/label/vol0: >> 8 partitions: >> # size offset fstype [fsize bsize bps/cpg] >> a: 3907029151 16 4.2BSD 0 0 0 >> c: 3907029168 0 unused 0 0 >> h: 1 3907029167 unused 0 0 >> partition c: partition extends past end of unit >> bsdlabel: partition c doesn't cover the whole unit! >> bsdlabel: An incorrect partition c may cause problems for standard >> system utilities >> partition h: partition extends past end of unit >> >> I don't care about partition 'h'; it is there only to stop the >> preceding partition from covering the last sector. Are there any real >> issues with the 'c' partition being 1 sector too big for the vol0 >> device (but just the right size for ada1)? >> >> This is a bit of a hack, but I'll take it if it stops the kernel from >> complaining and doesn't create any new problems. > > I don't see where adding an extra partition at the end does anything to > protect the earlier partition. In my example, if I remove the 'h' partition, "a: * * 4.2BSD" will be sized to take-up the entire disk, including the sector containing glabel metadata. This would allow newfs/UFS to overwrite that sector with some other data. By adding an extra 1-sector partition at the end, I'm making sure that the metadata stays outside of 'a' or any other partition preceding 'h'. This is only necessary when allowing bsdlabel to pick partition sizes automatically (using '*' for size). Once bsdlabel is written, the 'h' partition can be deleted. It will simply show up as 1-sector free space at the end of ada1. - Max ___ freebsd-questions@freebsd
Re: devd started with single-user mode?
David Demelier writes: > The problem when you're using directly kbdmux in the kernel config, > the ATKBD_DFLT_KEYMAP and UKBD_DFLT_KEYMAP are ineffective, you can't > set these both together ... > > For me I added these both to use uk.iso but in single user mode I > still have the standard us layout. Can you try the patch in kern/153459 ? It adds KBDMUX_DFLT_KEYMAP which allows using non-default layout in single user mode or ddb. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
linux_compat ldap authentication
Just quickly off the top: has/is anyone working on a solution for this? Acrobat and other linux programs aren't running with ldap authentication setup on 8.x. Aside from running a periodic script to grab the passwd entries, I'm wondering if anyone has succeeded in finding/building ldap auth libraries or another alternative? Cheers ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
fstat bug?
Hi All, I have a Python program that goes up to 100% CPU. Just like this (top): PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 80212 user1 2 440 70520K 16212K select 1 0:30 100.00% /usr/local/bin/python process_updates_ss_od.py -l 10 I have added extra logs and it turns out that there are two threads. One thread is calling "time.sleep()" and the other is calling "os.stat" call. (Actually it is calling os.path.isfile, but I hunted down the last link in the chain.) The most interesting thing is that the process is in "SELECT" state. As far as I know, CPU load should be 0% because "select" state should block program execution until the I/O completes. I must also tell you that the os.stat call is taking long because this system has about 7 million files on a slow disk under heavy load. It would be normal for an os.stat call to return after 10 seconds. I have no problem with that. But I think that the 100% CPU is not acceptable. I guess that the code is running a system call in kernel mode. I think this because I can send a KILL signal to it and the state changes to the following: PID USERNAME THR PRI NICE SIZERES STATE C TIME WCPU COMMAND 80212 user1 2 440 70520K 15256K STOP5 1:27 100.00% /usr/local/bin/python process_updates_ss_od.py -l 10 So the state of the process changes to "STOP", but the program does not stop until the os.stat call returns back. Sometimes for a minute. Could it be a problem with the operation system? Is it possible that an os.stat call requires 100% CPU power from the OS? (I believe that os.stat ends in fstat()). Or is it a problem with the Python implementation? (Unfortunately I cannot give you an example program. Giving an example would require giving you a slow I/O device with millions of files on it.) OS version: FreeBSD 8.1-STABLE amd64 Python version: 2.6.6 Thanks, Laszlo -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: devd started with single-user mode?
On 20/03/2011 12:13, Polytropon wrote: On Sun, 20 Mar 2011 09:55:35 +0100, David Demelier wrote: Hello, I just realized that I can't use my USB keyboard if I start FreeBSD in single user mode. The keyboard is still detected but I can't use it. It works with the loader of course. I don't know if it's related to devd and if it's running. I also have USB legacy enabled in the BIOS settings. Do you have kbdmux in your kernel? If you don't have it, switching to "the other" keyboard is needed to be issued from the AT keyboard (if present), using the kbdcontrol program. Kernel configuration should contain: options KBD_INSTALL_CDEV# install a CDEV entry in /dev # atkbdc0 controls both the keyboard and the PS/2 mouse device kbdmux # keyboard multiplexer device atkbdc # AT keyboard controller device atkbd # AT keyboard options ATKBD_DFLT_KEYMAP makeoptions ATKBD_DFLT_KEYMAP=german.iso # USB support stuff here... device ukbd# Keyboard options UKBD_DFLT_KEYMAP makeoptions UKBD_DFLT_KEYMAP=german.iso If I remember correctly, most of the important lines are part of the GENERIC kernel configuration. On my system, I can't use the USB keyboard in CMOS setup or at the loader, but it works as soon as the kernel has finished loading, so when the boot process has enabled the single user mode, the USB keyboard is usable. For loader-related things, I still have to keep a PS/2 AT keyboard handy. The problem when you're using directly kbdmux in the kernel config, the ATKBD_DFLT_KEYMAP and UKBD_DFLT_KEYMAP are ineffective, you can't set these both together ... For me I added these both to use uk.iso but in single user mode I still have the standard us layout. Cheers, -- David Demelier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
