Re: kdm xdm problem
You do not need the wrapper to login via kdm or gdm. What version are you using of gdm? Versions prior to 2 of GDM can be launched from ttys, but the latest versions require (are recommended???) the shell script that is installed to be run. Anthony On Sunday 30 March 2003 05:08, Dane Butler wrote: Hey, my name is Dane. I have been a Linux user for a few years and have been trying out FreeBSD 5.0, but there is a problem. I edited the /etc/ttys file as instructed to make kdm (and xdm) boot, but as soon as i login, x crashes and reboots, how do i get around this? _ Hotmail now available on Australian mobile phones. Go to http://ninemsn.com.au/mobilecentral/hotmail_mobile.asp ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
buildworld problem (source cvsup around 10:00pm march 30)
I'm running FreeBSD 5.0-CURRENT, and just updated my source tree from cvsup10.freebsd.org about 3 hours ago. Upon make buildworld, the make runs fine for about an hour, then spits out: === etc === etc/sendmail make: don't know how to make freebsd.mc. Stop *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Any help/suggestions would be appreciated. Thanks. -John ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: buildworld problem (source cvsup around 10:00pm march 30)
On Mon, Mar 31, 2003 at 01:25:37AM -0800, John Stockdale wrote: I'm running FreeBSD 5.0-CURRENT, and just updated my source tree from cvsup10.freebsd.org about 3 hours ago. Upon make buildworld, the make runs fine for about an hour, then spits out: === etc === etc/sendmail make: don't know how to make freebsd.mc. Stop *** Error code 2 1 error Any help/suggestions would be appreciated. Do you have SENDMAIL_MC in your /etc/make.conf ? -- Rgdz,/\ ASCII RIBBON CAMPAIGN Sergey Osokin aka oZZ, \ /AGAINST HTML MAIL http://ozz.pp.ru/ X AND NEWS / \ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ypserv and sshd not getting along in -current
At 11:59 AM 31/03/03, Glenn Johnson sent this up the stick: On Mon, Mar 31, 2003 at 10:46:07AM +1000, Rob B wrote: At 02:55 PM 29/03/03, Terry Lambert sent this up the stick: man ypbind (-s is the magic incantation). snip Mar 31 10:10:39 erwin ypserv[92]: access to master.passwd.byuid denied -- client 192.168.100.30:49255 not privileged Why would the request be coming from a high port when I have specifically told it to bind to a low port? The answer (work around) is to turn off PrivelegeSeparation in your sshd_config file. That got it, thanks Rob -- Two prostitutes standing on a street corner. One says to the other, Have you ever been picked up by the fuzz? The other replies, No, but I've been swung around by the boobs a few times! This is random quote 1117 of 1254. Distance from the centre of the brewing universe [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian Public Key fingerprint = 6219 33BD A37B 368D 29F5 19FB 945D C4D7 1F66 D9C5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
problem updating from 4.7 Stable do 5.0 Current
Hello all, I have a problem updating one of our servers from 4.7Stable to 5.0Current. It is a Compaq Proliant 7000 Server with 4 Xeons 500Mhz with 2MB L2 cache each. I has a 4200 Compaq Smart Raid Controler with attached 3 U1 Storages. I update the src rebuild the world from updated src to 5.0Current, build a GENERIC kernel and installed it. But after I boot it brokes up during the booting process with the following error: //strip Fatal trap 12: page fault while in kernel mode cpuid=0; lapic.id= 0100 fault virtual address = 0x54 fault code = supervisor read, page not present process eflags = interrupt enabled, resume, IOPL=0 current process = 4(g_down) kernel: type12trap, code=0 Stopped at ida_construct_qcb+0xe3: movzbl 0x54(%eax),%eax //strip It may have some punctual mistakes because it is not a copy/paste. Will appreciate any advices where could be the problem. Best regards, Veno ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem updating from 4.7 Stable do 5.0 Current
Have you installed the world? I don't know if just rebuilding it is sufficient To install the world you have to go to single user mode and run mergemaster to update any changes in configuration files (take a backup of your current files as it overwrites them). Anthony On Monday 31 March 2003 13:15, Ventsislav Velkov wrote: Hello all, I have a problem updating one of our servers from 4.7Stable to 5.0Current. It is a Compaq Proliant 7000 Server with 4 Xeons 500Mhz with 2MB L2 cache each. I has a 4200 Compaq Smart Raid Controler with attached 3 U1 Storages. I update the src rebuild the world from updated src to 5.0Current, build a GENERIC kernel and installed it. But after I boot it brokes up during the booting process with the following error: //strip Fatal trap 12: page fault while in kernel mode cpuid=0; lapic.id= 0100 fault virtual address = 0x54 fault code = supervisor read, page not present process eflags = interrupt enabled, resume, IOPL=0 current process = 4(g_down) kernel: type12trap, code=0 Stopped at ida_construct_qcb+0xe3: movzbl 0x54(%eax),%eax //strip It may have some punctual mistakes because it is not a copy/paste. Will appreciate any advices where could be the problem. Best regards, Veno ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem updating from 4.7 Stable do 5.0 Current
I could not boot in single user mode with the 5.0 kernel because it brokes. Do you mean I should boot in single user with the 4.7 kernel in there installworld and to mergemaster ? regards, Veno - Original Message - From: CARTER Anthony To: [EMAIL PROTECTED] Sent: Monday, March 31, 2003 3:15 PM Subject: Re: problem updating from 4.7 Stable do 5.0 Current Have you installed the world? I don't know if just rebuilding it is sufficient To install the world you have to go to single user mode and run mergemaster to update any changes in configuration files (take a backup of your current files as it overwrites them). Anthony On Monday 31 March 2003 13:15, Ventsislav Velkov wrote: Hello all, I have a problem updating one of our servers from 4.7Stable to 5.0Current. It is a Compaq Proliant 7000 Server with 4 Xeons 500Mhz with 2MB L2 cache each. I has a 4200 Compaq Smart Raid Controler with attached 3 U1 Storages. I update the src rebuild the world from updated src to 5.0Current, build a GENERIC kernel and installed it. But after I boot it brokes up during the booting process with the following error: //strip Fatal trap 12: page fault while in kernel mode cpuid=0; lapic.id= 0100 fault virtual address = 0x54 fault code = supervisor read, page not present process eflags = interrupt enabled, resume, IOPL=0 current process = 4(g_down) kernel: type12trap, code=0 Stopped at ida_construct_qcb+0xe3: movzbl 0x54(%eax),%eax //strip It may have some punctual mistakes because it is not a copy/paste. Will appreciate any advices where could be the problem. Best regards, Veno ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem updating from 4.7 Stable do 5.0 Current
What your server do when it panics? It tries to detect disks? Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Mon, 31 Mar 2003, Ventsislav Velkov wrote: I could not boot in single user mode with the 5.0 kernel because it brokes. Do you mean I should boot in single user with the 4.7 kernel in there installworld and to mergemaster ? regards, Veno - Original Message - From: CARTER Anthony To: [EMAIL PROTECTED] Sent: Monday, March 31, 2003 3:15 PM Subject: Re: problem updating from 4.7 Stable do 5.0 Current Have you installed the world? I don't know if just rebuilding it is sufficient To install the world you have to go to single user mode and run mergemaster to update any changes in configuration files (take a backup of your current files as it overwrites them). Anthony On Monday 31 March 2003 13:15, Ventsislav Velkov wrote: Hello all, I have a problem updating one of our servers from 4.7Stable to 5.0Current. It is a Compaq Proliant 7000 Server with 4 Xeons @500Mhz with 2MB L2 cache each. I has a 4200 Compaq Smart Raid Controler with attached 3 U1 Storages. I update the src rebuild the world from updated src to 5.0Current, build a GENERIC kernel and installed it. But after I boot it brokes up during the booting process with the following error: //strip Fatal trap 12: page fault while in kernel mode cpuid=0; lapic.id= 0100 fault virtual address = 0x54 fault code = supervisor read, page not present process eflags = interrupt enabled, resume, IOPL=0 current process = 4(g_down) kernel: type12trap, code=0 Stopped at ida_construct_qcb+0xe3: movzbl 0x54(%eax),%eax //strip It may have some punctual mistakes because it is not a copy/paste. Will appreciate any advices where could be the problem. Best regards, Veno ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem updating from 4.7 Stable do 5.0 Current
Process:
Boot up normally with 4.7 kernel.
DO THIS:
rm -rf /usr/obj/* (removes compiled files)
rm -rf /tmp/*
Add COMPAT_FREEBSD4 to your kernel configuration file.
make buildworld
make buildkernel KERNCONF=YOURKERNELFILE
cp /usr/src/sys/${MACHINE}/conf/GENERIC.hints /boot/device.hints
(MACHINE = i386, powerpc, ia64 etc depending on architecture. check out the
directory first)
make installkernel KERNCONF=YOURKERNELFILE
#The next line installs the 5.x boot loader.
cd /usr/src/sys/boot; make install
reboot.
Hit a key at boot (other than Enter)
Type: boot -s
This will boot into single user mode with your new kernel.
fsck -p
mount -u /
mount -a
mergemaster -p
rm -rf /usr/include/g++
make installworld
mergemaster
reboot
PLEASE NOTE: Your should REALLY REALLY read the /usr/src/UPDATING file. All
the information given here is taken from that file...You should read that
file to find out if there are any particular entries that are relevent to
your platform. The first few pages are updates to versions of FreeBSD, you
can ignore these really and scroll to the bottom where the upgrade processes
are described.
Good Luck,
Anthony Carter
Yeah.
When booting the computer and it tells you to press Enter to boot or any other
blah blah, hit any key (not enter ;)) and type
boot -s name_of_4.7_kernel
this will boot into single usermode.
Then, do this:
fsck -p
mount -u /
On Monday 31 March 2003 15:03, Ventsislav Velkov wrote:
I could not boot in single user mode with the 5.0 kernel because it
brokes.
Do you mean I should boot in single user with the 4.7 kernel in there
installworld and to mergemaster ?
regards,
Veno
- Original Message -
From: CARTER mailto:[EMAIL PROTECTED] Anthony
To: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Sent: Monday, March 31, 2003 3:15 PM
Subject: Re: problem updating from 4.7 Stable do 5.0 Current
Have you installed the world? I don't know if just rebuilding it is
sufficient
To install the world you have to go to single user mode and run
mergemaster to
update any changes in configuration files (take a backup of your current
files as it overwrites them).
Anthony
On Monday 31 March 2003 13:15, Ventsislav Velkov wrote:
Hello all,
I have a problem updating one of our servers from 4.7Stable to
5.0Current.
It is a Compaq Proliant 7000 Server with 4 Xeons 500Mhz with 2MB L2
cache
each. I has a 4200 Compaq Smart Raid Controler with attached 3 U1
Storages.
I update the src rebuild the world from updated src to 5.0Current,
build a
GENERIC kernel and installed it. But after I boot it brokes up during
the
booting process with the following error:
//strip
Fatal trap 12: page fault while in kernel mode cpuid=0; lapic.id=
0100
fault virtual address = 0x54
fault code = supervisor read, page not present
process eflags = interrupt enabled, resume, IOPL=0
current process = 4(g_down)
kernel: type12trap, code=0
Stopped at ida_construct_qcb+0xe3: movzbl 0x54(%eax),%eax
//strip
It may have some punctual mistakes because it is not a copy/paste.
Will appreciate any advices where could be the problem.
Best regards,
Veno
___
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem updating from 4.7 Stable do 5.0 Current
I am on the same opinion also, but only the maintainer of the driver could confirm. From: Maxim M. Kazachek To: Ventsislav Velkov Sent: Monday, March 31, 2003 5:22 PM Subject: Re: problem updating from 4.7 Stable do 5.0 Current Seems that the problem is in ida driver which runs your disk array... Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD/alpha kern.flp flood
On Sat, Mar 29, 2003 at 10:30:05PM +0200, Ruslan Ermilov wrote: On Sat, Mar 29, 2003 at 03:08:12AM -0800, Terry Lambert wrote: Makoto Matsushita wrote: It seems that kern.flp for FreeBSD/alpha is flooded (tested on FreeBSD/i386). Maybe several kbytes should be removed from the kernel: [ ... ] -r-xr-xr-x 1 root wheel 1223388 Mar 28 00:57 kernel.gz -r-xr-xr-x 1 root wheel 200864 Mar 28 00:57 loader [ ... ] Anybody have an idea to reduce the size? In theory, you could boot the kernel directly, without the loader. For that to work, though, you would need to do some extra work, but that would get you 200K back. bde@ had patches for i386 that obviate the need of loader(8). You might also consider stripping the kernel, if it's not stripped already; that will break some things, but probably not things you care about when booting from a floppy. It's already stripped. Stripping the .comment section saves me 400K for my i386 kernel. I was lying, only 12K or so. I didn't know that strip -R also does the usual stripping. Anyway, I've committed the fix to release/Makefile that strips the .comment section out from the BOOTMFS kernel. If you have time, you can exploit the effect of this by changing sweaping over src/sys/ and changing rcsid = $FreeBSD$ lines to be __FBSDID() -- that would put these IDs in the .comment section, thus reducing the size of the stripped kernel by a few more kilobytes. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age pgp0.pgp Description: PGP signature
MIDI
Hello, I am not sure if this is most appropriate here, but there is no sound-dev-current mailing list. I was very happy when compiling my 5.0 kernel. For the first time device midi compiled without giving any errors. This abnormal excitement only led to misery when I discovered after rebooting that there still was no MIDI. Is MIDI going to be implemented soon? Who is working on it? Can I help them? (I am not a very good programmer, but I can hack pre existing code, and I am good at testing). MIDI is the ONLY thing stopping me from running FreeBSD exclusively. Also Gentoo is extremely unstable. I updated ports about 2 days ago and installed it. I don't know if this is a 5.0 issue or a ports issue. Cheers, Tim -- http://www.fastmail.fm - Send your email first class ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
g++ or devd breaks world
Sources retrieved by cvsup 11 am PST. The tree is clean, and obj/ is empty. === sbin/devd c++ -O -pipe -mcpu=pentiumpro -I. -I/usr/src/sbin/devd -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/sbin/devd/devd.cc In file included from /usr/obj/usr/src/i386/usr/include/g++/bits/stl_iterator_base_funcs.h:68, from /usr/obj/usr/src/i386/usr/include/g++/bits/stl_algobase.h:74, from /usr/obj/usr/src/i386/usr/include/g++/algorithm:66, from /usr/src/sbin/devd/devd.cc:54: /usr/obj/usr/src/i386/usr/include/g++/bits/concept_check.h:64:1: multi-line comment *** Error code 1 -- Steve ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MIDI
I'm interrested in using MIDI on FreeBSD, too, but I have to tell you, that - as far as I found out - there has been midi support some time ago, but it's not included in the system/kernel anymore. There's probably some hope although, I don't find it, but I remember someone stated that you can easily apply the netbsd midi code as a patch to the current kernel. 5.0RC2 works according to this source, but had system reboots, when kldloading the midi module. If you're interrested, maybee you have more luck searching, there aren't many articles about freebsd and midi on the net (especially newer ones). I'll keep on searching Friedemann Hello, I am not sure if this is most appropriate here, but there is no sound-dev-current mailing list. I was very happy when compiling my 5.0 kernel. For the first time device midi compiled without giving any errors. This abnormal excitement only led to misery when I discovered after rebooting that there still was no MIDI. Is MIDI going to be implemented soon? Who is working on it? Can I help them? (I am not a very good programmer, but I can hack pre existing code, and I am good at testing). MIDI is the ONLY thing stopping me from running FreeBSD exclusively. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MIDI
Thus spake Thanjee Neefam [EMAIL PROTECTED]: I was very happy when compiling my 5.0 kernel. For the first time device midi compiled without giving any errors. This abnormal excitement only led to misery when I discovered after rebooting that there still was no MIDI. Is MIDI going to be implemented soon? Who is working on it? Can I help them? (I am not a very good programmer, but I can hack pre existing code, and I am good at testing). MIDI is the ONLY thing stopping me from running FreeBSD exclusively. FYI, the non-free OSS driver supports MIDI: http://www.opensound.com/bsd.html ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Upgrading from 5.0-RELEASE to -CURRENT on sparc64 (me too)
Im getting the same thing as http://groups.google.com/groups?q=+attempt+to+use+poisoned+%22malloc%22+cc1plushl=enlr=lang_enie=UTF-8oe=UTF-8safe=offselm=Pine.NEB.3.96L.1030212144405.82101A-10%40fledge.watson.org.lucky.freebsd.currentrnum=3 when doing a make buildworld.. after cvsupping CURRENT .. /usr/src/contrib/gcc/config/sparc/sysv4.h:96:1: warning: this is the location of the previous definition In file included from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/tconfig.h:11, from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/hconfig.h:2, from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/config.h:1, from /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/parse.y:34, from /usr/src/contrib/gcc/cp/spew.c:34: /usr/src/contrib/gcc/config/elfos.h:594:1: warning: STRING_ASM_OP redefined In file included from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/tconfig.h:15, from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/hconfig.h:2, from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/config.h:1, from /usr/src/contrib/gcc/cp/spew.c:26: /usr/src/contrib/gcc/config/sparc/sysv4.h:87:1: warning: this is the location of the previous definition In file included from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/tconfig.h:12, from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/hconfig.h:2, from /usr/obj/usr/src/sparc64/usr/src/gnu/usr.bin/cc/cc_tools/config.h:1, from /usr/src/gnu/usr.bin/cc/cc1plus/../../../../contrib/gcc/cp/parse.y:34, from /usr/src/contrib/gcc/cp/spew.c:34: /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:61:25: attempt to use poisoned malloc /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:62:25: attempt to use poisoned calloc /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:63:25: attempt to use poisoned realloc /usr/src/gnu/usr.bin/cc/cc_tools/freebsd-native.h:64:25: attempt to use poisoned strdup mkdep: compile failed *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc/cc1plus. *** Error code 1 Stop in /usr/src/gnu/usr.bin/cc. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. sparky# regards, Jason -- Coincidence, n.: You weren't paying attention to the other half of what was going on. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Odd issues with USB SmartMedia Reader/Writer (PNY)
I'm really dumb when it comes to CAM, SCSI, USB, and so on, so forgive if I am being naive... (Also that would probably explain why I am having a hard time deciding where this mail should end up... Forgive me on that account, plz.) I have a PNY USB SmartMedia reader which works excellently with 5.x with 8M media, but which blows up with 32M media. I'd assume this is due to improper geometry or something, but I really have no idea. Insert-reinsert produces no change in results, etc. Below are bits from dmesg, with the smaller then the larger. Any insight would be appreciated. Once this is taken care of, the weekly reboots into windows to clean off the camera can finally stop... Out last legitimate use of Windows :) %%% -- With the 8M SmartMedia umass0: Alcor Mass Storage Device, rev 1.10/1.00, addr 5 umass0: Get Max Lun not supported (STALLED) umass0:0:0:-1: Attached to scbus0 as device 0 pass0 at umass-sim0 bus 0 target 0 lun 0 pass0: Generic USB SMC Reader 1.00 Removable Direct Access SCSI-0 device pass0: 1.000MB/s transfers GEOM: new disk da0 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Generic USB SMC Reader 1.00 Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 7MB (16000 512 byte sectors: 64H 32S/T 7C) (da0:umass-sim0:0:0:0): READ(6)/WRITE(6) not supported, increasing minimum_cmd_size to 10. [0] f:80 typ:1 s(CHS):0/1/10 e(CHS):249/3/16 s:25 l:15975 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure da0s1, start 12800 length 8179200 end 8191999 %%% %%% -- With the 32M SmartMedia umass0: Alcor Mass Storage Device, rev 1.10/1.00, addr 5 umass0: Get Max Lun not supported (STALLED) umass0:0:0:-1: Attached to scbus0 as device 0 pass0 at umass-sim0 bus 0 target 0 lun 0 pass0: Generic USB SMC Reader 1.00 Removable Direct Access SCSI-0 device pass0: 1.000MB/s transfers GEOM: new disk da0 (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error da0 at umass-sim0 bus 0 target 0 lun 0 da0: Generic USB SMC Reader 1.00 Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present Unretryable error (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error Opened disk da0 - 6 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present Unretryable error (da0:umass-sim0:0:0:0): error 6 (da0:umass-sim0:0:0:0): Unretryable Error Opened disk da0 - 6 %%% Thanx! juli. -- juli mallett. email: [EMAIL PROTECTED]; aim: bsdflata; efnet: juli; ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
New threading code.
The kernel components for the 1:1 threading implementation are in the tree. This includes the thr system calls, the umtx implementation, and all of the signal changes. I will commit the library shortly. This is all 'beta' quality. It runs mozilla and openoffice without issue. There are known bugs which I will point out when libthr is in the tree. More to come. Cheers, Jeff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
sparc64 tinderbox failure
Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html -- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- === bin/ps /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/lib/libkvm.a(kvm_proc.o)(.text+0x794): undefined reference to `SIGANDSET' *** Error code 1 Stop in /tinderbox/sparc64/src/bin/ps. *** Error code 1 Stop in /tinderbox/sparc64/src/bin. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. *** Error code 1 Stop in /tinderbox/sparc64/src. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
libthr and 1:1 threading.
I have commited libthr. To try this out you'll need to do the following 1. cvsup 2. rebuild world and kernel 3. install world and kernel 4. build libthr from src/lib/libthr 5. Either replace /usr/lib/libc_r.so.5 with /usr/lib/libthr.so.1 or relink your applications against libthr.so.1 This works with mozilla and open office. Known errata: 1. Mutex priority inheritance is not implemented. 2. If you mess with the mutex or condvar queues from a signal handler you will break. 3. If you reset the sigaction for SIGTHR you will break things. 4. The scheduling parameters lie. 5. The garbage collector deadlocks. We never free threads. You will eventually leak memory or run out of LDT entries. 6. This is x86 only for a short while. 7. Some of the code is ugly. I will be addressing all of this shortly. Feel free to try it out and report bugs that are not mentioned above. Cheers, Jeff ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: isnan() with gcc 3.2.2 on FreeBSD 5.0-C
On Mon, Mar 31, 2003 at 02:46:05PM +0800, Ying-Chieh Liao wrote: what's wrong with my system ? or what can I do for it ? See Message-ID: [EMAIL PROTECTED] Kris pgp0.pgp Description: PGP signature
Re: isnan() with gcc 3.2.2 on FreeBSD 5.0-C
On Mon, Mar 31, 2003 at 02:46:05PM +0800, Ying-Chieh Liao wrote:
the following code snippet works fine with gcc 2.95.4 on RELENG_4
but failed on my -current
code
#include iostream
#include cmath
using namespace std;
int main(void)
{
cout isnan(1.0) endl;
return 0;
}
/code
err
test.cpp: In function `int main()':
test.cpp:8: `isnan' undeclared (first use this function)
test.cpp:8: (Each undeclared identifier is reported only once for each function
it appears in.)
/err
what's wrong with my system ? or what can I do for it ?
The isnan() macro is a new feature of C99 and thus not (yet) part of
C++. Nevertheless you can use -D_GLIBCPP_USE_C99 to include this and
some other non-standard C++ features.
Regards,
Stefan Farfeleder
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to [EMAIL PROTECTED]
