XFree86 ports / Font problem
Hi... after updating my 5.1-current machine: a) new kernel b) new world c) all packages (including XFree86) d) newest gnome-packages (using marcusmerge) i got these msgs in XFree86.0.log Warning: font renderer for .pcf already registered at priority 0 Warning: font renderer for .pcf.Z already registered at priority 0 Warning: font renderer for .pcf.gz already registered at priority 0 Warning: font renderer for .snf already registered at priority 0 Warning: font renderer for .snf.Z already registered at priority 0 Warning: font renderer for .snf.gz already registered at priority 0 Warning: font renderer for .bdf already registered at priority 0 Warning: font renderer for .bdf.Z already registered at priority 0 Warning: font renderer for .bdf.gz already registered at priority 0 Warning: font renderer for .pmf already registered at priority 0 The result is a fontless X... (okay enlightenment has it fonts... but mostly prgs do not... including gdm and all that things) Does anyone know something about this? Jan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CDROM / UDMA problem on -current (2 hours old)
are printed so fast i cant really read but it must be something like that: acd1: WARNING - REQUEST_UDMA (error request) acd1: WARNING - INQUIRE_SENSE (retrying request) Little can be said without complete and accurate error messages, preferrably including a complete kernel backtrace, but still it would be I would give you more info... but as i wrote... thats an endless loop. interesting to know whether the enclosed patch changes anything to your situation. Will try it. Pls give me some mins (~30) /usr/local/bin/cdrecord: Permission denied. Cannot send SCSI cmd via ioctl Check perms on your /dev nodes. cdrecord runs suid root should be enough rights... it's an atapicam problem... That we do not know so far. Recent problems reported by ATAPI/CAM users were mostly ATA and CAM bugs. Please do not make such hasty statements until a complete analysis of the problem has been made. Okay... you're right... shame on me and i try to see more in the depth of the kernel in the future ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CDROM / UDMA problem on -current (2 hours old)
On Mon, 2003-10-06 at 17:23, Thomas Quinot wrote: Le 2003-10-06, Jan Stocker écrivait : I would give you more info... but as i wrote... thats an endless loop. You might be able to interrupt the loop by breaking into DDB with Crtl+Alt+Esc, which then allows you to get a backtrace. Yep, if you've that enabled... my workstation hasn't.. but will have tomorrow you'll get some bt from me. interesting to know whether the enclosed patch changes anything to your situation. Will try it. Pls give me some mins (~30) Okay doesnt help But here some stuff when booting in safe mode (maybe it boots because DMA support for atapi is off, have to check) Oct 6 19:04:53 Twoflower kernel: acd0: CDROM ASUS CD-S500/A at ata1-master PIO4 Oct 6 19:04:53 Twoflower kernel: acd1: CDRW CDRW2224 PLUS at ata1-slave PIO4 Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): Recovered Sense Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): CAM Status: SCSI Status Error Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): SCSI Status: Check Condition Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): ILLEGAL REQUEST asc:24,0 Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): Invalid field in CDB Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): Recovered Sense Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0 Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): CAM Status: SCSI Status Error Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): SCSI Status: Check Condition Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): ILLEGAL REQUEST asc:24,0 Oct 6 19:04:53 Twoflower kernel: (probe2:ata1:0:0:0): Invalid field in CDB Oct 6 19:04:53 Twoflower kernel: GEOM: create disk cd0 dp=0xcbbe4e00 Oct 6 19:04:53 Twoflower kernel: GEOM: create disk cd1 dp=0xcbbe4600 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): Recovered Sense Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): CAM Status: SCSI Status Error Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): SCSI Status: Check Condition Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): NOT READY asc:3a,0 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): Medium not present Oct 6 19:04:53 Twoflower kernel: cd0 at ata1 bus 0 target 0 lun 0 Oct 6 19:04:53 Twoflower kernel: cd0: ASUS CD-S500/A 3.3H Removable CD-ROM SCSI-0 device Oct 6 19:04:53 Twoflower kernel: cd0: 16.000MB/s transfers Oct 6 19:04:53 Twoflower kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Oct 6 19:04:53 Twoflower kernel: (cd1:ata1:0:1:0): Recovered Sense Oct 6 19:04:53 Twoflower kernel: (cd1:ata1:0:1:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Oct 6 19:04:53 Twoflower kernel: (cd1:ata1:0:1:0): CAM Status: SCSI Status Error Oct 6 19:04:53 Twoflower kernel: (cd1:ata1:0:1:0): SCSI Status: Check Condition Oct 6 19:04:53 Twoflower kernel: (cd1:ata1:0:1:0): NOT READY asc:3a,0 Oct 6 19:04:53 Twoflower kernel: (cd1:ata1:0:1:0): Medium not present Oct 6 19:04:53 Twoflower kernel: cd1 at ata1 bus 0 target 1 lun 0 Oct 6 19:04:53 Twoflower kernel: cd1: Traxdata CDRW2224 PLUS 1.4 Removable CD-ROM SCSI-0 device Oct 6 19:04:53 Twoflower kernel: cd1: 16.000MB/s transfers Oct 6 19:04:53 Twoflower kernel: cd1: Attempt to query device size failed: NOT READY, Medium not present Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): Recovered Sense Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): CAM Status: SCSI Status Error Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): SCSI Status: Check Condition Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): NOT READY asc:3a,0 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): Medium not present Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): Recovered Sense Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): CAM Status: SCSI Status Error Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): SCSI Status: Check Condition Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): NOT READY asc:3a,0 Oct 6 19:04:53 Twoflower kernel: (cd0:ata1:0:0:0): Medium not present Oct 6 19:04:54 Twoflower kernel: (cd1:ata1:0:1:0): Recovered Sense Oct 6 19:04:54 Twoflower kernel: (cd1:ata1:0:1:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 Oct 6 19:04:54 Twoflower kernel: (cd1:ata1:0:1:0): CAM Status: SCSI Status Error Oct 6 19:04:54 Twoflower kernel: (cd1:ata1:0:1:0): SCSI Status: Check Condition Oct 6 19:04:54 Twoflower kernel: (cd1:ata1:0:1:0): NOT READY asc:3a,0 Oct 6 19:04:54 Twoflower kernel: (cd1:ata1:0:1:0): Medium not present Oct 6 19
Re: ls -c / ls -u doesn't work anymore
Newest world/kernel same prob [EMAIL PROTECTED]:~ # mkdir x [EMAIL PROTECTED]:~ # cd x [EMAIL PROTECTED]:~/x # touch b-first; sleep 60 [EMAIL PROTECTED]:~/x # touch c-second; sleep 60 [EMAIL PROTECTED]:~/x # touch a-third [EMAIL PROTECTED]:~/x # ls -l -c total 0 -rw-r--r-- 1 jstocker jstocker 0 5 Oct 11:10 a-third -rw-r--r-- 1 jstocker jstocker 0 5 Oct 11:08 b-first -rw-r--r-- 1 jstocker jstocker 0 5 Oct 11:09 c-second looks very alphabetic Jan On Sat, 2003-10-04 at 11:21, Shane Kinney wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I could be wrong, but mine seems to work fine with: FreeBSD kappa.freebsdhackers.net 5.1-CURRENT FreeBSD 5.1-CURRENT #19: Wed Oct 1 15:08:00 CDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KAPPA i386 Try re-building world. Hope that helps. ~Shane IRC: irc.freebsdhackers.net #freebsd PGP: http://www.freebsdhackers.net/pgp On Sat, 4 Oct 2003, Jan Stocker wrote: On my -current ls -c and ls -u produce only alphanumeric output, no sort by date my 4.7 box works fine... FreeBSD Twoflower 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Sep 14 14:17:26 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/Twoflower50 i386 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE/fpE0gsso3QO013ERAokYAKCHerMsaQiSkALws1SGcIHEZYkNeQCgugrD DMmPKrreXL1/1Uup7rfGOOk= =GA6F -END PGP SIGNATURE- -- Jan Stocker [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: CDROM / UDMA problem on -current (2 hours old)
It seems Jan Stocker wrote: That seems right :) I've updates my -current system from Sep, 14th to todays -current (2 hours old). Now i cant boot further than detecting cdrom drives. After testing my second cdrom (cdrw) for its UDMA capabilities the kernel hangs in an endless loop. The output is a repeat from two lines which are printed so fast i cant really read but it must be something like that: acd1: WARNING - REQUEST_UDMA (error request) acd1: WARNING - INQUIRE_SENSE (retrying request) The drive is an 2x2x24x CD/RW from Traxdata which is detected previously as: acd1: CDRW CDRW2224 PLUS at ata1-slave WDMA2 Try a kernel without atapicam ? Yep... it's an atapicam problem... Thomas: Thats the same drive previously does produce the output in cdrecord: /usr/local/bin/cdrecord: Warning: controller returns zero sized Ricoh Vendor Page page. /usr/local/bin/cdrecord: Warning: controller returns wrong size for Ricoh Vendor Page page. /usr/local/bin/cdrecord: Warning: controller returns wrong page 0 for Ricoh Vendor Page page (30). /usr/local/bin/cdrecord: Permission denied. Cannot send SCSI cmd via ioctl ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ls -c / ls -u doesn't work anymore
On Sun, 2003-10-05 at 12:11, Bruce Evans wrote: On Sun, 5 Oct 2003, Jan Stocker wrote: Newest world/kernel same prob [EMAIL PROTECTED]:~ # mkdir x [EMAIL PROTECTED]:~ # cd x [EMAIL PROTECTED]:~/x # touch b-first; sleep 60 [EMAIL PROTECTED]:~/x # touch c-second; sleep 60 [EMAIL PROTECTED]:~/x # touch a-third [EMAIL PROTECTED]:~/x # ls -l -c total 0 -rw-r--r-- 1 jstocker jstocker 0 5 Oct 11:10 a-third -rw-r--r-- 1 jstocker jstocker 0 5 Oct 11:08 b-first -rw-r--r-- 1 jstocker jstocker 0 5 Oct 11:09 c-second looks very alphabetic -c and -u only work when combined with -t. This may be bogus, but it is no different than in 4.4BSD-Lite2 and it is specified by POSIX (POSIX.1-200x-draft7: 21836 -cUse time of last modification of the file status information (see sys/stat.h in the 21837 System Interfaces volume of IEEE Std 1003.1-200x) instead of last modification of 21838 the file itself for sorting (-t) or writing (-l). 21864 -uUse time of last access (see sys/stat.h in the System Interfaces volume of 21865 IEEE Std 1003.1-200x) instead of last modification of the file for sorting (-t) or 21866 writing (-l). The FreeBSD ls clearly attempts to implement this. The FreeBSD man page is clearly a fuzzy version of this: -c Use time when file status was last changed for sorting or print- ing. -u Use time of last access, instead of last modification of the file for sorting (-t) or printing (-l). The FreeBSD man page is missing the critical detail that the status change time and access times are used _instead_ of the modification time. and then -t sorts that date... okay works fine Jan P.S. but the behaviour has changed and i've nowhere read it. my old box: FreeBSD 4.7-RC FreeBSD 4.7-RC #0: Thu Sep 19 01:04:45 MEST 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/ i386 has a working ls -c and does not need ls -t -c. Jan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
ls -c / ls -u doesn't work anymore
On my -current ls -c and ls -u produce only alphanumeric output, no sort by date my 4.7 box works fine... FreeBSD Twoflower 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Sun Sep 14 14:17:26 CEST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/Twoflower50 i386 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
CDROM / UDMA problem on -current (2 hours old)
I've updates my -current system from Sep, 14th to todays -current (2 hours old). Now i cant boot further than detecting cdrom drives. After testing my second cdrom (cdrw) for its UDMA capabilities the kernel hangs in an endless loop. The output is a repeat from two lines which are printed so fast i cant really read but it must be something like that: acd1: WARNING - REQUEST_UDMA (error request) acd1: WARNING - INQUIRE_SENSE (retrying request) The drive is an 2x2x24x CD/RW from Traxdata which is detected previously as: acd1: CDRW CDRW2224 PLUS at ata1-slave WDMA2 Jan P.S: same with / without acpi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
trap 12 while installing -current
On my system -current lived for the last 2 years quite good (ok, not for my last USB probs). I thought it's time to cleanly install my system from root. So i took one of those jpsnap iso images and boot from it. Installing in the same partition (removing old slice, creating new etc). My new fs is UFS2 with soft updates (but without it crashes, too). After about 2% of copying the base files, the kernel panics with trap type 12 code=0. This is reproducable here all the time. Cause i dont know how to get a kernel backtrace while booting from iso image, i took my pencil and paper. Here is the result (without the stack content) from yesterdays -current iso image (but all from the last 4 days looks the same). _mtx_lock_flags + 0x43 vfs_setdirty + 0x79 bdwrite + 0x358 ffs_update + 0x333 ffs_fsync + 0x42f ffs_fsync + 0x1a3 ffs_fsync + 0x16a shed_sync + 0x182 fork_exit + 0xcf fork_trampoline + 0x8 Anyone can fix this ? Jan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usbd does not use detach
On Thu, 2003-08-14 at 16:30, Olivier Cortes wrote: Le Mer 06/08/2003 à 17:55, Jan Stocker a écrit : Does nobody has this problem or does noone use this feature? the problem i see with detach is the utility of the command. but when detaching, the umount part should be done BEFORE detaching, not after. i can't find any good use for the detach hook. most of things should have been done before detaching, and i can't see how to do it without user interactivity, thus avoiding use of the detach hook. Thats another one thats a wrong specification or idea behind it... but here nothing is been called i once included a umount -f in the detach hook. after unplugin' the device, it resulted in a panic. i don't remember if the umount was causing it or if it was right after, when accessing the mount point or repluging the digital recorder. anyway, i learned that umount -f is not meant to be used often... perhaps not on top of usb. for now. But none of this should cause a panic. here this works fine if i doing it by hand... Jan -- Jan Stocker [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
USB connects my DigiCam to 8 devices the same time.....
After attaching my digicam (new kernel without quirks): Aug 13 16:39:50 Twoflower kernel: umass0: MINOLTA DIMAGE 2330 ZOOM DIMAGE2330ZOOM, rev 1.00/1.00, addr 2 Aug 13 16:39:50 Twoflower kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Aug 13 16:39:50 Twoflower kernel: da0: MINOLTA DIMAGE 2330 ZOOM 1.00 Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da0: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da0: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da1 at umass-sim0 bus 0 target 0 lun 1 Aug 13 16:39:50 Twoflower kernel: da1: MINOLTA DIMAGE 2330 ZOOM 1.00 Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da1: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da1: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da2 at umass-sim0 bus 0 target 0 lun 2 Aug 13 16:39:50 Twoflower kernel: da2: MINOLTA DIMAGE 2330 ZOOM 1.00 Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da2: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da2: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da3 at umass-sim0 bus 0 target 0 lun 3 Aug 13 16:39:50 Twoflower kernel: da3: MINOLTA DIMAGE 2330 ZOOM 1.00 Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da3: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da3: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da4 at umass-sim0 bus 0 target 0 lun 4 Aug 13 16:39:50 Twoflower kernel: da4: MINOLTA DIMAGE 2330 ZOOM 1.00 Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da4: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da4: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da5 at umass-sim0 bus 0 target 0 lun 5 Aug 13 16:39:50 Twoflower kernel: da5: MINOLTA DIMAGE 2330 ZOOM 1.00 Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da5: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da5: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da6 at umass-sim0 bus 0 target 0 lun 6 Aug 13 16:39:50 Twoflower kernel: da6: MINOLTA DIMAGE 2330 ZOOM 1.00 Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da6: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da6: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:39:50 Twoflower kernel: da7 at umass-sim0 bus 0 target 0 lun 7 Aug 13 16:39:50 Twoflower kernel: da7: MINOLTA DIMAGE 2330 ZOOM 1.00 Removable Direct Access SCSI-0 device Aug 13 16:39:50 Twoflower kernel: da7: 1.000MB/s transfers Aug 13 16:39:50 Twoflower kernel: da7: 62MB (128001 512 byte sectors: 64H 32S/T 62C) Aug 13 16:40:16 Twoflower kernel: umass0: at uhub0 port 1 (addr 2) disconnected Aug 13 16:40:16 Twoflower kernel: (da0:umass-sim0:0:0:0): lost device Aug 13 16:40:16 Twoflower kernel: (da0:umass-sim0:0:0:0): removing device entry Aug 13 16:40:16 Twoflower kernel: (da1:umass-sim0:0:0:1): lost device Aug 13 16:40:16 Twoflower kernel: (da1:umass-sim0:0:0:1): removing device entry Aug 13 16:40:16 Twoflower kernel: (da2:umass-sim0:0:0:2): lost device Aug 13 16:40:16 Twoflower kernel: (da2:umass-sim0:0:0:2): removing device entry Aug 13 16:40:16 Twoflower kernel: (da3:umass-sim0:0:0:3): lost device Aug 13 16:40:16 Twoflower kernel: (da3:umass-sim0:0:0:3): removing device entry Aug 13 16:40:16 Twoflower kernel: (da4:umass-sim0:0:0:4): lost device Aug 13 16:40:16 Twoflower kernel: (da4:umass-sim0:0:0:4): removing device entry Aug 13 16:40:16 Twoflower kernel: (da5:umass-sim0:0:0:5): lost device Aug 13 16:40:16 Twoflower kernel: (da5:umass-sim0:0:0:5): removing device entry Aug 13 16:40:16 Twoflower kernel: (da6:umass-sim0:0:0:6): lost device Aug 13 16:40:16 Twoflower kernel: (da6:umass-sim0:0:0:6): removing device entry Aug 13 16:40:16 Twoflower kernel: (da7:umass-sim0:0:0:7): lost device Aug 13 16:40:16 Twoflower kernel: (da7:umass-sim0:0:0:7): removing device entry Aug 13 16:40:16 Twoflower kernel: umass0: detached -- -BEGIN GEEK CODE BLOCK- Version: 3.1 GCS d-(+) s-:- a- C+ UB P+++ L- E--- W N+ o-- K? w$ O- M- V- PS PE? Y+ PGP+ t+() 5- X+ R+ tv- b++(+++) DI D--- G- e+++ h-- r++ z+ --END GEEK CODE BLOCK-- ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
usbd does not use detach
Does nobody has this problem or does noone use this feature? Jan On Sat, 2003-08-02 at 14:47, Jan Stocker wrote: Hi, my usbd on -current does not call my script (or any command) given in the detach-value in usbd.conf. This is the output usbd: ucom0 matches ucom0 usbd: Found action 'Palm Handheld Device' for Palm Handheld, Palm, Inc. at ucom0usbd: action 0: Palm Handheld Device vndr=0x0830 prdct=0x0060 devname: ucom0 attach='/usr/sbin/ppp -auto palm' detach='/test.sh' usbd: Setting DEVNAME='ucom0' usbd: Executing '/usr/sbin/ppp -auto palm' Working in auto mode Using interface: tun0 usbd: '/usr/sbin/ppp -auto palm' is ok usbd: processing event queue on /dev/usb usbd: driver-detach event cookie=3217029340 devname=ucom0 USB_EVENT_DRIVER_DETACH P.S. i am tring to get my usb palm working with FreeBSD. The most prefered solution is doing this with a ppp connection and a network sync (all solutions i found in web are not correct but a good advice). Does anyone has a USB palm directly syncing over USB? -- Jan Stocker [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usbd does not use detach
- --- usbd.c.orig Thu Aug 7 18:46:47 2003
+++ usbd.c Thu Aug 7 18:52:33 2003
@@ -911,7 +911,7 @@
break;
case USB_EVENT_DRIVER_ATTACH:
if (verbose)
- - printf(USB_EVENT_DRIVER_DETACH\n);
+ printf(USB_EVENT_DRIVER_ATTACH\n);
break;
case USB_EVENT_DRIVER_DETACH:
if (verbose)
It's here not a second attach output looks like the same:
[EMAIL PROTECTED]:/usr/src/usr.sbin/usbd $ /usr/sbin/usbd -c /etc/usbd.conf
-vvv -d usbd: opened /dev/usb0
usbd: reading configuration file /etc/usbd.conf
usbd: action 1: ActiveWire board, firmware download
vndr=0x0854 prdct=0x0100 rlse=0x
attach='/usr/local/bin/ezdownload -f
/usr/local/share/usb/firmware/0854.0100.0_01.hex ${DEVNAME}'
usbd: action 2: Entrega Serial with UART
vndr=0x1645 prdct=0x8001 rlse=0x0101
attach='/usr/sbin/ezdownload -v -f
/usr/share/usb/firmware/1645.8001.0101 /dev/${DEVNAME}'
usbd: action 3: USB ethernet
devname: [ackr]ue[0-9]+
attach='/etc/pccard_ether ${DEVNAME} start'
detach='/etc/pccard_ether ${DEVNAME} stop'
usbd: action 4: Handspring Visor
vndr=0x082d prdct=0x0100 rlse=0x0100
devname: ugen[0-9]+
attach='/usr/local/bin/coldsync -md -p /dev/${DEVNAME} -t usb'
usbd: action 5: Mouse
devname: ums[0-9]+
attach='/usr/sbin/moused -p /dev/${DEVNAME} -I
/var/run/moused.${DEVNAME}.pid ; /usr/sbin/vidcontrol -m on'
usbd: action 6: Palm Handheld Device
vndr=0x0830 prdct=0x0060
devname: ucom0
attach='/usr/sbin/ppp -auto palm'
detach='/test.sh'
usbd: action 7: USB device
usbd: 7 actions
usbd: opened /dev/usb
usbd: processing event queue on /dev/usb
usbd: driver-attach event cookie=3217029324 devname=ucom0
USB_EVENT_DRIVER_ATTACH
usbd: processing event queue on /dev/usb
usbd: device-attach event at 1060502709.481417000, Palm Handheld, Palm,
Inc.:
vndr=0x0830 prdct=0x0060 rlse=0x0100 clss=0x subclss=0x
prtcl=0x
device names: ucom0
usbd: ucom0 matches ucom0
usbd: Found action 'Palm Handheld Device' for Palm Handheld, Palm, Inc.
at ucom0
usbd: action 0: Palm Handheld Device
vndr=0x0830 prdct=0x0060
devname: ucom0
attach='/usr/sbin/ppp -auto palm'
detach='/test.sh'
usbd: Setting DEVNAME='ucom0'
usbd: Executing '/usr/sbin/ppp -auto palm'
Working in auto mode
Using interface: tun0
Warning: No default entry found in config file.
usbd: '/usr/sbin/ppp -auto palm' is ok
usbd: processing event queue on /dev/usb
usbd: driver-detach event cookie=3217029324 devname=ucom0
USB_EVENT_DRIVER_DETACH
usbd: doing timeout discovery on /dev/usb0
usbd: processing event queue due to timeout on /dev/usb
usbd: doing timeout discovery on /dev/usb0
usbd: processing event queue due to timeout on /dev/usb
usbd: doing timeout discovery on /dev/usb0
usbd: processing event queue due to timeout on /dev/usb
--
Jan Stocker [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
usbd does not use detach
Hi, my usbd on -current does not call my script (or any command) given in the detach-value in usbd.conf. This is the output usbd: ucom0 matches ucom0 usbd: Found action 'Palm Handheld Device' for Palm Handheld, Palm, Inc. at ucom0usbd: action 0: Palm Handheld Device vndr=0x0830 prdct=0x0060 devname: ucom0 attach='/usr/sbin/ppp -auto palm' detach='/test.sh' usbd: Setting DEVNAME='ucom0' usbd: Executing '/usr/sbin/ppp -auto palm' Working in auto mode Using interface: tun0 usbd: '/usr/sbin/ppp -auto palm' is ok usbd: processing event queue on /dev/usb usbd: driver-detach event cookie=3217029340 devname=ucom0 USB_EVENT_DRIVER_DETACH P.S. i am tring to get my usb palm working with FreeBSD. The most prefered solution is doing this with a ppp connection and a network sync (all solutions i found in web are not correct but a good advice). Does anyone has a USB palm directly syncing over USB? -- Jan Stocker [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: our compiler can't convert longlong to float? 5.1-RC1
Another thing with this code.
#include stdio.h
typedef long long longlong;
main()
{
longlong ll=1;
float f;
FILE *file=fopen(conftestval, w);
f = (float) ll;
fprintf(file,%g\n,f);
close(file);
I think this has to be fclose
exit (0);
}
--
Jan Stocker [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nvidia.ko load failed on -current
Jan Stocker wrote: Before blaming me, i know it is not supported for 5.x or -current, but i think some of us have that stuff already running on -current. I've been in hospital for many weeks and now i updated my system (late November) to the currents current. After adding the missing include, i successfully compiled the nvidia driver but loading the kernel module leads to: Feb 24 08:17:08 Twoflower kernel: link_elf: symbol rman_get_start undefined... IIRC I had this same problem when I tried the new scheduler (SCHED_ULE) because (for some reason I don't understand) the linux.ko kernel module was not built when I compiled my kernel. When I went back to the old scheduler (SCHED_4BSD) the linux.ko module reappeared and all worked again -- except that you'll get a 'page fault while in kernel mode' when you shut down the X server. I didn't try actually compiling linux into the kernel with the new scheduler -- you might try that first if you want to run the new scheduler My system has never seen the ULE scheduler, so there must be another thing... -- Jan Stocker [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
nvidia.ko load failed on -current
Before blaming me, i know it is not supported for 5.x or -current, but i think some of us have that stuff already running on -current. I've been in hospital for many weeks and now i updated my system (late November) to the currents current. After adding the missing include, i successfully compiled the nvidia driver but loading the kernel module leads to: Feb 24 08:17:08 Twoflower kernel: link_elf: symbol rman_get_start undefined Feb 24 08:17:08 Twoflower kernel: KLD file nvidia.ko - could not finalize loading Anyone an idea? Jan -- Jan Stocker [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
NVIDIA and GeForce DDR
My problems with the nvidia driver starts at early time, acpi disabled, bios pnp support to no, a kernel without optimisations and architecture specific stuff... no INVARIANT things The driver will not be activated... so X is far far away... Dec 1 14:24:04 Twoflower kernel: nvidia0: GeForce DDR mem 0xd800-0xdfff,0xd600-0xd6ff irq 11 at device 0.0 on pci1 Dec 1 14:24:04 Twoflower kernel: nvidia0: Unable to allocate NVIDIA memory resource. Dec 1 14:24:04 Twoflower kernel: device_probe_and_attach: nvidia0 attach returned 6 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ports/sysutils/bubblemon-dockapp fix
You should make a diff and create a PR with send-pr(1)... http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html may be a help. $ cd /usr/ports $ cp x/y x/y.orig make your changes in x/y $ diff -urN x/y.orig x/y $ send-pr On Sun, 2002-12-08 at 15:14, Vasyl S. Smirnov wrote: Hi, Today I was trying to install bubblemon-dockapp from ports/sysutils, and it failed to compile. I've made a small change in a source file (one #include was missing), and have built it successfully. My system was rebuilt on Dec 7 (5.0-RC), and ports cvsuped on Dec 6. Could somebody please tell me what to do to make this change go to the ports tree? sv -- Jan Stocker [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Kernel broken
CVSuped (2 mins ago) -current kernel is broken: cc1: warnings being treated as errors /usr/src/sys/dev/sound/isa/ad1816.c: In function `ad1816_lock': /usr/src/sys/dev/sound/isa/ad1816.c:81: warning: dereferencing `void *' pointer /usr/src/sys/dev/sound/isa/ad1816.c:81: request for member `mtx_lock' in something not a structure or union /usr/src/sys/dev/sound/isa/ad1816.c: In function `ad1816_unlock': /usr/src/sys/dev/sound/isa/ad1816.c:87: warning: dereferencing `void *' pointer /usr/src/sys/dev/sound/isa/ad1816.c:87: request for member `mtx_lock' in something not a structure or union Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: cvs commit: src/sys/dev/sound/pcm buffer.c channel.c feeder.c feeder_fmt.c feeder_rate.c sndstat.c sound.c sound.h vchan.c
First: sorry for sending same error i'ven't seen this thread I've the same prob on a freshly installed system with /usr/src only from CVS repository and /usr/obj clean (It is a minimum installed -current from a 2 days onld snapshot CD). Jan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Ray Kohler Sent: Tuesday, November 26, 2002 1:01 PM To: cameron grant Cc: [EMAIL PROTECTED] Subject: Re: cvs commit: src/sys/dev/sound/pcm buffer.c channel.c feeder.c feeder_fmt.c feeder_rate.c sndstat.c sound.c sound.h vchan.c On Tue, Nov 26, 2002 at 06:19:41AM +, cameron grant wrote: I have no idea why, but this commit broke kernel building: cc -c -O -pipe -mcpu=athlon -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/dev -I/usr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common -mno-align-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/dev/sound/isa/ad1816.c cc1: warnings being treated as errors /usr/src/sys/dev/sound/isa/ad1816.c: In function `ad1816_lock': /usr/src/sys/dev/sound/isa/ad1816.c:81: warning: dereferencing `void *' pointer /usr/src/sys/dev/sound/isa/ad1816.c:81: request for member `mtx_lock' in something not a structure or union /usr/src/sys/dev/sound/isa/ad1816.c: In function `ad1816_unlock': /usr/src/sys/dev/sound/isa/ad1816.c:87: warning: dereferencing `void *' pointer /usr/src/sys/dev/sound/isa/ad1816.c:87: request for member `mtx_lock' in something not a structure or union *** Error code 1 And the same result for other consumers of snd_mtx* . i'm unable to reproduce this. have you tried a clean build? It was a clean build, done by make buildkernel immediately after make buildworld. SOP. FWIW, I can't even figure out why this doesn't compile, everything looks fine to me and the errors make no sense at all. The only thing I can think to do is blow away /usr/src and get a new one, see if anything changes. -- Ray Kohler [EMAIL PROTECTED] It has been said that man is a rational animal. All my life I have been searching for evidence which could support this. -- Bertrand Russell To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: cvs commit: src/sys/dev/sound/pcm buffer.c channel.c feeder.c feeder_fmt.c feeder_rate.c sndstat.c sound.c sound.h vchan.c
Okay here a detailed description... a) Install a minumum -current from snapshot CD (2 days old). b) Add a cvsup-package without gui (i made before with pkg_create -b blah). c) Get -current fom cvs repo (with cvsup...). d) cd /usr/src make buildworld (works fine) e) copying my kernel-conf. f) make KERNCONF=x buildkernel Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WIne freezes -current for half a year
It'd probably be a good idea to try it again before reporting it as if it were still not working. It may or may not have been fixed by the signal and FP register state commits, etc., so just because it was broken doesn't mean it's broken now. Even if it *is* still broken, it could be broken in an entirely different way... 8-). It is broken with the same symtoms for the last months. a) FreeBSD freezes... you've to do a cold start, no keys or anything work b) FreeBSD reboots after a few secs of doing nothin' c) wine / wineserver process hangs in the background, doing nothing, consuming cpu time and cant be killed by kill -9 . My system is from 26. October. Not new enough? Tonight .i'll get the newest one and recompile the newest wine and tomorrow (8.00 CET) you'll get a dmesg / uname -a /sysctl -a for my system, i'm sure with a non-working wine. Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WIne freezes -current for half a year
On Mon, 2002-11-04 at 22:00, Jan Stocker wrote: It'd probably be a good idea to try it again before reporting it as if it were still not working. It may or may not have been fixed by the signal and FP register state commits, etc., so just because it was broken doesn't mean it's broken now. Even if it *is* still broken, it could be broken in an entirely different way... 8-). It is broken with the same symtoms for the last months. a) FreeBSD freezes... you've to do a cold start, no keys or anything work b) FreeBSD reboots after a few secs of doing nothin' c) wine / wineserver process hangs in the background, doing nothing, consuming cpu time and cant be killed by kill -9 . My system is from 26. October. Not new enough? Tonight .i'll get the newest one and recompile the newest wine and tomorrow (8.00 CET) you'll get a dmesg / uname -a /sysctl -a for my system, i'm sure with a non-working wine. We've a compile problem for wine, which should be fixed first before we con continue this thread Jan FYI: text_i386.o context_i386.c context_i386.c: In function `get_thread_context': context_i386.c:376: structure has no member named `dr0' context_i386.c:377: structure has no member named `dr1' context_i386.c:378: structure has no member named `dr2' context_i386.c:379: structure has no member named `dr3' context_i386.c:380: structure has no member named `dr6' context_i386.c:381: structure has no member named `dr7' context_i386.c: In function `set_thread_context': context_i386.c:440: structure has no member named `dr0' context_i386.c:441: structure has no member named `dr1' context_i386.c:442: structure has no member named `dr2' context_i386.c:443: structure has no member named `dr3' context_i386.c:444: structure has no member named `dr4' context_i386.c:445: structure has no member named `dr5' context_i386.c:446: structure has no member named `dr6' context_i386.c:447: structure has no member named `dr7' gmake[1]: *** [context_i386.o] Error 1 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: WIne freezes -current for half a year
We've a compile problem for wine, which should be fixed first before we con continue this thread Jan FYI: text_i386.o context_i386.c context_i386.c: In function `get_thread_context': context_i386.c:376: structure has no member named `dr0' context_i386.c:377: structure has no member named `dr1' context_i386.c:378: structure has no member named `dr2' context_i386.c:379: structure has no member named `dr3' context_i386.c:380: structure has no member named `dr6' context_i386.c:381: structure has no member named `dr7' context_i386.c: In function `set_thread_context': context_i386.c:440: structure has no member named `dr0' context_i386.c:441: structure has no member named `dr1' context_i386.c:442: structure has no member named `dr2' context_i386.c:443: structure has no member named `dr3' context_i386.c:444: structure has no member named `dr4' context_i386.c:445: structure has no member named `dr5' context_i386.c:446: structure has no member named `dr6' context_i386.c:447: structure has no member named `dr7' gmake[1]: *** [context_i386.o] Error 1 Custom patch using something like (from machine/reg.h) #define DBREG_DRX(d,x) (d-dr[(x)]) /* reference dr0 - dr7 by register number */ has disappeared. Will fix and send a pr tonight. Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
WIne freezes -current for half a year
Hi wine freezes my system (always -current) for months (half a year i think). Does anyone have the same prob and/or a solution? Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ASUS/P3BF: _SB_.LNKB - AE_BAD_DATA
What does this mean? acpi0: ASUS P3B_Fon motherboard acpi0: power button is handled as a fixed feature programming model. Timecounter ACPI-safe frequency 3579545 Hz can't fetch resources for \\_SB_.LNKB - AE_BAD_DATA acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 acpi_cpu0: CPU on acpi0 acpi_button0: Power Button on acpi0 acpi_pcib0: Host-PCI bridge port 0xcf8-0xcff on acpi0 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: SCSI emulation in FreeBSD
Anybody have any idea what I need and where I can find it? http://www.cuivre.fr.eu.org/~thomas/atapicam/ Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
CDROM failure
I replaced my old 486/66 with a P1/133 and some new devices... FreeBSD has a problem with my CD_ROM (alone as master on secondary ata), but it was working quite fine and fast under NT (which the previous owner had installed and i tested the system on). Jun 25 08:15:13 DSLRouter /kernel: acd0: MODE_SENSE_BIG command timeout - resetting Jun 25 08:15:13 DSLRouter /kernel: ata1: resetting devices .. done Jun 25 08:15:13 DSLRouter /kernel: acd0: read data overrun 29/5 Jun 25 08:15:14 DSLRouter /kernel: acd0: MODE_SENSE_BIG command timeout - resetting Jun 25 08:15:14 DSLRouter /kernel: ata1: resetting devices .. done Jun 25 08:15:14 DSLRouter /kernel: acd0: read data overrun 29/0 Jun 25 08:15:14 DSLRouter /kernel: acd0: CDROM CD-ROM CDR-S1G at ata1-master PIO0 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Floppy only 8.3 filenames
Hi, i am sure on my old 4.x system i was able to mount my floppy-disc and can use long filenames, but on my -current mount -t msdos /dev/fd0 /mnt leads to 8.3 lowercase and mount -t msdos /dev/fd0c /mnt the first time to 8.3 uppercase and the following to 8.3 lowercase... Does my mind playing with me??? Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Floppy only 8.3 filenames
/dev/ad0s1 /dosmsdos rw 0 0 looks quite longfilenamed on my FAT32 slice since ages... On Sat, 2002-06-22 at 22:48, Peter Hessler wrote: MS-DOS can only handle 8.3 file names. It's by design (MS not FreeBSD). /snip/ mount -t msdos /dev/fd0 /mnt /snip/ -- Peter Hessler [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Floppy only 8.3 filenames
This really helps and further mounts without the option will mount the floppy with longnames, but i am sure i never used such an option. Thanx Jan On Sat, 2002-06-22 at 23:07, Brian K. White wrote: - Original Message - From: Jan Stocker [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Saturday, June 22, 2002 4:50 PM Subject: Re: Floppy only 8.3 filenames /dev/ad0s1 /dosmsdos rw 0 0 looks quite longfilenamed on my FAT32 slice since ages... On Sat, 2002-06-22 at 22:48, Peter Hessler wrote: MS-DOS can only handle 8.3 file names. It's by design (MS not FreeBSD). /snip/ mount -t msdos /dev/fd0 /mnt /snip/ -- Peter Hessler [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message ugh top-posting... perhaps try forcing it with -o longnames ? Brian K. White -- [EMAIL PROTECTED] -- http://www.aljex.com/bkw/ +[+++[-]-]+..+.+++.-.[+---]++. filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: C++ troubles continue
Do you have cleaned your /usr/include/g++ directory from old gcc files? Jan On Wed, 2002-06-19 at 04:12, Charlie Root wrote: Trying to build kdebase3 on the FreeBSD 5.0-CURRENT #7: Mon Jun 17 22:46:16 EDT 2002 [...] gmake[4]: Nothing to be done for `all-am'. gmake[4]: Leaving directory `/ccd/ports/x11/kdebase3/work/kdebase-3.0.1/kappfinder/apps' gmake[3]: Leaving directory `/ccd/ports/x11/kdebase3/work/kdebase-3.0.1/kappfinder/apps' gmake[3]: Entering directory `/ccd/ports/x11/kdebase3/work/kdebase-3.0.1/kappfinder' /bin/sh ../libtool --mode=link --tag=CXX c++ -DNDEBUG -DNO_DEBUG -O2 -O -march=i686 -pipe -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT -DQT_NO_ASCII_CAST-o kappfinder -L/opt/lib -pthread -L/opt/lib -R /opt/lib -R /opt/lib -R /opt/lib -R /opt/lib main.o scanner.o checker.o kappfinder_meta_unload.o -lkdeui c++ -DNDEBUG -DNO_DEBUG -O2 -O -march=i686 -pipe -fno-exceptions -fno-check-new -DQT_CLEAN_NAMESPACE -DQT_NO_COMPAT -DQT_NO_ASCII_CAST -o kappfinder -pthread main.o scanner.o checker.o kappfinder_meta_unload.o -L/opt/lib /opt/lib/libkdeui.so /opt/lib/libkdecore.so -L/usr/lib /opt/lib/libDCOP.so /opt/lib/libkdefx.so -lqt-mt -lpng -lz -lXext -lX11 -lSM -lICE -lXrender -lstdc++ -lm -lgcc -Wl,--rpath -Wl,/opt/lib -Wl,--rpath -Wl,/opt/lib checker.o: In function `checkDesktopFile(QString const, QString)': checker.o(.text+0x536): undefined reference to `cout' checker.o(.text+0x543): undefined reference to `ostream::operator(char const*)' checker.o(.text+0x575): undefined reference to `ostream::operator(char const*)' checker.o(.text+0x585): undefined reference to `ostream::operator(char const*)' checker.o(.text+0x6f1): undefined reference to `cout' checker.o(.text+0x6fe): undefined reference to `ostream::operator(char const*)' checker.o(.text+0x706): undefined reference to `endl(ostream)' checker.o(.text+0x7e1): undefined reference to `cout' checker.o(.text+0x7ea): undefined reference to `ostream::operator(char const*)' checker.o(.text+0x7f2): undefined reference to `endl(ostream)' gmake[3]: *** [kappfinder] Error 1 gmake[3]: Leaving directory `/ccd/ports/x11/kdebase3/work/kdebase-3.0.1/kappfinder' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/ccd/ports/x11/kdebase3/work/kdebase-3.0.1/kappfinder' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/ccd/ports/x11/kdebase3/work/kdebase-3.0.1' gmake: *** [all] Error 2 *** Error code 2 Any clues? The /usr/lib/libstdc++.a has, for example: W std::basic_ostreamchar, std::char_traitschar std::endlchar, std::char_traitschar (std::basic_ostreamchar, std::char_traitschar ) B std::cout B std::buf_cout U std::cout U std::buf_cout -mi To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: pcm / mic
A Creative Soundblaster PCI64 (Ensoniq Audio PCI)... $cat /dev/sndstat FreeBSD Audio Driver (newpcm) Installed devices: pcm0: AudioPCI ES1370 at io 0xd000 irq 10 (1p/1r/0v channels duplex default) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Long, Scott Sent: Thursday, April 18, 2002 10:23 PM To: '[EMAIL PROTECTED]'; [EMAIL PROTECTED] Subject: RE: pcm / mic Hi, i cant record from /dev/dsp with the record device 'mic'. Is there support for the microphone input? What sound card are you using? Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
pcm / mic
Hi, i cant record from /dev/dsp with the record device 'mic'. Is there support for the microphone input? Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
weird date/time
Hello, all my X-proggys tell me its about 15:48 (and it's true) my Windows on the same machine told me the same after a reboot. But a date in console will tell: Tue Apr 16 17:49:20 MEST 2002 what the hell is this? And every fs timestamps are also 2 hours in the future. Clock normally set to localtime and German timezone selected. MEST looks quite good: Middle European Sommer Time.. and it is. So MEST is GMT +0200. Maybe someone is adding this time to my localtime Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sometimes make install does nothing
On Wed, 2002-04-17 at 18:15, Alfred Perlstein wrote: * Jan Stocker [EMAIL PROTECTED] [020417 06:33] wrote: Hi, sometime a 'make install' does completely nothing. This leads that dependencies weren't installed or i've to call the make again. Mostly this happens while defining install and clean on the commandline together. Have a look at the following output. The port wasnt installed before (and no work directory exists!) twoflower# make install clean === Cleaning for autoconf213-2.13.000227_1 === Cleaning for m4-1.4_1 === Cleaning for ruby-1.6.7.2002.03.27 === Cleaning for ruby-fnmatch-1.1b_1 twoflower# make install clean === Extracting for ruby-fnmatch-1.1b_1 Checksum OK for ruby/ruby-fnmatch-1.1b.tar.gz. === ruby-fnmatch-1.1b_1 depends on file: /usr/local/bin/ruby - found === Patching for ruby-fnmatch-1.1b_1 === Configuring for ruby-fnmatch-1.1b_1 === Running extconf.rb to configure ... It happens here and there and not all the time, i cant find a common part when or where it happens... Check for a .install_done file in the work dir. I think that's what can cause this. I think the answer is to use reinstall instead of install or to make clean first. As i wrote the port is clean NO WORK DIR, SO NO .install_done ! This happens also with a clean port (no work-dir) with $ make install nothing happens $ make install the make starts... so here cant the maybe (but really not) existing .install_done file disappear. But with clean and install both in one make the problem appears more times. -- -Alfred Perlstein [[EMAIL PROTECTED]] 'Instead of asking why a piece of software is using 1970s technology, start asking why software is ignoring 30 years of accumulated wisdom.' Tax deductible donations for FreeBSD: http://www.freebsdfoundation.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: weird date/time
Problem solved itself... cant say why... after some reboots everything looks fine. On Tue, 2002-04-16 at 19:25, Jan Stocker wrote: Hello, all my X-proggys tell me its about 15:48 (and it's true) my Windows on the same machine told me the same after a reboot. But a date in console will tell: Tue Apr 16 17:49:20 MEST 2002 what the hell is this? And every fs timestamps are also 2 hours in the future. Clock normally set to localtime and German timezone selected. MEST looks quite good: Middle European Sommer Time.. and it is. So MEST is GMT +0200. Maybe someone is adding this time to my localtime Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sometimes make install does nothing
On Wed, 2002-04-17 at 21:14, Kris Kennaway wrote:
On Tue, Apr 16, 2002 at 03:31:06PM +, Jan Stocker wrote:
twoflower# make install clean
Check you
a) don't already have an .install_done cookie in the ${WRKDIR}.
As i wrote: no work dir exists, so no .install_done.
b) have an up-to-date bsd.port.mk
Freshly cvsuped the last time... but it happens always in the last days.
Jan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Mouse in Xfree86 4.2.0
Whats about editing /etc/rc.devfs and inserting a symlink from /dev/mouse to /dev/sysmouse ? On Mon, 2002-04-15 at 08:26, Munish Chopra wrote: On Mon, Apr 15, 2002 at 10:02:33AM +0200, John Angelmo wrote: Hello When I start XFree86 I get the error that /dev/mouse can't be found, OK devfs seems to be installd so MAKEDEV dosn't exist anymore, is there anyway to get /dev/mouse working as in FreeBSD 4? Thanks /John Set your mouse as being /dev/sysmouse in your XF86Config. -- Munish Chopra The FreeBSD NVIDIA Driver Initiative http://nvidia.netexplorer.org To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
boot failure
After a buildworld / buildkernel /installkernel / installworld on my current system from yesterday sources (about 19:00 CET) my system doesnt boot: The kernel and the acpi module will be loaded and then nothing happens for a second, something is accessing the hd and i get a login screen. No hardware detect and nothing else before the login only kernel and acpi loaded. Of course you cant login... you cant input anything :) Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: gcc -O broken in CURRENT
okay... seems we are now out of topic... some arguments for a change some to retain the old custom (and in my opinion bootless stuff). I think later we'll need a survey for this and volunteers to do the work (if we want to do the change)... Alex are you still workin' for a patch? Jan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alexander Kabaev Sent: Thursday, March 14, 2002 5:26 PM To: Martin Blapp Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: gcc -O broken in CURRENT Do you have a patch for this ? I do not fully understand the parts of GCC involved, so I need some time to verify my initial diagnosis and to create a patch. In other words - not yet :) -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: gcc -O broken in CURRENT
2) Bug is in os delivered gcc but not in port gcc. a) port has more or less patches / os gcc has been modified -- Didn't someone told they are the same? b) other options were set at compile time -- Why dont change to the same in the port? Leads it to a broken world? If the only difference is the lost of binary compatibility, i would say, ok... do it now and we'll need to compile or ports... SOme bugs are related to the FreeBSD use of setjmp/longjmp to do exception unwinding rather than using the DWARF primitives. When you change the toolchain, you change the exception unwinding code when you use the ports version. You also introduce incompatabilities with the installed libstdc++ library, which uses the setjmp/longjmp exception unwinding, which will be in conflict with any exception throwing/handling code compiled with the ports compiler that uses the DWARF2 version. The tests that show it working with the ports version do not test anything other than bare-bones operation, without testing code interoperability eith vendor libraries. Does that clear things up for you? A little bit... most of you argumenting about binary incompatibility for -stable. OK... no chance to do it there, its my opinion too. But why not doing it for current and using that most common dwarf unwinding now (for a later ia64 port it should be faster than setjump i think). Okay everything needs a recompile but this -current is current and not a production os. You're right that we need a patch for -stable. But if we take the approach for -current maybe we leave these problems behind us and following the path of the rank and file (using dwarf2) and making profit of their experience versus doing this ourself and creating patches. -Original Message- From: David O'Brien [mailto:[EMAIL PROTECTED]] Sent: Thursday, March 14, 2002 7:16 PM To: Jan Stocker Cc: Alexander Kabaev; Martin Blapp; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: gcc -O broken in CURRENT On Thu, Mar 14, 2002 at 06:36:05PM +0100, Jan Stocker wrote: 2) Bug is in os delivered gcc but not in port gcc. a) port has more or less patches / os gcc has been modified -- Didn't someone told they are the same? Port has less patches. If you look at /usr/src/contrib/gcc/contrib/freebsd.h and /usr/src/contrib/gcc/contrib/i386/freebsd.h you will see how much things have to be modified because we support dual ELF/a.out [still]. This may be changed too for 5.0 shouldnt it? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: gcc -O broken in CURRENT
So now i am a little bit confused... State of the art: 1) Bug is in -stable and -current -- This means possible patches only in -current arent responsible for this behaviour 2) Bug is in os delivered gcc but not in port gcc. a) port has more or less patches / os gcc has been modified -- Didn't someone told they are the same? b) other options were set at compile time -- Why dont change to the same in the port? Leads it to a broken world? If the only difference is the lost of binary compatibility, i would say, ok... do it now and we'll need to compile or ports... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Alexander Kabaev Sent: Thursday, March 14, 2002 5:26 PM To: Martin Blapp Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: gcc -O broken in CURRENT Do you have a patch for this ? I do not fully understand the parts of GCC involved, so I need some time to verify my initial diagnosis and to create a patch. In other words - not yet :) -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: 4.5-5.0 New Bootloader needed
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, March 12, 2002 10:05 PM To: [EMAIL PROTECTED] Subject: 4.5-5.0 kldxref:No such file or directory As an asside, I've noticed in the past when upgrading from 4.0 to 5.0, I've had to forcebly reinstall the loader. I dont know why, but the loader shiped with (at least) 4.4 doesnt seem to like loading 5.0 kernel bits. If i understand the boot procedure right it isnt the the mbr but the boot sector of the partition. For 5.0 the kernel and modules stuff can be found unter /boot not in the root-tree. So after a buildkernel and installkernel none of the boot sectors are overwritten and the old kernel will be loaded. I think this has to be mentioned in the UPDATING text should it? Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Updating 4.5-5.0 forces some ports to fail: old include files
Hi, after updating my fresh installed 4.5 to -current i was unable to compile GDM. After a nice hint the problem was found. In /usr/include are some old files which are no longer used by -current but be found by the configure program of gdm (i think) and so be used. So i think updating an old 4.x system should lead to a removal of no longer used files to avoid this problem. I've moved my old include and made a installworld again. This is the diff: Only in include.old: gmp.h Only in include.old/machine: asnames.h Only in include.old/machine: bus_pio_ind.h Only in include.old/machine: console.h Only in include.old/machine: globaldata.h Only in include.old/machine: globals.h Only in include.old/machine: i4b_isppp.h Only in include.old/machine: if_wavelan_ieee.h Only in include.old/machine: ioctl_fd.h Only in include.old/machine: ipl.h Only in include.old/machine: lock.h Only in include.old/machine: mouse.h Only in include.old/machine: ultrasound.h Only in include.old: msdosfs Only in include.old/net: hostcache.h Only in include.old/net: if_faith.h Only in include.old/netatm: kern_include.h Only in include.old/netinet: in_hostcache.h Only in include.old/nfs: krpc.h Only in include.old/nfs: nfs.h Only in include.old/nfs: nfsdiskless.h Only in include.old/nfs: nfsm_subs.h Only in include.old/nfs: nfsmount.h Only in include.old/nfs: nfsrtt.h Only in include.old/nfs: nfsrvcache.h Only in include.old/nfs: nfsv2.h Only in include.old/nfs: nqnfs.h Only in include.old: ntfs Only in include.old: nwfs Only in include.old/security: _pam_compat.h Only in include.old/security: _pam_macros.h Only in include.old/security: _pam_types.h Only in include.old/security: pam_malloc.h Only in include.old/security: pam_misc.h Only in include.old: skey.h Only in include.old: ss Only in include.old: struct.h Only in include.old/sys: inttypes.h Only in include.old/sys: syscall-hide.h Only in include.old/sys: tprintf.h Only in include.old/sys: wormio.h Only in include.old/ufs: mfs -Original Message- From: Michael J Estes [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 12, 2002 12:13 AM To: [EMAIL PROTECTED] Cc: gnome@FreeBSD. ORG; ports@FreeBSD. ORG Subject: Re: GDM port broken I had the same problem recently and I managed to fix it my removing /usr/include then doing a 'make installworld'. I'm assuming you are on -CURRENT. I think this is related to recent pam changes. Seems there may have been some stale pam related .h files. -Mike Estes On Mon, 2002-03-11 at 14:46, Jan Stocker wrote: Compiling gdm failed on completly fresh installed system... cc -O -pipe -march=pentiumpro -I/usr/X11R6/include -g -Wall -Wpointer-arith -Wmi ssing-prototypes -Wmissing-declarations -o gdmaskpass dmaskpass.o -Wl,-E -L/us r/X11R6/lib -L/usr/local/lib -lintl -lpam -lwrap -lpam -lutil -lutil -lXiner ama gdmaskpass.o: In function `main': /usr/ports/x11/gdm/work/gdm-2.2.5.4/utils/gdmaskpass.c(.data+0x0): undefined ref erence to `misc_conv' gmake[2]: *** [gdmaskpass] Error 1 gmake[2]: Leaving directory `/usr/ports/x11/gdm/work/gdm-2.2.5.4/utils' To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-gnome in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: gcc -O broken in CURRENT
Hello... isn't anyone workin on this prob? Or do i have a leak in my mailbox? Jan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Jan Stocker Sent: Wednesday, March 06, 2002 9:15 AM To: Martin Blapp; [EMAIL PROTECTED] Subject: RE: gcc -O broken in CURRENT This can be reproduced on my system and it may be a big problem. I installed everthing from source with -O set in make.conf and some proggys running fine under 4.4 wont unter -current. Recompiling the proggys without -O dont fix it but maybe it is caused by some libs... Is anyone examining this problem? Jan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Martin Blapp Sent: Monday, March 04, 2002 9:02 PM To: [EMAIL PROTECTED] Subject: gcc -O broken in CURRENT Hi all, Unfortunatly I have a example from the ports, needed by OpenOffice port (work in progress) cd /usr/ports/devel/stlport/ make install cd /usr/ports/devel/stlport/work/STLport-4.5.3/test/eh gmake -f gcc-freebsd.mak [vector] :testing n-size constructor (const) ... 95 try successful [vector] :testing pointer range constructor (const) ... Bus error - core dumped Then remove the three -O from gcc-freebsd.mak and run it again. You will see that all tests are successfully done. [...] [hash_multiset] :testing default constructor (const) ... 2 try successful [hash_multiset] :testing iterator range n-size constructor (const) ... 127 try successful [hash_multiset] :testing copy constructor (const) ... 54 try successful [hash_multiset] :testing assignment operator (weak) ... 53 try successful [...] [string] :testing copy constructor (const) ... 2 try successful [string] :testing assignment operator (weak) ... 1 try successful EH test : Done Martin Martin Blapp, [EMAIL PROTECTED] [EMAIL PROTECTED] -- ImproWare AG, UNIXSP ISP, Zurlindenstrasse 29, 4133 Pratteln, CH Phone: +41 061 826 93 00: +41 61 826 93 01 PGP Fingerprint: B434 53FC C87C FE7B 0A18 B84C 8686 EF22 D300 551E -- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
4-5 REL - 5.0 CUR
I tried to install a new current from a minimal installed 4.5 RELEASE and cvsuped source tree. $ cd /usr/src $ make -DNOPROFILE=true -DNO_WERROR buildworld ... $ make buildkernel KERNCONF=GENERIC ... $ make installkernel KERNCONF=GENERIC ... install -c -o root -g wheel -m 555 vesa.ko /boot/kernel/ === wi install -c -o root -g wheel -m 555 if_wi.ko /boot/kernel/ === xe install -c -o root -g wheel -m 555 if_xe.ko /boot/kernel/ kldxref /boot/kernel kldxref:No such file or directory *** Error code 1 (ignored) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: 4-5 REL - 5.0 CUR
ops of cource copied the hints file too -Original Message- From: Jan Stocker [mailto:[EMAIL PROTECTED]] Sent: Monday, March 11, 2002 12:32 PM To: freebsd-current@FreeBSD. ORG Subject: 4-5 REL - 5.0 CUR I tried to install a new current from a minimal installed 4.5 RELEASE and cvsuped source tree. $ cd /usr/src $ make -DNOPROFILE=true -DNO_WERROR buildworld ... $ make buildkernel KERNCONF=GENERIC ... $ make installkernel KERNCONF=GENERIC ... install -c -o root -g wheel -m 555 vesa.ko /boot/kernel/ === wi install -c -o root -g wheel -m 555 if_wi.ko /boot/kernel/ === xe install -c -o root -g wheel -m 555 if_xe.ko /boot/kernel/ kldxref /boot/kernel kldxref:No such file or directory *** Error code 1 (ignored) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Updated ATAPI/CAM patches
I think Thomas is doing here a quite good job and it is also to him to decide to include his sources and maybe maintain them. The ata sources have changed a lot the last weeks, so until Thomas thinks his sources are under heavy development too, both should do their jobs and we've some patches from Thomas. If you include it now one depends of the other and you may get into the problem of both altering the code from the other at the same time. The (somewhat selfish) behavior to include it and give maintainership to someone else leads to a originator stopping his work or the creation of 2 parallel solutions. Isn't it better the core team (or someone else thinking (s)he's a better idea) supports Thomas and a stable and good solution is integrated later (maybe with maintainership of Thomas)? Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Updated ATAPI/CAM patches
On Thu, 2002-02-28 at 23:15, Julian Elischer wrote: We have CVS Okay.. thats a piece software.. Why not commit the prototype now and update it as people get the corner cases worked out? If Thomas can and will maintain it, ok... else read my comment from my last mail... The code doesn't interfere with either the CAM system or the ATAPI system that I can see. So lately atapi_softc disapperead (o.k. has been renamed). So what to do... is the person who made the change responsible to change the affected code (maybe changing this struct causes something more than find/replace the old name) or do you want to wait for the maintainer to fix it and kernel is broken for this time. So you need a person who really want this, have time and the knowledge to do it. You cant check it in and lets see what happens. Jan On Thu, 28 Feb 2002, Jan Stocker wrote: I think Thomas is doing here a quite good job and it is also to him to decide to include his sources and maybe maintain them. The ata sources have changed a lot the last weeks, so until Thomas thinks his sources are under heavy development too, both should do their jobs and we've some patches from Thomas. If you include it now one depends of the other and you may get into the problem of both altering the code from the other at the same time. The (somewhat selfish) behavior to include it and give maintainership to someone else leads to a originator stopping his work or the creation of 2 parallel solutions. Isn't it better the core team (or someone else thinking (s)he's a better idea) supports Thomas and a stable and good solution is integrated later (maybe with maintainership of Thomas)? Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-scsi in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: HEADS UP: DHCP 3.0.1RC6 imported
I am using isc-dhcp3-3.0.r12 with DDNS on my FreeBSD 4.3 router a long time and have no problem. Shall this msg mean the port is completly integrated in freebsd 5? Jan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Murray Stokely Sent: Tuesday, February 19, 2002 4:07 PM To: [EMAIL PROTECTED] Subject: HEADS UP: DHCP 3.0.1RC6 imported DHCP 3.0.1 RC6 has been imported into -CURRENT. DHCP 3.x provides DHCP failover support, dynamic DNS updates, and much more. http://www.isc.org/products/DHCP/dhcp-prerelease.html I've done testing with some Alpha and i386 machines on my local network, but it's certainly possible that the new DHCP client will behave in unexpected ways in more demanding environments. If you notice any regressions in functionality, please email me. Thanks, - Murray To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Where to put errors for ports only in current?
Hi, where i've to post a error regarding an installed software from ports, which only occurs on current? Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: USB camera
Looks quite fine for me... looks like your cam was connected for about 6 mins... what does a $ mount -t msdos /dev/da0s1 /mnt say? Maybe you should take a look at the partition table with $ fdisk da0 if it tells you something like fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: UNUSED The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 32, size 126944 (61 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 61/ head 63/ sector 32 you should add a quirk for your cam... Jan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Joe Halpin Sent: Thursday, December 27, 2001 11:15 PM To: [EMAIL PROTECTED] Subject: USB camera I'm not able to mount my USB camera. This is what dmesg has to say about my usb port: $ dmesg | grep -i usb uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0xe000-0xe01f irq 11 at device 7.2 on pci0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 bash-2.05$ dmesg | grep -i scsi da0: NIKON NIKON DSC E995 1.00 Removable Direct Access SCSI-2 device da0: NIKON NIKON DSC E995 1.00 Removable Direct Access SCSI-2 device This is what /var/log/messages says when I plug the camera in and turn it on: Dec 27 15:41:01 fbsd /kernel: da0 at umass-sim0 bus 0 target 0 lun 0 Dec 27 15:41:01 fbsd /kernel: da0: NIKON NIKON DSC E995 1.00 Removable Direct Access SCSI-2 device Dec 27 15:41:01 fbsd /kernel: da0: 650KB/s transfers Dec 27 15:41:01 fbsd /kernel: da0: 15MB (31808 512 byte sectors: 64H 32S/T 15C) Dec 27 15:47:13 fbsd /kernel: umass0: at uhub0 port 1 (addr 2) disconnected Dec 27 15:47:13 fbsd /kernel: (da0:umass-sim0:0:0:0): lost device Dec 27 15:47:13 fbsd /kernel: (da0:umass-sim0:0:0:0): removing device entry Dec 27 15:47:13 fbsd /kernel: umass0: detached On my Linux box I just mount the device file and the camera shows up as a filesystem. Is it different in FreeBSD? Thanks Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: USB camera
The s1 after da0s1 is similar for all disc devices under bsd. It means the first slice (similar to partition for Wind**s users). But this is something out of topic here... move to FreeBSD-question or take a private talk with me... Jan On Fri, 2001-12-28 at 17:28, Joe Halpin wrote: Jan Stocker wrote: Looks quite fine for me... looks like your cam was connected for about 6 mins... what does a $ mount -t msdos /dev/da0s1 /mnt say? That works fine. I guess I'm trying to mount the wrong device file. sigh Sorry, I'm pretty new to usb and haven't caught on yet. Is there a document that describes what the device files under /dev are for? I don't see da0s1 in my kernel config file at all. Thanks Joe To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: smbfs support
What is the state of smbfs for current at present? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Kernel broken
Sources from: Dec, 26 11:28 CET linking kernel procfs.o: In function `procfs_init': procfs.o(.text+0x1ac): undefined reference to `pfs_create_link' procfs.o(.text+0x1c0): undefined reference to `pfs_create_dir' procfs.o(.text+0x1db): undefined reference to `pfs_create_file' procfs.o(.text+0x1f4): undefined reference to `pfs_create_file' procfs.o(.text+0x213): undefined reference to `pfs_create_file' procfs.o(.text+0x229): undefined reference to `pfs_create_file' procfs.o(.text+0x248): undefined reference to `pfs_create_file' procfs.o(.text+0x261): more undefined references to `pfs_create_file' follow procfs.o: In function `procfs_init': procfs.o(.text+0x330): undefined reference to `pfs_create_link' procfs.o: In function `_procfs_mount': procfs.o(.text+0x36b): undefined reference to `pfs_mount' procfs.o: In function `_procfs_init': procfs.o(.text+0x385): undefined reference to `pfs_init' procfs.o: In function `_procfs_uninit': procfs.o(.text+0x39d): undefined reference to `pfs_uninit' procfs.o(.data+0x68): undefined reference to `pfs_unmount' procfs.o(.data+0x6c): undefined reference to `pfs_root' procfs.o(.data+0x74): undefined reference to `pfs_statfs' *** Error code 1 Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Kernel broken
Xcuse me...overread it... Jan On Wed, 2001-12-26 at 19:46, Maxime Henrion wrote: Jan Stocker wrote: Sources from: Dec, 26 11:28 CET linking kernel procfs.o: In function `procfs_init': procfs.o(.text+0x1ac): undefined reference to `pfs_create_link' procfs.o(.text+0x1c0): undefined reference to `pfs_create_dir' procfs.o(.text+0x1db): undefined reference to `pfs_create_file' procfs.o(.text+0x1f4): undefined reference to `pfs_create_file' [...] Please read /usr/src/UPDATING : 20011203: The procfs pseudo-filesystem has now been converted to use the pseudofs framework. If you have 'options PROCFS' in your kernel config, you'll need to add 'options PSEUDOFS' if it's not there already. Maxime -- Don't be fooled by cheap finnish imitations ; BSD is the One True Code To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: ntfs fs
Okay, i'll send you a callstack if i am at work again (have now a week holiday). The current kernel wasnt compiled with debug info... Jan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Steve Kargl Sent: Thursday, November 29, 2001 8:18 PM To: [EMAIL PROTECTED] Cc: freebsd-current@FreeBSD. ORG Subject: Re: ntfs fs On Thu, Nov 29, 2001 at 08:03:55PM +0100, Jan Stocker wrote: Hi, after a 'ls -l' on a ntfs mounted partition my system freezes and reboots. A normal 'ls' really runs quite fine... Jan, This message contains very little useful information. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbo ok/kerneldebug.html -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
ntfs fs
Hi, after a 'ls -l' on a ntfs mounted partition my system freezes and reboots. A normal 'ls' really runs quite fine... Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
[Fwd: AMD not existing USB devices]
Hi, i dont know where is the right place for this questions. On my -current FreeBSD system exist a USB device which is not always attached. My amd is configured to automount this device: cam type:=pcfs;dev:=/dev/da0s1;opts:=rw which runs quite fine, if the device is attached at boot time. So i can attach/detach it and it will be mounted/dismounted. But if i havent attached the device at boot time my system hangs at startup from amd. Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
AMD not running
My amd wont run... log says: Nov 14 16:35:04 twoflower amd[758]/fatal: unable to register (AMQ_PROGRAM=300019, AMQ_VERSION, tcp) Nov 14 16:35:04 twoflower amd[758]/info: Finishing with status 3 amd is still running as process but doing nothing... and of course amq isnt doing anything... And some weird stuff also happens, when i try to load nfsclient.ko (this was supposed be a bug in the last months) $ kldload /boot/kernel/nfsclient.ko kldload: can't load /boot/kernel/nfsclient.ko: Exec format error Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: AMD not running
Am Wed, 2001-11-14 um 17.52 schrieb Samuel Tardieu: On 14/11, Jan Stocker wrote: | My amd wont run... log says: | | Nov 14 16:35:04 twoflower amd[758]/fatal: unable to register | (AMQ_PROGRAM=300019, AMQ_VERSION, tcp) | Nov 14 16:35:04 twoflower amd[758]/info: Finishing with status 3 Are you running a portmapper? No... To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
struct thread
FYI: Ive posted an article to comp.emulators.ms-windows.wine about compiling errors for wine. This is caused by an redefinition of struct thread. This is the state at present: From: [EMAIL PROTECTED] (Steven G. Kargl) Subject: Re: Compile errors with FreeBSD 5.0 Newsgroups: comp.emulators.ms-windows.wine In article [EMAIL PROTECTED], Ove Kaaven [EMAIL PROTECTED] writes: Jan Stocker wrote: Hi, the current version of FreeBSD (5.0) has a common header which defines struct thread, so there will be an redefinition and nothing works. I think you shall rename your stuff from thread.h to something like wine_thre to get out of this trouble. I'd rather say that the problem is FreeBSD. System headers should not pollute the namespace of applicatio. The glibc headers take great care to avoid polluting the namespace, but FreeBSD is starting to look like it thinks that it can define any common name, and if there's a collision because of that carelessness, they tell all the apps to rename their symbols, instead of fixing the OS. Can you elaborate? The application is pulling in the system header sys/proc.h where struct thread is defined. If an application purposely pulls in a system header file, how can the system header pollute the namespace of the application when the applications requests the information in that header? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: struct thread
Wine includes sys/user.h which includes sys/proc.h. The configure skript determines the existence, but it isnt really needed to compile Maybe other systems defines here some needful stuff which is included somewhere else in FreeBSD? Jan On Tue, 2001-11-13 at 21:32, Julian Elischer wrote: The trouble is that proc.h is not supposed to be exporting anything to userland.. (with the exception of hacks like 'ps' but they are a special category. It is kernel internal definitions.. Why is wine including it? If there is something in it that is needed by wine then we need to think about why it needs a kernel internal definition, and maybe whether we shouldn't move it somewhere else that IS exported.. On Tue, 13 Nov 2001, Jan Stocker wrote: FYI: Ive posted an article to comp.emulators.ms-windows.wine about compiling errors for wine. This is caused by an redefinition of struct thread. This is the state at present: From: [EMAIL PROTECTED] (Steven G. Kargl) Subject: Re: Compile errors with FreeBSD 5.0 Newsgroups: comp.emulators.ms-windows.wine In article [EMAIL PROTECTED], Ove Kaaven [EMAIL PROTECTED] writes: Jan Stocker wrote: Hi, the current version of FreeBSD (5.0) has a common header which defines struct thread, so there will be an redefinition and nothing works. I think you shall rename your stuff from thread.h to something like wine_thre to get out of this trouble. I'd rather say that the problem is FreeBSD. System headers should not pollute the namespace of applicatio. The glibc headers take great care to avoid polluting the namespace, but FreeBSD is starting to look like it thinks that it can define any common name, and if there's a collision because of that carelessness, they tell all the apps to rename their symbols, instead of fixing the OS. Can you elaborate? The application is pulling in the system header sys/proc.h where struct thread is defined. If an application purposely pulls in a system header file, how can the system header pollute the namespace of the application when the applications requests the information in that header? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: struct thread
No, ive removed the include, and it compiled and runs very good. Jan On Tue, 2001-11-13 at 22:45, Julian Elischer wrote: do they need user.h? On 13 Nov 2001, Jan Stocker wrote: Wine includes sys/user.h which includes sys/proc.h. The configure skript determines the existence, but it isnt really needed to compile Maybe other systems defines here some needful stuff which is included somewhere else in FreeBSD? Jan On Tue, 2001-11-13 at 21:32, Julian Elischer wrote: The trouble is that proc.h is not supposed to be exporting anything to userland.. (with the exception of hacks like 'ps' but they are a special category. It is kernel internal definitions.. Why is wine including it? If there is something in it that is needed by wine then we need to think about why it needs a kernel internal definition, and maybe whether we shouldn't move it somewhere else that IS exported.. On Tue, 13 Nov 2001, Jan Stocker wrote: FYI: Ive posted an article to comp.emulators.ms-windows.wine about compiling errors for wine. This is caused by an redefinition of struct thread. This is the state at present: From: [EMAIL PROTECTED] (Steven G. Kargl) Subject: Re: Compile errors with FreeBSD 5.0 Newsgroups: comp.emulators.ms-windows.wine In article [EMAIL PROTECTED], Ove Kaaven [EMAIL PROTECTED] writes: Jan Stocker wrote: Hi, the current version of FreeBSD (5.0) has a common header which defines struct thread, so there will be an redefinition and nothing works. I think you shall rename your stuff from thread.h to something like wine_thre to get out of this trouble. I'd rather say that the problem is FreeBSD. System headers should not pollute the namespace of applicatio. The glibc headers take great care to avoid polluting the namespace, but FreeBSD is starting to look like it thinks that it can define any common name, and if there's a collision because of that carelessness, they tell all the apps to rename their symbols, instead of fixing the OS. Can you elaborate? The application is pulling in the system header sys/proc.h where struct thread is defined. If an application purposely pulls in a system header file, how can the system header pollute the namespace of the application when the applications requests the information in that header? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
SCSI-IDE
Is there any working thread for doing a SCSI-IDE translation like NetBSD and LINUX has? This is very useful to get proggys like cdrecord (and the GUIs [GnomeToaster]) running on IDE cd writers. Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
WARNING: Driver mistake: destroy_dev on 154/0
Ive updated the first time my system to current (Oct-28, with cvsup). After a make buildword and installworld, i made a new GENERIC kernel and copied the file GENERIC.hints to /boot/device.hints and installed the new kernel. I ve updated all files in /etc and remade all devices. Now a bootup hangs: a) The kernel is loading b) acpi.ko is loading c) Pentium Pro MTRR support enable d) WARNING: Driver mistake: destroy_dev on 154/0 next is a kernel panic dont do that So whats on? Jan To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
