Re: icc8 failed on 4.10: Illegal instruction
On Tue, 28 Dec 2004, Kris Kennaway wrote: > On Wed, Dec 29, 2004 at 10:21:05AM +0300, Igor Sysoev wrote: > > > > > > > Then I installed the port and I ran /usr/local/intel_cc_80/bin/icc, > > > > > > but it always failed with message "Illegal instruction". > > > > > > > > > > You forgot to mention what type of CPU you have. > > > > > Sorry, it was so obvious for me that is not CPU problem in this case, > > > > so I forgot to mention it. From dmesg: > > > > > > > > CPU: Intel(R) Pentium(R) 4 CPU 2.66GHz (2679.56-MHz 686-class CPU) > > > > Origin = "GenuineIntel" Id = 0xf27 Stepping = 7 > > > 0x80b13d7 <__intel_proc_init_ftzdaz+79>:stmxcsr (%esp,1) > > > Strange, the code in __intel_proc_init_ftzdaz looks like the right code. > > Right now I can not say from what extention "stmxcsr" come from. > > Here is the features from dmesg: > > > > Features=0xbfebfbff > MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> > > It's an SSE instruction, and you need to enable support for SSE in > your kernel. Thank you. The "options CPU_ENABLE_SSE" resolves the problem. I think it should be mention in the port for 4.x. However, it seems that 4.10's headers are not good for icc8: >cat q.c #include >/usr/local/intel_cc_80/bin/icc q.c /usr/include/wchar.h(79): error: "__mbstate_t" has already been declared in the current scope } __mbstate_t; ^ /usr/include/libio.h(463): error: identifier "__gnuc_va_list" is undefined _IO_va_list, int *__restrict) __THROW; ^ /usr/include/libio.h(465): error: identifier "__gnuc_va_list" is undefined _IO_va_list) __THROW; ^ /usr/include/stdio.h(307): error: identifier "__gnuc_va_list" is undefined _G_va_list __arg) __THROW; ^ /usr/include/stdio.h(309): error: identifier "__gnuc_va_list" is undefined extern int vprintf (__const char *__restrict __format, _G_va_list __arg) ^ /usr/include/stdio.h(313): error: identifier "__gnuc_va_list" is undefined _G_va_list __arg) __THROW; ^ /usr/include/stdio.h(324): error: identifier "__gnuc_va_list" is undefined __const char *__restrict __format, _G_va_list __arg) ^ compilation aborted for q.c (code 2) Igor Sysoev http://sysoev.ru/en/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
MegaRAID 'Bad Slot' Kernel message and crash.
Folks, We have a 4.10-STABLE production server which has an Intel SRCU42X RAID controller installed: amr0: mem 0xfe58-0xfe5f,0xfbef-0xfbef irq 22 at device 0.0 on pci4 amr0: Firmware 411M, BIOS H404, 128MB RAM The server crashed yesterday in the small hours of the morning and when we arrived on site to reboot it, there was a "bad slot" kernel message on the console, which places the RAID controller in the frame. The amr driver man page says that this message is indicative of a firmware or hardware problem with the controller, but we are not convinced. We experienced the same message and lockups daily during stress testing of the box under FreeBSD 5.3 and this ultimately forced us to 'downgrade' to 4.10 for production. The box had been rock solid under 4.10 for a number of weeks before yesterday's crash. Could this indicate a bug in the driver, or at least in its support for our re-badged RAID controller? Has anyone else had problems with the amr driver with the same card? Many thanks, Regards, Tony. -- Tony Byrne ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: TIMEOUT - WRITE_DMA - A possible FIX! turn off ACPI
Arno J. Klaassen wrote: dunno, I'd more suspect ACPI<->APIC issues : untill now I only had problems on nForce based systems, but today I installed a brand new VIA based A7VT mini-server and re-voila les "XXX_DMA" errors (and accompanying severe system slow-down). (Disk swapped from the old PII-233 minimalist-server; worked OK there; disabling APIC (in BOIS and/or config and/or hints) made disappear the XXX_DMA messages (and gave me my network connexion back ;) ) whilst ACPI still enabled). No help here with ACPI or APIC disabled/enabled in any order. First ata-channel works ok with 40GB & 120GB disks, but second channel with single 160GB disk has *_DMA issues. 160GB disk works ok at PIO4 mode. Asus A7A266 motherboard with ALI chipset & Athlon 1333MHz processor. FreeBSD 5.3-STABLE (&RELEASE) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: icc8 failed on 4.10: Illegal instruction
On Wed, 29 Dec 2004, Igor Sysoev wrote: > On Tue, 28 Dec 2004, Kris Kennaway wrote: > > It's an SSE instruction, and you need to enable support for SSE in > > your kernel. > > Thank you. The "options CPU_ENABLE_SSE" resolves the problem. > I think it should be mention in the port for 4.x. The message about CPU_ENABLE_SSE exists, however it does not say about a signal: If you use icc on a Pentium 4 you may have to use 'options CPU_ENABLE_SSE' (depending on the OS version, if in doubt try if it works) in your kernel config (have a look at http://www.FreeBSD.org/handbook/ if you do not know how to do this), else icc will hang forever." > However, it seems that 4.10's headers are not good for icc8: > > >cat q.c > #include > > >/usr/local/intel_cc_80/bin/icc q.c > /usr/include/wchar.h(79): error: "__mbstate_t" has already been declared in > the current scope > } __mbstate_t; > ^ > > /usr/include/libio.h(463): error: identifier "__gnuc_va_list" is undefined > _IO_va_list, int *__restrict) __THROW; > ^ [ ... ] > /usr/include/stdio.h(324): error: identifier "__gnuc_va_list" is undefined > __const char *__restrict __format, _G_va_list __arg) > ^ > > compilation aborted for q.c (code 2) The __gnuc_va_list errors could be fixed by adding "-D__gnuc_va_list=va_list" to /usr/local/intel_cc_80/bin/icc.cfg and /usr/local/intel_cc_80/bin/icpc.cfg, but how to fix __mbstate_t error I do not know. Igor Sysoev http://sysoev.ru/en/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
calcru: negative runtime
Hi, I'm getting these messages calcru: negative runtime of -2792421 usec for pid 44 (swi5: clock sio) calcru: negative runtime of -2792421 usec for pid 44 (swi5: clock sio) calcru: negative runtime of -2789814 usec for pid 44 (swi5: clock sio) calcru: negative runtime of -2789814 usec for pid 44 (swi5: clock sio) I don't know what's wrong or if this is wrong. I'm running FreeBSD-stable (RELENG_5) I use the SMP kernel config and added options PREEMPTION Below is the dmesg output, what is wrong? Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #0: Mon Dec 27 19:16:11 CET 2004 root@:/usr/obj/usr/src/sys/Mipam ACPI APIC Table: Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Pentium(R) III CPU family 1133MHz (1125.78-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6b1 Stepping = 1 Features=0x383fbff real memory = 2147467264 (2047 MB) avail memory = 2096001024 (1998 MB) FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 3 cpu1 (AP): APIC ID: 0 MADT: Forcing active-low polarity and level trigger for SCI ioapic1 irqs 16-31 on motherboard ioapic0 irqs 0-15 on motherboard npx0: [FAST] npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x240-0x243 on acpi0 cpu0: on acpi0 cpu1: on acpi0 acpi_tz0: on acpi0 pcib0: on acpi0 pci0: on pcib0 ciss0: port 0x2000-0x20ff mem 0xf5ef-0xf5ef3fff,0xf7ec-0xf7ef irq 16 at device 1.0 on pci0 ciss0: [GIANT-LOCKED] fxp0: port 0x2400-0x243f mem 0xf7d0-0xf7df,0xf7eb-0xf7eb0fff irq 18 at device 2.0 on pci0 miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp0: Ethernet address: 00:02:a5:da:70:0d fxp1: port 0x2440-0x247f mem 0xf7b0-0xf7bf,0xf7cf-0xf7cf0fff irq 20 at device 4.0 on pci0 miibus1: on fxp1 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: Ethernet address: 00:02:a5:da:70:0c pci0: at device 5.0 (no driver attached) pci0: at device 6.0 (no driver attached) isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0x2c00-0x2c0f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 15.1 on pci0 ata0: channel #0 on atapci0 ata1: channel #1 on atapci0 ohci0: mem 0xf5fd-0xf5fd0fff irq 22 at device 15.2 on pci0 ohci0: [GIANT-LOCKED] usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: (0x1166) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pcib1: on acpi0 pci1: on pcib1 pcib2: on acpi0 pci7: on pcib2 pci7: at device 7.0 (no driver attached) atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] sio0: port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 16550A fdc0: port 0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 orm0: at iomem 0xee000-0xe,0xcc000-0xcd7ff,0xc8000-0xcbfff,0xc-0xc7fff on isa0 pmtimer0 on isa0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec acd0: CDROM at ata0-master PIO4 da0 at ciss0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 135.168MB/s transfers da0: 104183MB (213367680 512 byte sectors: 255H 32S/T 26148C) SMP: AP CPU #1 Launched! Mounting root from ufs:/dev/da0s1a calcru: negative runtime of -1785252 usec for pid 44 (swi5: clock sio) calcru: negative runtime of -1785252 usec for pid 44 (swi5: clock sio) calcru: negative runtime of -1638504 usec for pid 44 (swi5: clock sio) calcru: negative runtime of -1638483 usec for pid 44 (swi5: clock sio) calcru: negative runtime of -2792421 usec for pid 44 (swi5: clock sio) calcru: negative runtime of -2792421 usec for pid 44 (swi5: clock sio) calcru: negative runtime of -2789814 usec for pid 44 (swi5: clock sio) calcru: negative runtime of -2789814 usec for pid 44 (swi5: clock sio) Bye, Mipam. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MegaRAID 'Bad Slot' Kernel message and crash.
On Dec 29, 2004, at 12:18, Tony Byrne wrote: The amr driver man page says that this message is indicative of a firmware or hardware problem with the controller, but we are not convinced. We experienced the same message and lockups daily during stress testing of the box under FreeBSD 5.3 and this ultimately forced us to 'downgrade' to 4.10 for production. The box had been rock solid under 4.10 for a number of weeks before yesterday's crash. May I ask what kind of tests you ran? What motherboard do you have? I have a SRCU42X in a server with Intel motherboard (SE7501HG2), and have not made it crash yet. However, the box is not in production yet, so... I ran more generic tests and did not apply severe pressure on the disk subsystem: endless loop of buildworld -j8 bonnie++ running with one instance per array I think it ran for a week or so without any issues. But I would really like to try whatever you did to your servers to find out if I'll have the same issues here :-) -- Frode Could this indicate a bug in the driver, or at least in its support for our re-badged RAID controller? Has anyone else had problems with the amr driver with the same card? Many thanks, Regards, Tony. -- Tony Byrne ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: MegaRAID 'Bad Slot' Kernel message and crash.
Tony Byrne wrote: Folks, We have a 4.10-STABLE production server which has an Intel SRCU42X RAID controller installed: amr0: mem 0xfe58-0xfe5f,0xfbef-0xfbef irq 22 at device 0.0 on pci4 amr0: Firmware 411M, BIOS H404, 128MB RAM The server crashed yesterday in the small hours of the morning and when we arrived on site to reboot it, there was a "bad slot" kernel message on the console, which places the RAID controller in the frame. The amr driver man page says that this message is indicative of a firmware or hardware problem with the controller, but we are not convinced. We experienced the same message and lockups daily during stress testing of the box under FreeBSD 5.3 and this ultimately forced us to 'downgrade' to 4.10 for production. The box had been rock solid under 4.10 for a number of weeks before yesterday's crash. Could this indicate a bug in the driver, or at least in its support for our re-badged RAID controller? Has anyone else had problems with the amr driver with the same card? Many thanks, Regards, Tony. I've been seeing this problem recently too. I believe that there is some sort of timing bug/race in the driver, but I haven't been able to figure it out yet. It also seems to be related to panic from the block layer that point to commands being completed twice. To be clear with your observations, are you saying that 4.10-RELEASE is behaving the same or differently than 4.10-STABLE? Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
ucom and sio
Judging from the man page, ucom is limited to acting like a tty with no support for sio. Is this true? Is there some magic config bit somewhere that will enable hidden sio support? I have some old software that talks to some old hardware over rs232 (using cuaa) and the builtin 232 port just died. I'm trying to get a Bafo BF-810 working in raw mode but haven't had much luck (open()'s and write()'s block, unless non-blocking is set, but then they return without doing anything). Any suggestions? Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB scanner not attached when connected after system startup]
Getting no reaction from ``questions''. Thanks for any help. -- Harald Weis FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003 --- Begin Message --- My scanner (EPSON PERFECTION 1650) is working alright if it is connected before system startup. But when connected to the running system it doesn't get attached by usbd. I can't find out from Handbook, manpages or mailing lists what could be the reason. Many thanks in advance for any help. -- Harald Weis FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" --- End Message --- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re[2]: MegaRAID 'Bad Slot' Kernel message and crash.
Hello Scott, Wednesday, December 29, 2004, 2:46:04 PM, you wrote: SL> I've been seeing this problem recently too. I believe that there is SL> some sort of timing bug/race in the driver, but I haven't been able to SL> figure it out yet. It also seems to be related to panic from the block SL> layer that point to commands being completed twice. To be clear with SL> your observations, are you saying that 4.10-RELEASE is behaving the same SL> or differently than 4.10-STABLE? We tried 5.3 just after RELEASE, if I recall correctly, but had updated our sources and rebuilt world before running our tests. Under 5.3 we wedged the controller a number of times in the space of 3 days each with a "bad slot" kernel message. Once we decided that 5.3 was not a going to cut it for us, we downgraded to 4.10-STABLE (circa 16th Nov) and re-ran our tests, this time we couldn't wedge the system. The server has been in production on 4.10-STABLE for about a month and yesterday was the first "bad slot" wedge we've seen. I'd hate to think that we can now look forward to a monthly trip to the hosting facility to hard reset the box :-( Regards, Tony. -- Tony Byrne ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: icc8 failed on 4.10: Illegal instruction
On Wed, Dec 29, 2004 at 12:52:09PM +0300, Igor Sysoev wrote: > Thank you. The "options CPU_ENABLE_SSE" resolves the problem. > I think it should be mention in the port for 4.x. It is mentioned when you install the port. > However, it seems that 4.10's headers are not good for icc8: You'd have to talk to the maintainer. Kris pgp7JD52rD7XX.pgp Description: PGP signature
Re: icc8 failed on 4.10: Illegal instruction
On Wed, Dec 29, 2004 at 04:23:50PM +0300, Igor Sysoev wrote: > On Wed, 29 Dec 2004, Igor Sysoev wrote: > > > On Tue, 28 Dec 2004, Kris Kennaway wrote: > > > > It's an SSE instruction, and you need to enable support for SSE in > > > your kernel. > > > > Thank you. The "options CPU_ENABLE_SSE" resolves the problem. > > I think it should be mention in the port for 4.x. > > The message about CPU_ENABLE_SSE exists, however it does not say about > a signal: > > If you use icc on a Pentium 4 you may have to use 'options CPU_ENABLE_SSE' > (depending on the OS version, if in doubt try if it works) in your kernel > config (have a look at http://www.FreeBSD.org/handbook/ if you do not know > how to do this), else icc will hang forever." Please also raise this with the maintainer, or send a PR. Kris pgpqd1ALBQhcx.pgp Description: PGP signature
Re: USB scanner not attached when connected after system startup]
On Wed, Dec 29, 2004 at 04:49:05PM +0100, Harald Weis wrote: > My scanner (EPSON PERFECTION 1650) is working alright if it is > connected before system startup. But when connected to the running > system it doesn't get attached by usbd. I can't find out from > Handbook, manpages or mailing lists what could be the reason. > > Many thanks in advance for any help. Could you upgrade to 5.3? I've got a 1650 that works perfectly on 5.3-RELEASE on amd64. (BTW, 5.3 uses devfs). Roland -- R.F. Smith /"\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \Respect for open standards pgpZiHh5RJm9V.pgp Description: PGP signature
Re: cdrecord cannot see DVD-RW with ATAPICAM
Zahemszky Gábor wrote this message on Sat, Dec 18, 2004 at 08:30 +0100: > So the problem exists: how can it be, that "camcontrol devlist" shows an > ATAPICAM-generated "SCSI"-DVD-RW, but cdrecord couldn't see it with > "cdrecord -scanbus": > > $ camcontrol devlist > at scbus0 target 4 lun 0 (cd0,pass0) > at scbus0 target 13 lun 0 (da0,pass1) > at scbus0 target 15 lun 0 (da1,pass2) >at scbus2 target 0 lun 0 (cd1,pass3) ^^ ^ > $ cdrecord -scanbus > Cdrecord 2.00.3 (i386-unknown-freebsd5.2) Copyright (C) 1995-2002 Jörg > Schilling > Using libscg version 'schily-0.7' > scsibus0: > 0,0,0 0) * > 0,1,0 1) * > 0,2,0 2) * > 0,3,0 3) * > 0,4,0 4) 'YAMAHA ' 'CRW8824S' '1.00' Removable CD-ROM > 0,5,0 5) * > 0,6,0 6) * > 0,7,0 7) * Not sure if you solved your problem yet.. the reason cdrecord doesn't see your burner is that it's on the third scsi bus... why don't you try: cdrecord dev=2,0,0 -checkdrive Though you'll probably want to d/l the ProDVD version of cdrecord to be able to burn DVD's.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
how to remote update 4.10 -> 5.3?
Hi! Has anyone managed to update a 4.10 system to 5.3 remotely, i.e. without console access, and without spare disk partitions? I have a bunch of 4.10 machines that are too far away for me to actually do the update hands on. I've tried it on a test machine, it fails half way through installworld, and really needs single user mode to succeed. The install procedure fails since it starts using the newly installed stuff, things like sh(1) and test(1), and they cannot find their libc.so.5, I guess... One idea I have is copying / and /usr to some other place and set ldconfig and PATH=some/other/place and when building and installing. Haven't tried it yet, thought I'd hear anyone on this list has a better suggestion? Optimally, there would a couple of gigs on a separate spare disk partition so I could just install everything there and use it upon reboot. Problem is, there is no such space. :( Thanks Palle ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how to remote update 4.10 -> 5.3?
On Wed, Dec 29, 2004 at 09:30:37PM +0100, Palle Girgensohn wrote: > Has anyone managed to update a 4.10 system to 5.3 remotely, i.e. without > console access, and without spare disk partitions? > > I have a bunch of 4.10 machines that are too far away for me to actually do > the update hands on. I've tried it on a test machine, it fails half way > through installworld, and really needs single user mode to succeed. The > install procedure fails since it starts using the newly installed stuff, > things like sh(1) and test(1), and they cannot find their libc.so.5, I > guess... > > One idea I have is copying / and /usr to some other place and set ldconfig > and PATH=some/other/place and when building and installing. Haven't tried > it yet, thought I'd hear anyone on this list has a better suggestion? > > Optimally, there would a couple of gigs on a separate spare disk partition > so I could just install everything there and use it upon reboot. Problem > is, there is no such space. :( In general, my suggestion would be, don't do that. Do you really need to upgrade? Remember, 4.11 is likely to be supported for security upgrades into early 2006 so if your machines are working and you don't really need the new functionality, I'd suggest avoiding an upgrade. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpQcYiT6Z3pY.pgp Description: PGP signature
Re: how to remote update 4.10 -> 5.3?
--On onsdag, december 29, 2004 12.36.01 -0800 Brooks Davis <[EMAIL PROTECTED]> wrote: On Wed, Dec 29, 2004 at 09:30:37PM +0100, Palle Girgensohn wrote: Has anyone managed to update a 4.10 system to 5.3 remotely, i.e. without console access, and without spare disk partitions? I have a bunch of 4.10 machines that are too far away for me to actually do the update hands on. I've tried it on a test machine, it fails half way through installworld, and really needs single user mode to succeed. The install procedure fails since it starts using the newly installed stuff, things like sh(1) and test(1), and they cannot find their libc.so.5, I guess... One idea I have is copying / and /usr to some other place and set ldconfig and PATH=some/other/place and when building and installing. Haven't tried it yet, thought I'd hear anyone on this list has a better suggestion? Optimally, there would a couple of gigs on a separate spare disk partition so I could just install everything there and use it upon reboot. Problem is, there is no such space. :( In general, my suggestion would be, don't do that. Do you really need to upgrade? Remember, 4.11 is likely to be supported for security upgrades into early 2006 so if your machines are working and you don't really need the new functionality, I'd suggest avoiding an upgrade. Well, I need wide char support, as in iswlower and the likes. Maybe I could use some portability lib or similar...? Ideas? BTW, do you mean that 5.3 is not stable enough, or just that it is a nuisance to upgrade? While I agree that 4.10 is very stable, a lot of things have improved with 5.x... /Palle ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how to remote update 4.10 -> 5.3?
On Wed, Dec 29, 2004 at 09:49:10PM +0100, Palle Girgensohn wrote: > > > --On onsdag, december 29, 2004 12.36.01 -0800 Brooks Davis > <[EMAIL PROTECTED]> wrote: > > >On Wed, Dec 29, 2004 at 09:30:37PM +0100, Palle Girgensohn wrote: > >>Has anyone managed to update a 4.10 system to 5.3 remotely, i.e. without > >>console access, and without spare disk partitions? > >> > >>I have a bunch of 4.10 machines that are too far away for me to actually > >>do the update hands on. I've tried it on a test machine, it fails half > >>way through installworld, and really needs single user mode to succeed. > >>The install procedure fails since it starts using the newly installed > >>stuff, things like sh(1) and test(1), and they cannot find their > >>libc.so.5, I guess... > >> > >>One idea I have is copying / and /usr to some other place and set > >>ldconfig and PATH=some/other/place and when building and installing. > >>Haven't tried it yet, thought I'd hear anyone on this list has a better > >>suggestion? > >> > >>Optimally, there would a couple of gigs on a separate spare disk > >>partition so I could just install everything there and use it upon > >>reboot. Problem is, there is no such space. :( > > > >In general, my suggestion would be, don't do that. Do you really need > >to upgrade? Remember, 4.11 is likely to be supported for security > >upgrades into early 2006 so if your machines are working and you don't > >really need the new functionality, I'd suggest avoiding an upgrade. > > Well, I need wide char support, as in iswlower and the likes. Maybe I could > use some portability lib or similar...? Ideas? > > BTW, do you mean that 5.3 is not stable enough, or just that it is a > nuisance to upgrade? While I agree that 4.10 is very stable, a lot of > things have improved with 5.x... If you need the improved wide char support, then you will probably have to upgrade. 5.3 is generally stable, but I personally think upgrading for 4.x by any method other then a new install is a bad idea. It's certaintly possiable, but not trivial. I believe the instructions in UPDATING should work, but I've never tried them remotely. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpgYT7ZCk1uv.pgp Description: PGP signature
Re: how to remote update 4.10 -> 5.3?
--On onsdag, december 29, 2004 13.01.10 -0800 Brooks Davis <[EMAIL PROTECTED]> wrote: On Wed, Dec 29, 2004 at 09:49:10PM +0100, Palle Girgensohn wrote: --On onsdag, december 29, 2004 12.36.01 -0800 Brooks Davis <[EMAIL PROTECTED]> wrote: > On Wed, Dec 29, 2004 at 09:30:37PM +0100, Palle Girgensohn wrote: >> Has anyone managed to update a 4.10 system to 5.3 remotely, i.e. >> without console access, and without spare disk partitions? >> >> I have a bunch of 4.10 machines that are too far away for me to >> actually do the update hands on. I've tried it on a test machine, it >> fails half way through installworld, and really needs single user >> mode to succeed. The install procedure fails since it starts using >> the newly installed stuff, things like sh(1) and test(1), and they >> cannot find their libc.so.5, I guess... >> >> One idea I have is copying / and /usr to some other place and set >> ldconfig and PATH=some/other/place and when building and installing. >> Haven't tried it yet, thought I'd hear anyone on this list has a >> better suggestion? >> >> Optimally, there would a couple of gigs on a separate spare disk >> partition so I could just install everything there and use it upon >> reboot. Problem is, there is no such space. :( > > In general, my suggestion would be, don't do that. Do you really need > to upgrade? Remember, 4.11 is likely to be supported for security > upgrades into early 2006 so if your machines are working and you don't > really need the new functionality, I'd suggest avoiding an upgrade. Well, I need wide char support, as in iswlower and the likes. Maybe I could use some portability lib or similar...? Ideas? BTW, do you mean that 5.3 is not stable enough, or just that it is a nuisance to upgrade? While I agree that 4.10 is very stable, a lot of things have improved with 5.x... If you need the improved wide char support, then you will probably have to upgrade. 5.3 is generally stable, but I personally think upgrading for 4.x by any method other then a new install is a bad idea. It's certaintly possiable, but not trivial. I believe the instructions in UPDATING should work, but I've never tried them remotely. I've tried the UPDATING instructions, both locally and remotely (the latter failed ;-). But really, everything has to be reinstalled, ports and the lot, so a new install is probably the best way... Thanks for you input anyway! /Palle ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cdrecord cannot see DVD-RW with ATAPICAM
On Wed, 29 Dec 2004 11:14:04 -0800, John-Mark Gurney <[EMAIL PROTECTED]> wrote: > Though you'll probably want to d/l the ProDVD version of cdrecord to > be able to burn DVD's.. Either that or use dvd+rw-tools (see /usr/ports/sysutils/dvd+rw-tools). -- G. Stewart - [EMAIL PROTECTED] If you plan to leave your mark in the sands of time, you better wear work shoes. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: how to remote update 4.10 -> 5.3?
Palle Girgensohn wrote: I've tried the UPDATING instructions, both locally and remotely (the latter failed ;-). But really, everything has to be reinstalled, ports and the lot, so a new install is probably the best way... That's not so bad. A reinstall means you can newfs your partitions as UFS2 filesystems, which wouldn't be the case if you upgraded 4.10 in-place. Cheers, Paul. -- e-mail: [EMAIL PROTECTED] "Without music to decorate it, time is just a bunch of boring production deadlines or dates by which bills must be paid." --- Frank Vincent Zappa ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[Fwd: GThread_ERROR | glib2 | gthread-posix.c]
Thank you to all who replied to my message below. A clean install of 5.3, xorg, gnome &c.. solved the problem (a little drastic I'll admit, but I was going to have to upgrade at some point). Best regards, Richard Mahoney Forwarded Message From: Richard MAHONEY <[EMAIL PROTECTED]> To: Subscribers to FreeBSD-Stable Subject: GThread_ERROR | glib2 | gthread-posix.c Date: Sun, 26 Dec 2004 10:33:22 +1300 Dear Listmembers, I've just upgraded to `xorg-6.8.1' and have begun to experience seg. faults and core dumps with apps that rely on `glib-2.4.8'. The standard error is noted below. `gnome2-2.8.2' no longer works and I've had to revert to `pwm-2003.06.17'. A recompile of `glib', `gtk', all of `Gnome2' &c. has failed to resolve the problem. Does it have something to do with the following? : /usr/home/ports/devel/glib20/files/patch-gthread_gthread-posix.c Any help would be very much appreciated. Best regards, Richard Mahoney the system: [EMAIL PROTECTED] /usr/home/rbm49/pkg $ uname -a FreeBSD 131-203-240-72.remote.comnet.co.nz 4.11-STABLE FreeBSD \ 4.11-STABLE #0: Sun Dec 19 21:29:45 NZDT 2004 \ [EMAIL PROTECTED]:/usr/home/obj/usr/src/sys/GENERIC \ i386 the problem: [EMAIL PROTECTED] /usr/home/rbm49/pkg $ firefox GThread-ERROR **: file gthread-posix.c: line 137 \ (g_thread_impl_init): error 'Invalid argument' during \ 'pthread_getschedparam (pthread_self(), &policy, &sched)' aborting... Abort trap (core dumped) [EMAIL PROTECTED] /usr/home/rbm49/pkg $ rm -f *core firefox-bin.core ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB scanner not attached when connected after system startup]
On Wed, Dec 29, 2004 at 07:40:00PM +0100, Roland Smith wrote: > On Wed, Dec 29, 2004 at 04:49:05PM +0100, Harald Weis wrote: > > My scanner (EPSON PERFECTION 1650) is working alright if it is > > connected before system startup. But when connected to the running > > system it doesn't get attached by usbd. I can't find out from > > Handbook, manpages or mailing lists what could be the reason. > > > > Many thanks in advance for any help. > > Could you upgrade to 5.3? I've got a 1650 that works perfectly on > 5.3-RELEASE on amd64. (BTW, 5.3 uses devfs). Yes, no problem, I've planned to migrate to 5.3 anyway in 2 weeks time. But I would like to understand _why_ usbd's attach/detach function, as I understood it from Handbook and manpages, does not work on 4.X (I'm using the scanner since 2 or 3 years without any other problem). It should work, shouldn't it ? Do I mis-interpret e.g. usbd.conf(5) ? Harald -- FreeBSD 4.9-RELEASE #0: Mon Oct 27 17:51:09 GMT 2003 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB scanner not attached when connected after system startup]
On Wed, Dec 29, 2004 at 11:17:24PM +0100, Harald Weis wrote: > > Could you upgrade to 5.3? I've got a 1650 that works perfectly on > > 5.3-RELEASE on amd64. (BTW, 5.3 uses devfs). > > Yes, no problem, I've planned to migrate to 5.3 anyway in 2 weeks > time. But I would like to understand _why_ usbd's attach/detach > function, as I understood it from Handbook and manpages, does not work > on 4.X (I'm using the scanner since 2 or 3 years without any other > problem). It should work, shouldn't it ? Do I mis-interpret > e.g. usbd.conf(5) ? Try running usbd from a console or xterm with the -d flag. This gives debugging output, so you can see what's going on. If you're using devfs, make sure that you have a devfs.rules to set the user/group and the right permission for the scanner device. Roland -- R.F. Smith /"\ASCII Ribbon Campaign r s m i t h @ x s 4 a l l . n l \ /No HTML/RTF in email http://www.xs4all.nl/~rsmith/ X No Word docs in email / \Respect for open standards pgpnLcp3Cb84T.pgp Description: PGP signature
Memory handling problem with FreeBSD 5.3?
I have installed FreeBSD 5.3-STABLE i386 on a new Dell PowerEdge 2850, but it crashes under load like "make buildworld" with a "panic: page fault". The server has following configuration: 2x Intel Xeon 3.4 GHz (800 MHz FSB), 6x 1 GB DDR2 ECC RAM and Perc 4e/Di (LSI Logic/amr driver). After some days working on the problem, I think there is some problem with handling the memory. The only way I have got the server to become stable was by switching a special option in the Dell BIOS, which limits the system memory to 256 MB. I have tried to limit the memory to 4 GB by activating a spare memory bank, but the server still crashes. Disabling HTT in BIOS and ACPI in the loader also didn't solved the problem. The kernel is compiled with SMP of course and PAE because of >4 GB memory. I have removed all the unnecessary devices. Dells own diagnostic tool couldn't find any hardware errors. The special memory test also passed all tests. I have also tried with memtest (http://www.memtest.org/) which either could find any memory errors. Has anyone an idea to a solution? Has anyone succeeded running FreeBSD 5.3 on similar hardware? Would it maybe be better to run the AMD64 version of FreeBSD 5.3? I think the i386 version should be more stable? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Multiple Vinum Problems Since Upgrade From 4.9 To 4.10
Since an upgrade from 4.9 to 4.10, I've had problems with vinum. The basic problem is that upon reboot, two of my vinum drives show up as "referenced" and thus create the associated chaos. I've tried many things and fiddled around quite a bit so I can't say exactly what I've done. I can include all of the entries in the history file since Oct. 31 if that's a help but it would be a long list. So prior to digging that deep, I will describe where I stand currently and where I want to finish. Currently, I have one vinum volume that I use for /usr. Fortunately this volume is up and running or I would really be in a mess. Here's the 'vinum list' output in this state: blacklamb# vinum vinum -> list 2 drives: D disk1 State: up Device /dev/da0s1h Avail: 0/8383 MB (0%) D disk2 State: up Device /dev/da1s1h Avail: 0/8383 MB (0%) 1 volumes: V usr State: up Plexes: 1 Size: 16 GB 1 plexes: P usr.p0 S State: up Subdisks: 2 Size: 16 GB 2 subdisks: S usr.p0.s0 State: up PO:0 B Size: 8383 MB S usr.p0.s1 State: up PO: 256 kB Size: 8383 MB I want to add another volume and mount it on /ftp. After creating the volume, vinum sees it and it appears OK as indicated in this output: vinum -> list 5 drives: D disk1 State: up Device /dev/da0s1h Avail: 0/8383 MB (0%) D disk2 State: up Device /dev/da1s1h Avail: 0/8383 MB (0%) D ftp1 State: up Device /dev/ad0s1h Avail: 0/76319 MB (0%) D ftp2 State: up Device /dev/ad1s1h Avail: 0/76319 MB (0%) D ftp3 State: up Device /dev/da3s1h Avail: 0/114473 MB (0%) 2 volumes: V usr State: up Plexes: 1 Size: 16 GB V ftp State: up Plexes: 1 Size:260 GB 2 plexes: P usr.p0 S State: up Subdisks: 2 Size: 16 GB P ftp.p0 C State: up Subdisks: 3 Size:260 GB 5 subdisks: S usr.p0.s0 State: up PO:0 B Size: 8383 MB S usr.p0.s1 State: up PO: 256 kB Size: 8383 MB S ftp.p0.s0 State: up PO:0 B Size: 74 GB S ftp.p0.s1 State: up PO: 74 GB Size: 74 GB S ftp.p0.s2 State: up PO: 149 GB Size:111 GB Next I 'quit' the vinum command line and fsck my newly created volume. It finishes successfully and I mount it: blacklamb# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 30235010208817607437%/ /dev/vinum/usr 16639674 5433762 987473935%/usr procfs 4 4 0 100%/proc /dev/vinum/ftp 265119539 119729707 13213385648%/ftp I recheck with the 'vinum list' command and the output is the same as above. Now I cross my fingers and reboot to see if the volume comes up properly on startup. However ftp3 (/dev/da3s1h) comes up 'referenced' and causes problems. Mounting root from ufs:/dev/da0s1a dumpon: crash dumps to /dev/da1s1b (13, 131081) vinum: loaded vinum: reading configuration from /dev/ad1s1h vinum: ftp.p0.s2 is crashed vinum: ftp.p0 is corrupt vinum: updating configuration from /dev/ad0s1h vinum: updating configuration from /dev/da1s1h vinum: updating configuration from /dev/da0s1h vinum: /dev is mounted read-only, not rebuilding /dev/vinum Warning: defective objects D ftp3 State: referenced Device Avail: 0/0 MB P ftp.p0 C State: corrupt Subdisks: 3 Size:260 GB S ftp.p0.s2 State: crashed PO: 149 GB Size:111 GB swapon: adding /dev/da1s1b as swap device Automatic boot in progress... /dev/da0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/da0s1a: clean, 100130 free (938 frags, 12399 blocks, 0.6% fragmentation) /dev/vinum/ftp: CANNOT READ: BLK 546979872 /dev/vinum/ftp: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. /dev/vinum/ftp: CANNOT WRITE: BLK 2800 /dev/vinum/ftp: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. /dev/vinum/usr: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/vinum/usr: clean, 11205903 free (152463 frags, 1381680 blocks, 0.9% fragmentation) THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: /dev/vinum/ftp (/ftp) File system preen failed, trying fsck -y . . . ** /dev/da0s1a ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 2053 files, 51045 used, 100130 free (938 frags, 12399 blocks, 0.6% fragmentation) ** /dev/vinum/usr ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Che
Re: how to remote update 4.10 -> 5.3?
Remember, a remote install is possible (although I've never done it) by connecting a null modem cable between two machines' serial ports and using that for a console - Some people keep remote systems daisy-chained in this manner to cope with boot failures. On Wed, 29 Dec 2004 16:38:23 -0500, Paul Mather <[EMAIL PROTECTED]> wrote: > Palle Girgensohn wrote: > > > I've tried the UPDATING instructions, both locally and remotely (the > > latter failed ;-). But really, everything has to be reinstalled, ports > > and the lot, so a new install is probably the best way... > > > > That's not so bad. A reinstall means you can newfs your partitions as > UFS2 filesystems, which wouldn't be the case if you upgraded 4.10 in-place. > > Cheers, > > Paul. > -- > > e-mail: [EMAIL PROTECTED] > > "Without music to decorate it, time is just a bunch of boring production > deadlines or dates by which bills must be paid." > --- Frank Vincent Zappa > > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Memory handling problem with FreeBSD 5.3?
Christian R. wrote: I have installed FreeBSD 5.3-STABLE i386 on a new Dell PowerEdge 2850, but it crashes under load like "make buildworld" with a "panic: page fault". The server has following configuration: 2x Intel Xeon 3.4 GHz (800 MHz FSB), 6x 1 GB DDR2 ECC RAM and Perc 4e/Di (LSI Logic/amr driver). After some days working on the problem, I think there is some problem with handling the memory. The only way I have got the server to become stable was by switching a special option in the Dell BIOS, which limits the system memory to 256 MB. I have tried to limit the memory to 4 GB by activating a spare memory bank, but the server still crashes. Disabling HTT in BIOS and ACPI in the loader also didn't solved the problem. The kernel is compiled with SMP of course and PAE because of >4 GB memory. I have removed all the unnecessary devices. Dells own diagnostic tool couldn't find any hardware errors. The special memory test also passed all tests. I have also tried with memtest (http://www.memtest.org/) which either could find any memory errors. Has anyone an idea to a solution? Has anyone succeeded running FreeBSD 5.3 on similar hardware? Would it maybe be better to run the AMD64 version of FreeBSD 5.3? I think the i386 version should be more stable? Upgrade to 5-STABLE. I fixed these problems a few weeks ago. Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
clock running fast
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Salutations -- I have an old board with an installation of STABLE whose time keeps running away. ntpd is not helping. I can manually set the time using ntpdate, and my ntpq queries look fine, yet the clock persists in running very fast (seems to be about 1.5x speed). The BIOS clock remains correct, and the machine therefore has the correct time at each reboot, but quickly runs away. Data points: - - I have set kern.timecounter.hardware=TSC, and this has not helped. - - Two other hosts on the same network, using the same ntp server, do not have this problem. - - This box did not display this behavior under FreeBSD 5.2. - - I have replaced the board on the problem box (with the same age and type), and the problem persists. - - dmesg for this machine, an old Dell Optiplex 590, is below. What other information might help diagnose the problem? Thank you ... -d - -- David Talkington [EMAIL PROTECTED] Copyright (c) 1992-2004 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.3-STABLE #0: Sat Dec 25 18:55:20 PST 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/CERBERUS WARNING: debug.mpsafenet forced to 0 as ipsec requires Giant WARNING: MPSAFE network stack disabled, expect reduced performance. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium/P54C (85.52-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x1bf real memory = 67108864 (64 MB) avail memory = 56074240 (53 MB) Intel Pentium detected, installing workaround for F00F bug npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcib0: pcibus 0 on motherboard pci0: on pcib0 isab0: at device 2.0 on pci0 isa0: on isab0 pci0: at device 11.0 (no driver attached) atapci0: irq 14 at device 12.0 on pci0 ata2: channel #0 on atapci0 device_attach: ata2 attach returned 6 cpu0 on motherboard orm0: at iomem 0xc-0xc7fff on isa0 pmtimer0 on isa0 ep0: <3Com 3C509-TP EtherLink III> at port 0x220-0x22f irq 11 on isa0 ep0: Ethernet address: 00:20:af:06:9e:35 ep0: [GIANT-LOCKED] ep1: <3Com 3C509-TP EtherLink III> at port 0x300-0x30f irq 10 on isa0 ep1: Ethernet address: 00:20:af:08:7a:c2 ep1: [GIANT-LOCKED] ep2: <3Com 3C509-TP EtherLink III> at port 0x210-0x21f irq 5 on isa0 ep2: Ethernet address: 00:20:af:ec:c4:c6 ep2: [GIANT-LOCKED] ata0 at port 0x3f6,0x1f0-0x1f7 irq 14 on isa0 ata1 at port 0x376,0x170-0x177 irq 15 on isa0 atkbdc0: at port 0x64,0x60 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] fdc0: at port 0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: [FAST] fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ppc0: parallel port not found. sc0: at flags 0x100 on isa0 sc0: VGA (mono) <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio1: port may not be enabled vga0: at port 0x3b0-0x3cf iomem 0xa-0xb on isa0 unknown: can't assign resources (port) unknown: can't assign resources (port) ppc1: parallel port not found. unknown: can't assign resources (port) Timecounter "TSC" frequency 85517886 Hz quality 800 Timecounters tick every 10.000 msec IPsec: Initialized Security Association Processing. IP Filter: v3.4.35 initialized. Default = pass all, Logging = disabled ipfw2 initialized, divert enabled, rule-based forwarding disabled, default to deny, logging unlimited ad0: 515MB [1048/16/63] at ata0-master PIO3 Mounting root from ufs:/dev/ad0s1a -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFB03Jp5FKhdwBLj4sRAhvDAKCIs0YHcnzxN8AkS90Wr+dp7Euu7wCgnQEP kHY+K7GXuxL+w/cIY9hFGbc= =YaTo -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: -stable, uhci and the iRiver H320.
John Wilson wrote: Hello, all. Hi, I am now looking into purchasing an iRiver H320 player. There was not a lot of information turning up on Google in regard to people being successful, or not, with this device under either Linux or FreeBSD, so I am now turning to this list in hopes of finding a firsthand experience with this device under FreeBSD. If anyone can indeed confirm proper function under FreeBSD, it would be most appreciated. I have an iRiver H340 and it works well under Linux (USB 2.0). Under FreeBSD, umass(4) has some issues and the player doesn't work currently (tested with FreeBSD 5-STABLE and 6-CURRENT) but I'm sure it's just a matter of time :-) Jean-Seb signature.asc Description: OpenPGP digital signature
AW: how to remote update 4.10 -> 5.3?
i managed to update remote server by sending a prepared harddisk which was mounted by a local technical staff. after the system boots you can mount the old partitions and move them to the new harddisk. Then partition the old harddisks, newfs with ufs2 and move the data back in place. This works very well. after everything is done the sent harddisk can be removed and the system work with the original hardware. Everything else then a fresh install and formating with ufs2 looks like to make no sence. -- Best regards / Mit freundlichen Gruessen, Karl M. Joch -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Palle Girgensohn Gesendet: Mittwoch, 29. Dezember 2004 21:31 An: [EMAIL PROTECTED] Betreff: how to remote update 4.10 -> 5.3? Hi! Has anyone managed to update a 4.10 system to 5.3 remotely, i.e. without console access, and without spare disk partitions? I have a bunch of 4.10 machines that are too far away for me to actually do the update hands on. I've tried it on a test machine, it fails half way through installworld, and really needs single user mode to succeed. The install procedure fails since it starts using the newly installed stuff, things like sh(1) and test(1), and they cannot find their libc.so.5, I guess... One idea I have is copying / and /usr to some other place and set ldconfig and PATH=some/other/place and when building and installing. Haven't tried it yet, thought I'd hear anyone on this list has a better suggestion? Optimally, there would a couple of gigs on a separate spare disk partition so I could just install everything there and use it upon reboot. Problem is, there is no such space. :( Thanks Palle ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: -stable, uhci and the iRiver H320.
On Thu, 30 Dec 2004, [ISO-8859-1] Jean-S?bastien P?dron wrote: > > I am now looking into purchasing an iRiver H320 player. There was not a lot > > of information turning up on Google in regard to people being successful, or > > not, with this device under either Linux or FreeBSD, so I am now turning to > > this list in hopes of finding a firsthand experience with this device under > > FreeBSD. > > > > If anyone can indeed confirm proper function under FreeBSD, it would be most > > appreciated. > > I have an iRiver H340 and it works well under Linux (USB 2.0). Under > FreeBSD, umass(4) has some issues and the player doesn't work currently > (tested with FreeBSD 5-STABLE and 6-CURRENT) but I'm sure it's just a > matter of time :-) Works for me ;) [EMAIL PROTECTED]:~$ uname -a FreeBSD hellbell.local 5.3-STABLE FreeBSD 5.3-STABLE #0: Thu Nov 25 13:52:49 MSK 2004 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/HELLBELL i386 uhci0: port 0xd800-0xd81f irq 9 at device 29.0 on pci0 uhci0: [GIANT-LOCKED] usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd000-0xd01f irq 11 at device 29.1 on pci0 uhci1: [GIANT-LOCKED] usb1: on uhci1 usb1: USB revision 1.0 uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhci2: port 0xd400-0xd41f irq 11 at device 29.2 on pci0 uhci2: [GIANT-LOCKED] usb2: on uhci2 usb2: USB revision 1.0 uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub2: 2 ports with 2 removable, self powered ehci0: mem 0xdc00-0xdc0003ff irq 11 at device 29.7 on pci0 ehci0: [GIANT-LOCKED] ehci_pci_attach: companion usb0 ehci_pci_attach: companion usb1 ehci_pci_attach: companion usb2 usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: on ehci0 usb3: USB revision 2.0 uhub3: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1 uhub3: 6 ports with 6 removable, self powered Attach player: dmesg: ehci_idone: need toggle update status=80028d40 nstatus=80008c80 umass0: iRiver iRiver H300 Series, rev 2.00/1.00, addr 2 ehci_idone: need toggle update status=80028d40 nstatus=80008c80 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 38147MB (78126048 512 byte sectors: 255H 63S/T 4863C) [EMAIL PROTECTED]:~$ dd if=/dev/da0s1 of=/dev/null bs=1024k count=16 16+0 records in 16+0 records out 16777216 bytes transferred in 2.167703 secs (7739629 bytes/sec) [EMAIL PROTECTED]:~$ less /sys/i386/conf/HELLBELL # USB support device uhci# UHCI PCI->USB interface device ohci# OHCI PCI->USB interface device ehci device usb # USB Bus (required) #device udbp# USB Double Bulk Pipe devices device ugen# Generic device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse *** WBR, Alexey Zakirov ([EMAIL PROTECTED]) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
