Re: freebsd on laptop
Hi, On modern laptops, the BIOS allows you to boot from an USB key. So, you could prepare a key on another machine to bootstrap FreeBSD, by putting a proper MBR, partition table and partition (slice in FreeBSD vocabulary). The BIOS makes real-mode programs that use it believe the key is a regular floppy disk. Unless the FreeBSD's boot loader has problem or your BIOS does weird things, this should work. Please note that I've not tested this procedure myself, so I'm not 100% sure it will work. Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade error
Hi, You may be facing the same problem as I did a few days ago. Please see my previous post at: http://www.mail-archive.com/freebsd-hackers%40freebsd.org/msg52283.html for a quick (and dirty?) solution. Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading from 5.3 to 5.4
Has anybody done this yet? Any gotcha's, or is it a fairly smooth upgrade? Hi! Yes, I've done that a week ago, and everything went well. You only have to be careful with your compile options (in /etc/make.conf) if you have increased the optimization level for compiling ports (don't use more than -O). Just follow the handbook instructions (new procedure) and you're on your way. In case something fails and if you're not familiar with the booting process, read the section about how to boot your old kernel if the new one doesn't work. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Problem with libgphoto2, Canon Ixus v2 (USB) and 5.3-STABLE
Hi there, I've tried to download a few pics from my Canon Ixus v2 camera with libgphoto2 (frontends: kamera and gphoto2) without success. The camera is supported though, I even used libgphoto2 successfully on a Linux system with an older version of the lib (which I don't remember!). I've tried to add several traces to libgphoto2 to see where the problem was happening. I get as deep as usb_bulk_read but I haven't investigated further at the moment. libusb, libgphoto2 and gphoto2 have all been compiled from the ports collection, one time with and the other time without optimization flags, leading to the same result. Below is the output of gphoto2 --debug -l, in which there are some extra traces left (beginning with Olivier:). I see a strange 'Canon:PowerShot S200' at some point, but have not made anything of that. I've no special tweaks for usb. FreeBSD version is 5.3-STABLE, compiled with the following for usb (in case it would help): # USB support device uhci# UHCI PCI-USB interface #device ohci# OHCI PCI-USB interface device usb # USB Bus (required) #device udbp# USB Double Bulk Pipe devices device ugen# Generic device uhid# Human Interface Devices device ukbd# Keyboard device ulpt# Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse #device urio# Diamond Rio 500 MP3 player #device uscanner# Scanners Feel free to ask if you would like more information! Thanks for reading. Regards, Olivier PS: This post has been submitted to both the freebsd-questions and gphoto-devel mailing lists because it might interest both. No follow-up nor reply to! 0.33 main(2): ALWAYS INCLUDE THE FOLLOWING LINES WHEN SENDING DEBUG MESSAGES TO THE MAILING LIST: 0.001896 main(2): gphoto2 2.1.5 0.002171 main(2): gphoto2 has been compiled with the following options: 0.002470 main(2): + cc (C compiler used) 0.002728 main(2): + popt (for handling command-line parameters) 0.003014 main(2): + exif (for displaying EXIF information) 0.003292 main(2): + no cdk (for accessing configuration options) 0.003579 main(2): + aa (for displaying live previews) 0.003852 main(2): + jpeg (for displaying live previews in JPEG format) 0.004147 main(2): + readline (for easy navigation in the shell) 0.004443 main(2): libgphoto2 2.1.5 0.004698 main(2): libgphoto2 has been compiled with the following options: 0.004996 main(2): + cc (C compiler used) 0.005254 main(2): + EXIF (for special handling of EXIF files) 0.005537 main(2): + no ltdl (working around buggy libltdl, eh? :-) 0.005846 main(2): + no /proc/meminfo (adapts cache size to memory available) 0.006158 main(2): libgphoto2_port 0.5.1 0.006420 main(2): libgphoto2_port has been compiled with the following options: 0.006723 main(2): + cc (C compiler used) 0.007058 main(2): + USB (for USB cameras) 0.007319 main(2): + serial (for serial cameras) 0.007582 main(2): + no resmgr (serial port access and locking) 0.007864 main(2): + no baudboy (serial port locking) 0.008131 main(2): + no ttylock (serial port locking) 0.008403 main(2): + no lockdev (serial port locking) 0.008669 main(2): + no ltdl (working around buggy libltdl, eh? :-) 0.009132 main(2): The user has not specified both a model and a port. Try to figure them out. 0.009496 gp-port-info-list(2): Loading io-drivers from '/usr/local/lib/gphoto2_port/0.5.1'... 0.010304 gphoto2-port-serial(2): Trying to lock '/dev/cuaa0'... 0.013833 gphoto2-port-serial(2): Trying to lock '/dev/cuaa1'... 0.014186 gphoto2-port-serial(2): Trying to lock '/dev/cuaa2'... 0.014505 gphoto2-port-serial(2): Trying to lock '/dev/cuaa3'... 0.014822 gphoto2-port-serial(2): Trying to lock '/dev/cuaa4'... 0.015138 gphoto2-port-serial(2): Trying to lock '/dev/cuaa5'... 0.015456 gphoto2-port-serial(2): Trying to lock '/dev/cuaa6'... 0.015771 gphoto2-port-serial(2): Trying to lock '/dev/cuaa7'... 0.016088 gphoto2-port-serial(2): Trying to lock '/dev/cuaa8'... 0.016406 gphoto2-port-serial(2): Trying to lock '/dev/cuaa9'... 0.016725 gphoto2-port-serial(2): Trying to lock '/dev/cuaaa'... 0.017041 gphoto2-port-serial(2): Trying to lock '/dev/cuaab'... 0.017360 gphoto2-port-serial(2): Trying to lock '/dev/cuaac'... 0.017676 gphoto2-port-serial(2): Trying to lock '/dev/cuaad'... 0.017992 gphoto2-port-serial(2): Trying to lock '/dev/cuaae'... 0.018307 gphoto2-port-serial(2): Trying to lock '/dev/cuaaf'... 0.019431 gphoto2-port-core(2): Loaded '' (^serial) from 'libgphoto2_port_serial.so' 0.042286 gphoto2-port-core(2): Loaded 'Universal Serial Bus' (usb:) from 'libgphoto2_port_usb.so' 0.042929 gphoto2-port-core(2): Loaded 'Universal Serial Bus' (usb:/dev/usb1,/dev/ugen0)
Re: Keep compile options through upgrade
Thanks for these 2 answers. I didn't have seen this file mentioned in the portupgrade manpage, so I could have been searching for a while before finding... Le Vendredi 28 Janvier 2005 00:45, Glenn E. Sieb a écrit : Olivier Certner wrote: Hello all, Is there an easy way to keep/retrieve the options last used to compile a given port? This could be used with portupgrade to upgrade to a newer version while retaining the previous build-time configuration (of course this won't work if the options available change). Maybe I could put all the options in make.conf, but in this case I fear that this file would become really messy. Moreover, if options are shared by several ports, no fine grain tuning per port will be possible. Any advices? Check /usr/local/etc/pkgtools.conf Some ports keep things in /var/db/ports too... Best, --Glenn ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.3 interrupt storm (atapicam) and I/O error
Hi, Could you give a look at my post dated 04/01/2005 entitled Freeze with CAM (using KsCD)? Maybe we have fallen on the same kind of bug concerning atapicam. If you have KDE, maybe you should try to reproduce the problem I had. I've no time to test your scenario (the one with the EIDE drive, I don't have SCSI) now, but I'll try to reproduce it at the beginning of next week, in order to see if the freeze happens also on my computer. Hope this will help us to progress on our issues. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Keep compile options through upgrade
Hello all, Is there an easy way to keep/retrieve the options last used to compile a given port? This could be used with portupgrade to upgrade to a newer version while retaining the previous build-time configuration (of course this won't work if the options available change). Maybe I could put all the options in make.conf, but in this case I fear that this file would become really messy. Moreover, if options are shared by several ports, no fine grain tuning per port will be possible. Any advices? Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is bpf a part of IPFW, or am I confused?
I'm not able to give a deep answer on that. What I can say is that you must compile the kernel with bpf if you want to use the DHCP protocol or the tcpdump utility. It would be great if someone can clarify the precise roles of bpf. Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Freeze with CAM (using KsCD)
Hello all, I'm getting a problem when using KsCD, the KDE CD player, and the SCSI emulation for ATAPI devices within the kernel. A couple of minutes after having logged in with kdm, which launches a KDE session with a KsCD iconified, the whole machine freezes: apparently no more display update, impossible to move the pointer, etc. Pressing keys on the keyboard continues to work, but at a very low rate, ie if I do a CTRL+ALT+Fn to switch to console mode, I have to wait for 5 minutes... Then I'm sometimes able to login (sometimes keys are ignored), which means the kernel is still alive. Here are the logged messages I get every time the problem occurs: kernel: atapicam0: timeout sending command=a0 kernel: atapicam0: error issuing ATAPI packet command ...repeated lots of times... kernel: scsi_cd: error in readtocentries, returning EINVAL The only way I've found to avoid that is to deactivate KsCD in KDE. Despite that, I'm not totally sure if the problem is really trigerred by KsCD, since no precise visible operation seems to trigger it instantaneously. I use CAM in order to be able to burn CDs/DVDs, so I have compiled support for atapicam, among others, as these lines in my kernel conf file states: device ata device atadisk # ATA disk drives device atapicam# emulate ATAPI devices as SCSI ditto via CAM # needs CAM to be present (scbus pass) options ATA_STATIC_ID # Static device numbering device scbus # SCSI bus (required for SCSI) device cd # CD device pass# Passthrough device (direct SCSI access) There is no support for SCSI's hard disk since I just want to use my CD/DVD units through the emulation. I'm using FreeBSD 5.3-RELEASE for the kernel source (as well as for the KDE packages). Does anybody have heard something about that? It seems to me it is a bug but I would like some advices before submitting it. Thanks in advance for your answers. Regards, Olivier ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
