From owner-freebsd-mobile Sun Feb 14 00:01:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01234 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 00:01:18 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA01229 for ; Sun, 14 Feb 1999 00:01:16 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 10BwUL-0003gG-00; Sun, 14 Feb 1999 01:01:13 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.2/8.8.3) with ESMTP id BAA28748; Sun, 14 Feb 1999 01:03:18 -0700 (MST) Message-Id: <199902140803.BAA28748@harmony.village.org> To: Gianmarco Giovannelli Subject: Re: PCMCIA Question: Toshiba PDR-2 Digital Camera Cc: Michael Robinson , mobile@FreeBSD.ORG In-reply-to: Your message of "Thu, 11 Feb 1999 15:00:14 +0100." <4.1.19990211145825.0097c100@194.184.65.4> References: <4.1.19990211145825.0097c100@194.184.65.4> <3.0.3.32.19990208124746.00e43f08@207.86.113.200> Date: Sun, 14 Feb 1999 01:03:18 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <4.1.19990211145825.0097c100@194.184.65.4> Gianmarco Giovannelli writes: : Why not find some any good soul and finally commit them ?? : I have asked it several time, but without any success ... I'll do it. Well, I think I need to get a ATA flash rom card first to check it out... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Feb 14 06:32:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02580 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 06:32:26 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from olsen.capsl.udel.edu (olsen.capsl.udel.edu [128.4.10.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02575 for ; Sun, 14 Feb 1999 06:32:23 -0800 (PST) (envelope-from heber@elmasri.capsl.udel.edu) Received: from elmasri.capsl.udel.edu (elmasri.capsl.udel.edu [128.4.10.24]) by olsen.capsl.udel.edu (8.9.1/8.9.1) with SMTP id JAA14489; Sun, 14 Feb 1999 09:32:14 -0500 (EST) Date: Sun, 14 Feb 1999 09:32:12 -0500 (EST) From: Gerd Heber To: Warner Losh cc: ulf@Alameda.net, mobile@FreeBSD.ORG Subject: Re: external floppy on libretto 110ct In-Reply-To: <199902140802.BAA28726@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org folks, thanks for all your comments. from what I found, the Libretto 110CT's external floppy is supported in PAO but not in 2.2.8-STABLE. the entry in the kernel config reads as follows. controller fdc1 at isa? disable port "IO_YEFDC" bio irq 6 vector fdintr disk fd1 at fdc1 drive 0 options FDC_YE Luigi's sound driver works well with this entry: device pcm0 at isa? port ? tty irq 5 drq 1 flags 0x10 vector pcmintr hibernation mode on power off or closing the panel works fine, and controlling it by libretto-config (/usr/ports/sysutils) is very easy. thanks for your help. gerd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Feb 14 08:46:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA12492 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 08:46:40 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA12487 for ; Sun, 14 Feb 1999 08:46:37 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (ppp7.imasy.or.jp [202.227.24.17]) by tasogare.imasy.or.jp (8.9.3+3.1W/3.7W-tasogare) with ESMTP id BAA21353; Mon, 15 Feb 1999 01:46:04 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199902141646.BAA21353@tasogare.imasy.or.jp> To: Valentin Shopov Cc: mobile@FreeBSD.ORG, Nate Williams , Warner Losh Subject: Re: apm & current In-reply-to: Your message of "Sat, 13 Feb 1999 07:39:58 PST." <19990213153958.2977.rocketmail@send1e.yahoomail.com> References: <19990213153958.2977.rocketmail@send1e.yahoomail.com> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 15 Feb 1999 01:43:35 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 790 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I'm now working on APM code for PAO in Japan. > Also kernel panics every time when I run apm, but zzz - suspend is > working. I already noticed that this problem happens on some old laptops which has apm v1.1 or 1.0 (Sotec WinBookPro DX4/100, DEC HiNote Ultra II, etc.). -current/-stable apm(8) try to call APM v1.2 BIOS functions (e.g. APM_RESUMETIMER) without version checking. Some of the old APM BIOSes, however, can make kernel panic when recieved unkown APM BIOS functions. In /sys/i386/apm/apm.c, apm_get_info() has the same problem (APM_GETCAPABILITIES), therefore xbatt also will cause the same trouble. So, now I'm going to commit version checking code just before calling apm_bios_call() in /sys/i386/apm/apm.c into PAO3 CVS repository. Adding to this, I noticed many other problems in apm code, such as - Fixed segment description for APM. The limit granularity should be specified in bytes, not pages. - Try to limit the number of apm_bios_call() executing to only one at the same time, watching busy state made by previous call and waiting if necessary. - Made apm_suspend() and apm_standby() be invoked by apm_timeout() in order to obtain stablities. - Added adjustment for segment size limits informed by APM BIOS. Following patch for apm_init.S and make in /sys/i386/apm/apm_init/ to generate apm_init.inc are required if VM86 isn't enabled in your kernel. --- /usr/src/sys/i386/apm/apm_init/apm_init.S Sat Feb 22 18:29:52 1997 +++ apm_init/apm_init.S Sun Feb 14 20:47:04 1999 @@ -150,6 +150,8 @@ movb $(APM_PROT32CONNECT), %al data32 movl $(PMDV_APMBIOS), %ebx + xorl %esi, %esi /* XXX clear %esi for cs length */ + xorl %edi, %edi /* XXX clear %edi for ds length */ sti int $(SYSTEM_BIOS) cli Followings are diffs for /sys/i386/apm/apm.c between PAO3 (not commited yet) and 3.0-RELEASE, please take a look this code. --- /usr/src/sys/i386/apm/apm.c Mon Sep 28 12:41:12 1998 +++ apm.c Sun Feb 14 22:01:16 1999 @@ -29,6 +29,7 @@ #endif /*DEVFS*/ #include #include +#include #include #include #include @@ -48,11 +49,17 @@ static int apm_int __P((u_long *eax, u_long *ebx, u_long *ecx, u_long *edx)); static void apm_resume __P((void)); +#define APM_FORCE_APM10_FLAG 0x02 +#define APM_NO_CLOCK_ADJUST_FLAG 0x04 +#define APM_FORCE_64K_SEG_FLAG 0x08 + + /* static data */ struct apm_softc { int initialized, active; int always_halt_cpu, slow_idle_cpu; int disabled, disengaged; + int suspending; u_int minorversion, majorversion; u_int cs32_base, cs16_base, ds_base; u_int cs16_limit, cs32_limit, ds_limit; @@ -92,16 +99,54 @@ setup_apm_gdt(u_int code32_base, u_int code16_base, u_int data_base, u_int code32_limit, u_int code16_limit, u_int data_limit) { /* setup 32bit code segment */ + /* iwasaki (1999/1/24) + * type : S bit = on, code segment, readable, accessed + * dpl : kernel priority level + * def32: default 32 bit size + * gran : limit granularity = byte units + */ gdt_segs[GAPMCODE32_SEL].ssd_base = code32_base; gdt_segs[GAPMCODE32_SEL].ssd_limit = code32_limit; + gdt_segs[GAPMCODE32_SEL].ssd_type = SDT_MEMERA; + gdt_segs[GAPMCODE32_SEL].ssd_dpl = SEL_KPL; + gdt_segs[GAPMCODE32_SEL].ssd_def32 = 1; + gdt_segs[GAPMCODE32_SEL].ssd_gran = 0; /* setup 16bit code segment */ + /* iwasaki (1999/1/24) + * type : S bit = on, code segment, readable, accessed + * dpl : kernel priority level + * def32: default 16 bit size + * gran : limit granularity = byte units + */ gdt_segs[GAPMCODE16_SEL].ssd_base = code16_base; gdt_segs[GAPMCODE16_SEL].ssd_limit = code16_limit; + gdt_segs[GAPMCODE16_SEL].ssd_type = SDT_MEMERA; + gdt_segs[GAPMCODE16_SEL].ssd_dpl = SEL_KPL; + gdt_segs[GAPMCODE16_SEL].ssd_def32 = 0; + gdt_segs[GAPMCODE16_SEL].ssd_gran = 0; /* setup data segment */ + /* iwasaki (1999/1/24) + * type : S bit = on, data segment, writable, accessed + * dpl : kernel priority level + * def32: default 32 bit size + * gran : limit granularity = byte units + */ gdt_segs[GAPMDATA_SEL ].ssd_base = data_base; gdt_segs[GAPMDATA_SEL ].ssd_limit = data_limit; + gdt_segs[GAPMDATA_SEL ].ssd_type = SDT_MEMRWA; + gdt_segs[GAPMDATA_SEL ].ssd_dpl = SEL_KPL; + gdt_segs[GAPMDATA_SEL ].ssd_def32 = 1; + gdt_segs[GAPMDATA_SEL ].ssd_gran = 0; + if (data_limit == 0) { + /* iwasaki (1999/1/24) + * type : S bit = on, data segment, accessed + * def32: default 16 bit size + */ + gdt_segs[GAPMDATA_SEL ].ssd_type = SDT_MEMROA; + gdt_segs[GAPMDATA_SEL ].ssd_def32 = 0; + } /* reflect these changes on physical GDT */ ssdtosd(gdt_segs + GAPMCODE32_SEL, &gdt[GAPMCODE32_SEL].sd); @@ -116,6 +161,49 @@ } apm_addr; static int apm_errno; +static int apm_bios_busy = 0; + +static int +apm_do_int(struct apm_bios_arg *apap) +{ + struct apm_softc *sc = &apm_softc; + int cf; + int n = 0; + u_long apm_func; + + apm_func = apap->eax & 0x00ff; + switch (sc->intversion) { + case INTVERSION(1, 0): + if (apm_func != APM_DRVVERSION && + apm_func > APM_GETPMEVENT) { +#ifdef APM_DEBUG +printf("apm_int: function 0x%lx is not supported by APM V1.0\n", apm_func); +#endif + return ENOSYS; + } + break; + case INTVERSION(1, 1): + if (apm_func != APM_DRVVERSION && + apm_func > APM_ENGAGEDISENGAGEPM && + apm_func < APM_OEMFUNC) { +#ifdef APM_DEBUG +printf("apm_int: function 0x%lx is not supported by APM V1.1\n", apm_func); +#endif + return ENOSYS; + } + break; + case INTVERSION(1, 2): + break; + } + + while (apm_bios_busy && n++ < 50) { + DELAY(100000L); + } + ++apm_bios_busy; + cf = apm_bios_call(apap); + apm_bios_busy = 0; + return cf; +} static int apm_int(u_long *eax, u_long *ebx, u_long *ecx, u_long *edx) @@ -127,7 +215,9 @@ apa.ebx = *ebx; apa.ecx = *ecx; apa.edx = *edx; - cf = apm_bios_call(&apa); + apa.esi = 0; /* clear register */ + apa.edi = 0; /* clear register */ + cf = apm_do_int(&apa); *eax = apa.eax; *ebx = apa.ebx; *ecx = apa.ecx; @@ -156,12 +246,12 @@ return apm_int(&eax, &ebx, &ecx, &edx); } +/* Tell APM-BIOS that WE will do 1.1 and see what they say... */ static void apm_driver_version(int version) { u_long eax, ebx, ecx, edx; - /* First try APM 1.2 */ eax = (APM_BIOS << 8) | APM_DRVVERSION; ebx = 0x0; ecx = version; @@ -246,17 +336,24 @@ * Turn off the entire system. */ void -apm_power_off(void) +apm_power_off(int dummy, void *dummy_arg) { u_long eax, ebx, ecx, edx; if (!apm_softc.active) return; + + /* wait 1sec before turning off the system power */ + DELAY(1000000); + eax = (APM_BIOS << 8) | APM_SETPWSTATE; ebx = PMDV_ALLDEV; ecx = PMST_OFF; edx = 0; - apm_int(&eax, &ebx, &ecx, &edx); + if (apm_int(&eax, &ebx, &ecx, &edx)) { + printf("Power off failure: errcode = %ld\n", + 0xff & (eax >> 8)); + } } /* APM Battery low handler */ @@ -358,6 +455,7 @@ static struct timeval suspend_time; static struct timeval diff_time; +static int apm_no_clock_adjust = 0; static int apm_default_resume(void *arg) @@ -366,40 +464,45 @@ u_int second, minute, hour; struct timeval resume_time, tmp_time; - /* modified for adjkerntz */ - pl = splsoftclock(); - inittodr(0); /* adjust time to RTC */ - microtime(&resume_time); - getmicrotime(&tmp_time); - timevaladd(&tmp_time, &diff_time); + if (apm_no_clock_adjust) { + log(LOG_NOTICE, "resumed from suspended mode\n"); + } + else { + /* modified for adjkerntz */ + pl = splsoftclock(); + inittodr(0); /* adjust time to RTC */ + microtime(&resume_time); + getmicrotime(&tmp_time); + timevaladd(&tmp_time, &diff_time); #ifdef FIXME - /* XXX THIS DOESN'T WORK!!! */ - time = tmp_time; + /* XXX THIS DOESN'T WORK!!! */ + time = tmp_time; #endif #ifdef APM_FIXUP_CALLTODO - /* Calculate the delta time suspended */ - timevalsub(&resume_time, &suspend_time); - /* Fixup the calltodo list with the delta time. */ - adjust_timeout_calltodo(&resume_time); + /* Calculate the delta time suspended */ + timevalsub(&resume_time, &suspend_time); + /* Fixup the calltodo list with the delta time. */ + adjust_timeout_calltodo(&resume_time); #endif /* APM_FIXUP_CALLTODOK */ - splx(pl); + splx(pl); #ifndef APM_FIXUP_CALLTODO - second = resume_time.tv_sec - suspend_time.tv_sec; + second = resume_time.tv_sec - suspend_time.tv_sec; #else /* APM_FIXUP_CALLTODO */ - /* - * We've already calculated resume_time to be the delta between - * the suspend and the resume. - */ - second = resume_time.tv_sec; + /* + * We've already calculated resume_time to be the delta between + * the suspend and the resume. + */ + second = resume_time.tv_sec; #endif /* APM_FIXUP_CALLTODO */ - hour = second / 3600; - second %= 3600; - minute = second / 60; - second %= 60; - log(LOG_NOTICE, "resumed from suspended mode (slept %02d:%02d:%02d)\n", - hour, minute, second); + hour = second / 3600; + second %= 3600; + minute = second / 60; + second %= 60; + log(LOG_NOTICE, "resumed from suspended mode (slept %02d:%02d:%02d)\n", + hour, minute, second); + } return 0; } @@ -408,35 +511,52 @@ { int pl; - pl = splsoftclock(); - microtime(&diff_time); - inittodr(0); - microtime(&suspend_time); - timevalsub(&diff_time, &suspend_time); - splx(pl); + if (!apm_no_clock_adjust) { + pl = splsoftclock(); + microtime(&diff_time); + inittodr(0); + microtime(&suspend_time); + timevalsub(&diff_time, &suspend_time); + splx(pl); + } return 0; } +/* + * Do not suspend immediately after the system is resumed from + * suspended mode + */ + static void apm_processevent(void); -/* - * Public interface to the suspend/resume: - * - * Execute suspend and resume hook before and after sleep, respectively. - * - */ +static u_int apm_standbys = 0; +static u_int apm_suspends = 0; +static u_int apm_op_inprog = 0; -void -apm_suspend(int state) +static void +apm_do_suspend(void) { struct apm_softc *sc = &apm_softc; if (!sc) return; + apm_op_inprog = 0; + apm_suspends = 0; + + if (sc->suspending != 0) { /* avoid reentry */ + /* PCG-505: suspend -> save-to-disk */ + if (sc->initialized) { + if (apm_suspend_system(PMST_SUSPEND) == 0) + apm_processevent(); + } + return; + } + sc->suspending = 1; + if (sc->initialized) { apm_execute_hook(hook[APM_HOOK_SUSPEND]); - if (apm_suspend_system(state) == 0) + if (apm_suspend_system(PMST_SUSPEND) == 0) apm_processevent(); else /* Failure, 'resume' the system again */ @@ -444,6 +564,61 @@ } } +static void +apm_do_standby(void) +{ + apm_op_inprog = 0; + apm_standbys = 0; + + apm_default_suspend(&apm_softc); + if (apm_suspend_system(PMST_STANDBY) == 0) + apm_processevent(); +} + +static void +apm_lastreq_notify(void) +{ + u_long eax, ebx, ecx, edx; + + eax = (APM_BIOS << 8) | APM_SETPWSTATE; + ebx = PMDV_ALLDEV; + ecx = PMST_LASTREQNOTIFY; + edx = 0; + + apm_int(&eax, &ebx, &ecx, &edx); +} + +/* + * Public interface to the suspend/resume: + * + * Execute suspend and resume hook before and after sleep, respectively. + * + */ + +void +apm_suspend(int state) +{ + switch (state) { + case PMST_SUSPEND: + if(apm_suspends) + return; + apm_suspends++; + apm_op_inprog++; + apm_lastreq_notify(); + break; + case PMST_STANDBY: + if(apm_standbys) + return; + apm_standbys++; + apm_op_inprog++; + apm_lastreq_notify(); + break; + default: + printf("Unknown Suspend state 0x%x\n", state); + break; + } +} + void apm_resume(void) { @@ -452,6 +627,8 @@ if (!sc) return; + sc->suspending = 0; + if (sc->initialized) apm_execute_hook(hook[APM_HOOK_RESUME]); } @@ -472,7 +649,7 @@ if (apm_int(&eax, &ebx, &ecx, &edx)) return 1; - aip->ai_infoversion = 1; + aip->ai_infoversion = (sc->intversion >= INTVERSION(1, 2)) ? 1 : 0; aip->ai_acline = (ebx >> 8) & 0xff; aip->ai_batt_stat = ebx & 0xff; aip->ai_batt_life = ecx & 0xff; @@ -487,16 +664,21 @@ else /* Time is in seconds */ aip->ai_batt_time = edx; - eax = (APM_BIOS << 8) | APM_GETCAPABILITIES; - ebx = 0; - ecx = 0; - edx = 0; - if (apm_int(&eax, &ebx, &ecx, &edx)) { - aip->ai_batteries = -1; /* Unknown */ - aip->ai_capabilities = 0xff00; /* Unknown, with no bits set */ + if (sc->intversion >= INTVERSION(1, 2)) { + eax = (APM_BIOS << 8) | APM_GETCAPABILITIES; + ebx = 0; + ecx = 0; + edx = 0; + if (apm_int(&eax, &ebx, &ecx, &edx)) { + aip->ai_batteries = -1; /* Unknown */ + aip->ai_capabilities = 0xff00; /* Unknown, with no bits set */ + } else { + aip->ai_batteries = ebx & 0xff; + aip->ai_capabilities = ecx & 0xf; + } } else { - aip->ai_batteries = ebx & 0xff; - aip->ai_capabilities = ecx & 0xf; + aip->ai_batteries = -1; /* Unknown */ + aip->ai_capabilities = 0xff00; /* Unknown, with no bits set */ } bzero(aip->ai_spare, sizeof aip->ai_spare); @@ -564,10 +746,21 @@ { struct apm_softc *sc = &apm_softc; + if (apm_op_inprog) + apm_lastreq_notify(); + apm_processevent(); - if (sc->active == 1) + + if (apm_standbys) + apm_do_standby(); + + if (apm_suspends) + apm_do_suspend(); + + if (sc->active == 1) { /* Run slightly more oftan than 1 Hz */ apm_timeout_ch = timeout(apm_timeout, NULL, hz - 1 ); + } } /* enable APM BIOS */ @@ -741,7 +934,7 @@ apm_suspend(PMST_SUSPEND); break; OPMEV_DEBUGMESSAGE(PMEV_CRITSUSPEND); - apm_suspend(PMST_SUSPEND); + apm_do_suspend(); break; OPMEV_DEBUGMESSAGE(PMEV_NORMRESUME); apm_resume(); @@ -750,11 +943,17 @@ apm_resume(); break; OPMEV_DEBUGMESSAGE(PMEV_STANDBYRESUME); - apm_resume(); +#if 0 + apm_resume(); /* should we call this or not? */ +#else /* 0 */ + inittodr(0); /* adjust time to RTC */ +#endif /* 0 */ break; OPMEV_DEBUGMESSAGE(PMEV_BATTERYLOW); apm_battery_low(); +#ifdef APM_BATT_LOW_SUSPEND apm_suspend(PMST_SUSPEND); +#endif /* APM_BATT_LOW_SUSPEND */ break; OPMEV_DEBUGMESSAGE(PMEV_POWERSTATECHANGE); break; @@ -781,6 +980,27 @@ { #define APM_KERNBASE KERNBASE struct apm_softc *sc = &apm_softc; + int apm_force_apm10 = 0; + int apm_force_64k_segments = 0; + int rversion, rmajorversion, rminorversion; + +#ifdef FORCE_APM10 + apm_force_apm10 = 1; +#else /* FORCE_APM10 */ + apm_force_apm10 = (dvp->id_flags & APM_FORCE_APM10_FLAG); +#endif /* FORCE_APM10 */ + +#ifdef APM_NO_CLOCK_ADJUST + apm_no_clock_adjust = 1; +#else /* APM_NO_CLOCK_ADJUST */ + apm_no_clock_adjust = (dvp->id_flags & APM_NO_CLOCK_ADJUST_FLAG); +#endif /* APM_NO_CLOCK_ADJUST */ + +#ifdef APM_FORCE_64K_SEG + apm_force_64k_segments = 1; +#else /* APM_FORCE_64K_SEG */ + apm_force_64k_segments = (dvp->id_flags & APM_FORCE_64K_SEG_FLAG); +#endif /* APM_FORCE_64K_SEG */ sc->initialized = 0; @@ -791,13 +1011,85 @@ sc->cs16_base = (apm_cs16_base << 4) + APM_KERNBASE; sc->cs32_base = (apm_cs32_base << 4) + APM_KERNBASE; sc->ds_base = (apm_ds_base << 4) + APM_KERNBASE; - sc->cs32_limit = apm_cs32_limit - 1; - if (apm_cs16_limit == 0) - apm_cs16_limit == apm_cs32_limit; - sc->cs16_limit = apm_cs16_limit - 1; - sc->ds_limit = apm_ds_limit - 1; sc->cs_entry = apm_cs_entry; + /* + * Some bogus APM V1.1 BIOSes do not return any + * size limits in the registers they are supposed to. + * We forced them to zero before calling the BIOS + * (see apm_init.S), so if we see zero limits here + * we assume that means they should be 64k (and trimmed + * if needed for legitimate memory needs). + */ + + /* for V1.0 and bogus BIOSes */ + if (apm_version <= 0x100 || apm_version >= 0xa00 || apm_force_apm10) { + apm_force_64k_segments = 1; + } + + if (apm_force_64k_segments) { + sc->cs32_limit = 0xffff; + sc->cs16_limit = 0xffff; + sc->ds_limit = 0xffff; + } else { + /* code segment (32 bit) */ + if (apm_cs32_limit == 0) { + /* XXX + * some BIOSes are lame, even if v1.1. + * (Or maybe they want 64k even though they can + * only ask for 64k-1?) + */ +#ifdef APM_DEBUG + printf("apmattach: lame v%04lx bios gave zero len code32, pegged to 64k\n", + apm_version); +#endif + sc->cs32_limit = 0xffff; + } else { + sc->cs32_limit = apm_cs32_limit - 1; + } + + /* code segment (16 bit) */ + if (apm_cs16_limit == 0) { +#ifdef APM_DEBUG + printf("apmattach: v%04lx bios gave zero len code16, pegged to code32's one\n", + apm_version); +#endif + sc->cs16_limit = sc->cs32_limit; + } else { + sc->cs16_limit = apm_cs16_limit - 1; + } + + /* data segment */ + if (apm_ds_limit == 0) { + /* XXX + * some BIOSes are lame, even if v1.1. + * just assume that means they should be 64k :-) + * TODO: + * need to confirm that segment in an available + * location within ISA hole or at page zero or + * above biosbasemem and below ISA hole end. + * if there is no avaivable locations, set up + * the segment descriptor to just the first byte + * of the code segment, read only. + */ +#ifdef APM_DEBUG + printf("apmattach: lame v%04lx bios gave zero len data, tentative 64k\n", + apm_version); +#endif + sc->ds_limit = 0xffff; + } else { + sc->ds_limit = apm_ds_limit - 1; + } + } + + if (sc->cs32_limit < sc->cs_entry + 4) { +#ifdef APM_DEBUG + printf("apmattach: nonsensical BIOS code length %d ignored (entry point offset is %d)\n", + sc->cs32_limit, sc->cs_entry); +#endif + sc->cs32_limit = 0xffff; + } + /* Always call HLT in idle loop */ sc->always_halt_cpu = 1; @@ -807,14 +1099,14 @@ /* print bootstrap messages */ #ifdef APM_DEBUG - printf("apm: APM BIOS version %04x\n", apm_version); + printf("apm: APM BIOS version %04lx\n", apm_version); printf("apm: Code32 0x%08x, Code16 0x%08x, Data 0x%08x\n", sc->cs32_base, sc->cs16_base, sc->ds_base); printf("apm: Code entry 0x%08x, Idling CPU %s, Management %s\n", sc->cs_entry, is_enabled(sc->slow_idle_cpu), is_enabled(!sc->disabled)); printf("apm: CS32_limit=0x%x, CS16_limit=0x%x, DS_limit=0x%x\n", - (u_short)sc->cs32_limit, (u_short)sc->cs16_limit, (u_short)sc->ds_limit); + sc->cs32_limit, sc->cs16_limit, sc->ds_limit); #endif /* APM_DEBUG */ #if 0 @@ -831,35 +1123,60 @@ apm_addr.segment = GSEL(GAPMCODE32_SEL, SEL_KPL); apm_addr.offset = sc->cs_entry; - if ((dvp->id_flags & 0x10)) { - if ((dvp->id_flags & 0xf) >= 0x2) { + rversion = apm_version; + rminorversion = ((rversion & 0x00f0) >> 4) * 10 + + ((rversion & 0x000f) >> 0); + rmajorversion = ((rversion & 0xf000) >> 12) * 10 + + ((rversion & 0x0f00) >> 8); + + if (apm_force_apm10) { + apm_version = 0x100; + sc->majorversion = 1; + sc->minorversion = 0; + sc->intversion = INTVERSION(1, 0); + printf("apm: running in APM 1.0 compatible mode\n"); + } + else{ + if (rmajorversion > 1 || + (rmajorversion == 1 && rminorversion >= 2)) { apm_driver_version(0x102); - } - if (!apm_version && (dvp->id_flags & 0xf) >= 0x1) { + sc->intversion = INTVERSION(1, 2); + } else if (rmajorversion == 1 && rminorversion >= 1) { apm_driver_version(0x101); + sc->intversion = INTVERSION(1, 1); } - } else { - apm_driver_version(0x102); - if (!apm_version) - apm_driver_version(0x101); - } - if (!apm_version) - apm_version = 0x100; - sc->minorversion = ((apm_version & 0x00f0) >> 4) * 10 + - ((apm_version & 0x000f) >> 0); - sc->majorversion = ((apm_version & 0xf000) >> 12) * 10 + - ((apm_version & 0x0f00) >> 8); + if (!apm_version) + apm_version = 0x100; - sc->intversion = INTVERSION(sc->majorversion, sc->minorversion); + sc->minorversion = ((apm_version & 0x00f0) >> 4) * 10 + + ((apm_version & 0x000f) >> 0); + sc->majorversion = ((apm_version & 0xf000) >> 12) * 10 + + ((apm_version & 0x0f00) >> 8); + + if ((sc->majorversion == 1 && sc->minorversion == 0 + && rmajorversion >= 1 && rminorversion >= 1) + || sc->majorversion > 10 /* for broken APM 1.1 */ + ) { + apm_version = 0x100; + sc->majorversion = 1; + sc->minorversion = 0; + sc->intversion = INTVERSION(1, 0); + printf("apm: running in APM 1.0 compatible mode\n"); + } + else{ + sc->intversion = INTVERSION(sc->majorversion, sc->minorversion); #ifdef APM_DEBUG - if (sc->intversion >= INTVERSION(1, 1)) - printf("apm: Engaged control %s\n", is_enabled(!sc->disengaged)); + if (sc->intversion >= INTVERSION(1, 1)) + printf("apm: Engaged control %s\n", + is_enabled(!sc->disengaged)); #endif - printf("apm: found APM BIOS version %d.%d\n", - sc->majorversion, sc->minorversion); + printf("apm: found APM BIOS version %d.%d\n", + sc->majorversion, sc->minorversion); + } + } #ifdef APM_DEBUG printf("apm: Slow Idling CPU %s\n", is_enabled(sc->slow_idle_cpu)); @@ -901,6 +1218,8 @@ apm_hook_establish(APM_HOOK_SUSPEND, &sc->sc_suspend); apm_hook_establish(APM_HOOK_RESUME , &sc->sc_resume); + at_shutdown(apm_power_off, NULL, SHUTDOWN_POWER_OFF); + apm_event_enable(); sc->initialized = 1; @@ -939,7 +1258,7 @@ if (minor(dev) != 0 || !sc->initialized) return (ENXIO); #ifdef APM_DEBUG - printf("APM ioctl: cmd = 0x%x\n", cmd); + printf("APM ioctl: cmd = 0x%lx\n", cmd); #endif switch (cmd) { case APMIO_SUSPEND: @@ -991,11 +1310,13 @@ case APMIO_DISPLAY: newstate = *(int *)addr; if (apm_display(newstate)) error = ENXIO; break; case APMIO_BIOS: - if (apm_bios_call((struct apm_bios_arg*)addr) == 0) + if ((error = apm_do_int((struct apm_bios_arg*)addr)) == 0) ((struct apm_bios_arg*)addr)->eax &= 0xff; + else if (error == 1) + error = 0; break; default: error = EINVAL; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Feb 14 11:17:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27463 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 11:17:40 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from send104.yahoomail.com (send104.yahoomail.com [205.180.60.122]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA27457 for ; Sun, 14 Feb 1999 11:17:37 -0800 (PST) (envelope-from valsho@yahoo.com) Message-ID: <19990214191802.16765.rocketmail@send104.yahoomail.com> Received: from [147.226.106.179] by send104.yahoomail.com; Sun, 14 Feb 1999 11:18:02 PST Date: Sun, 14 Feb 1999 11:18:02 -0800 (PST) From: Valentin Shopov Subject: Re: apm & current To: Mitsuru IWASAKI Cc: mobile@FreeBSD.ORG, Nate Williams , Warner Losh MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ---Mitsuru IWASAKI wrote: > > Hello, I'm now working on APM code for PAO in Japan. > > > Also kernel panics every time when I run apm, but zzz - suspend is > > working. > > I already noticed that this problem happens on some old laptops which has > apm v1.1 or 1.0 (Sotec WinBookPro DX4/100, DEC HiNote Ultra II, etc.). > -current/-stable apm(8) try to call APM v1.2 BIOS functions > (e.g. APM_RESUMETIMER) without version checking. > Some of the old APM BIOSes, however, can make kernel panic when recieved > unkown APM BIOS functions. > In /sys/i386/apm/apm.c, apm_get_info() has the same problem > (APM_GETCAPABILITIES), therefore xbatt also will cause the same trouble. > > So, now I'm going to commit version checking code just before > calling apm_bios_call() in /sys/i386/apm/apm.c into PAO3 CVS repository. > On my old GVC G740 notebook (486DX4/75) kernel panics after calling V1.2 functions . Val == Valentin Shopov 2301 West Bethel Ave., #53 Muncie, IN 47304-2112 Phone: ++1-(765)-214-0504 E-Mail: valsho@yahoo.com valsho@usa.net URL: http://www.cyberspace.org/~valentin _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Feb 14 13:00:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08057 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 13:00:25 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA08052 for ; Sun, 14 Feb 1999 13:00:19 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 10C8dw-00047t-00; Sun, 14 Feb 1999 13:59:56 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.2/8.8.3) with ESMTP id OAA32088; Sun, 14 Feb 1999 14:02:07 -0700 (MST) Message-Id: <199902142102.OAA32088@harmony.village.org> To: Mitsuru IWASAKI Subject: Re: apm & current Cc: Valentin Shopov , mobile@FreeBSD.ORG, Nate Williams In-reply-to: Your message of "Mon, 15 Feb 1999 01:43:35 +0900." <199902141646.BAA21353@tasogare.imasy.or.jp> References: <199902141646.BAA21353@tasogare.imasy.or.jp> <19990213153958.2977.rocketmail@send1e.yahoomail.com> Date: Sun, 14 Feb 1999 14:02:06 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199902141646.BAA21353@tasogare.imasy.or.jp> Mitsuru IWASAKI writes: : I already noticed that this problem happens on some old laptops which has : apm v1.1 or 1.0 (Sotec WinBookPro DX4/100, DEC HiNote Ultra II, etc.). : -current/-stable apm(8) try to call APM v1.2 BIOS functions : (e.g. APM_RESUMETIMER) without version checking. : Some of the old APM BIOSes, however, can make kernel panic when recieved : unkown APM BIOS functions. : In /sys/i386/apm/apm.c, apm_get_info() has the same problem : (APM_GETCAPABILITIES), therefore xbatt also will cause the same trouble. : : So, now I'm going to commit version checking code just before : calling apm_bios_call() in /sys/i386/apm/apm.c into PAO3 CVS repository. These patches look basically good. I'll integrate them when I have a chance. : Adding to this, I noticed many other problems in apm code, such as : - Fixed segment description for APM. The limit granularity should be : specified in bytes, not pages. This looks good. : - Try to limit the number of apm_bios_call() executing to only one : at the same time, watching busy state made by previous call and : waiting if necessary. I wonder how this can happen, but it couldn't hurt. : - Made apm_suspend() and apm_standby() be invoked by apm_timeout() in order to : obtain stablities. What stabilities are these? I'm curious. : - Added adjustment for segment size limits informed by APM BIOS. Following : patch for apm_init.S and make in /sys/i386/apm/apm_init/ to generate : apm_init.inc are required if VM86 isn't enabled in your kernel. These look good to me. I'll also have to take a look at the PAO3 CVS tree... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Feb 14 13:02:35 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08487 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 13:02:35 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA08482 for ; Sun, 14 Feb 1999 13:02:33 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 10C8gO-000486-00; Sun, 14 Feb 1999 14:02:28 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.2/8.8.3) with ESMTP id OAA32130; Sun, 14 Feb 1999 14:04:40 -0700 (MST) Message-Id: <199902142104.OAA32130@harmony.village.org> To: Mitsuru IWASAKI Subject: Re: apm & current Cc: Valentin Shopov , mobile@FreeBSD.ORG, Nate Williams In-reply-to: Your message of "Mon, 15 Feb 1999 01:43:35 +0900." <199902141646.BAA21353@tasogare.imasy.or.jp> References: <199902141646.BAA21353@tasogare.imasy.or.jp> <19990213153958.2977.rocketmail@send1e.yahoomail.com> Date: Sun, 14 Feb 1999 14:04:39 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199902141646.BAA21353@tasogare.imasy.or.jp> Mitsuru IWASAKI writes: : Hello, I'm now working on APM code for PAO in Japan. I just looked more closely at the patches that you sent. I notice that there is different tod stuff on suspend/resume. What problem does that address? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Feb 14 13:12:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09792 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 13:12:06 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09752 for ; Sun, 14 Feb 1999 13:11:59 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id OAA22260; Sun, 14 Feb 1999 14:11:27 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA22337; Sun, 14 Feb 1999 14:11:24 -0700 Date: Sun, 14 Feb 1999 14:11:24 -0700 Message-Id: <199902142111.OAA22337@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: Mitsuru IWASAKI , Valentin Shopov , mobile@FreeBSD.ORG, Nate Williams Subject: Re: apm & current In-Reply-To: <199902142102.OAA32088@harmony.village.org> References: <199902141646.BAA21353@tasogare.imasy.or.jp> <19990213153958.2977.rocketmail@send1e.yahoomail.com> <199902142102.OAA32088@harmony.village.org> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > : So, now I'm going to commit version checking code just before > : calling apm_bios_call() in /sys/i386/apm/apm.c into PAO3 CVS repository. > > These patches look basically good. I'll integrate them when I have a > chance. The only issue I have is the plethora of 'options'. There's got to be a better way of configuring the apm device, and adding more options is *NOT* the way to do it. Also, last I looked (quite a while ago, just before APM 1.2 was standardized) the PAO code did not follow the APM specifications when probing. Some of this code was merged into the tree by PHK in Rev 1.55, but I quit arguing about it. This might explain why APM 1.2 commands cause the system to fail, although I'm not sure how they are implemented in the code. I think the patch could make this checking much easier by adding a variable to softc stating the version. That way the check is very simple instead of the complicated way it's done now. In other words, I don't think the patches as sent are very clean, although the functionality in them may be correct. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Feb 14 13:29:18 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11753 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 13:29:18 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from dingo.cdrom.com (castles146.castles.com [208.214.165.146]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11748 for ; Sun, 14 Feb 1999 13:29:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA05491; Sun, 14 Feb 1999 13:24:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902142124.NAA05491@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh cc: Mitsuru IWASAKI , Valentin Shopov , mobile@FreeBSD.ORG, Nate Williams Subject: Re: apm & current In-reply-to: Your message of "Sun, 14 Feb 1999 14:02:06 MST." <199902142102.OAA32088@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Feb 1999 13:24:43 -0800 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > : Adding to this, I noticed many other problems in apm code, such as > : - Fixed segment description for APM. The limit granularity should be > : specified in bytes, not pages. > > This looks good. I curse myself for missing the patch here. The segment limits are only ever specified in bytes as far as I can tell; we should be using vm86 all the time to get the APM information now. > : - Try to limit the number of apm_bios_call() executing to only one > : at the same time, watching busy state made by previous call and > : waiting if necessary. > > I wonder how this can happen, but it couldn't hurt. It can't happen, until the SMP giant kernel lock goes away, and at that point it should be fixed to use a suitable SMP locking construct. Don't add any other code to obfuscate this. > : - Made apm_suspend() and apm_standby() be invoked by apm_timeout() in order to > : obtain stablities. > > What stabilities are these? I'm curious. Likewise. I'm not sure that hanging these off apm_timeout is bad, but I'm puzzled as to what this hopes to gain. It strikes me that this may result in pending disk I/O etc. which will be lost by the suspend/ standby. > : - Added adjustment for segment size limits informed by APM BIOS. Following > : patch for apm_init.S and make in /sys/i386/apm/apm_init/ to generate > : apm_init.inc are required if VM86 isn't enabled in your kernel. > > These look good to me. They're redundant; vm86 should be non-optional. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Feb 14 20:39:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29324 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 20:39:01 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29319 for ; Sun, 14 Feb 1999 20:38:59 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (ppp2.imasy.or.jp [202.227.24.12]) by tasogare.imasy.or.jp (8.9.3+3.1W/3.7W-tasogare/smtpfeed 0.92) with ESMTP id NAA07446; Mon, 15 Feb 1999 13:38:44 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199902150438.NAA07446@tasogare.imasy.or.jp> To: mike@smith.net.au Cc: imp@village.org, iwasaki@jp.FreeBSD.org, valsho@yahoo.com, mobile@FreeBSD.ORG, nate@mt.sri.com Subject: Re: apm & current In-Reply-To: Your message of "Sun, 14 Feb 1999 13:24:43 -0800" <199902142124.NAA05491@dingo.cdrom.com> References: <199902142124.NAA05491@dingo.cdrom.com> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 15 Feb 1999 13:36:17 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 89 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > : Adding to this, I noticed many other problems in apm code, such as > > : - Fixed segment description for APM. The limit granularity should be > > : specified in bytes, not pages. > > > > This looks good. > > I curse myself for missing the patch here. The segment limits are only > ever specified in bytes as far as I can tell; we should be using vm86 > all the time to get the APM information now. The proper way to fix this is to correct APM entry of gdt_segs[] in /sys/i386/i386/machdep.c, I think. > > : - Try to limit the number of apm_bios_call() executing to only one > > : at the same time, watching busy state made by previous call and > > : waiting if necessary. > > > > I wonder how this can happen, but it couldn't hurt. > > It can't happen, until the SMP giant kernel lock goes away, and at that > point it should be fixed to use a suitable SMP locking construct. > Don't add any other code to obfuscate this. The APM BIOS calls invoked by apm_timeout() every seconds VS BIOS calls via ioctl invoked by other APM application like wmapm (WindowMaker stuff) or apm(8) seem to bump, but it is no serious matter as Warner Losh mentioned. I saw this symptom on 2.2.8 with PAO, but never seen on 3.0 so far. If you want see this, please try to run this script as many as possible and tail -f /var/log/messages with the original code :-) #!/bin/sh while true do apm > /dev/null & done > > : - Made apm_suspend() and apm_standby() be invoked by apm_timeout() in order to > > : obtain stablities. > > > > What stabilities are these? I'm curious. > > Likewise. I'm not sure that hanging these off apm_timeout is bad, but > I'm puzzled as to what this hopes to gain. It strikes me that this > may result in pending disk I/O etc. which will be lost by the suspend/ > standby. Actually, these changes was started from standby. All of our laptops (Sharp PC-9329T, Toshiba SS3010 and Hitachi Chandra2) could not change to standby state all the time, like apm -Z -> LCD blinking 2 or 3 times -> resume immediately. We made alot of try & errors, and found out one of the solutions, to invoked by apm_timeout() in kernel has some advantages against APM BIOS call directry via ioctl. I don't think this is the best solution, there may be better ways. On suspend, some machies (DEC HiNote Ultra II. etc) had problem with resume from suspend. After apm -z, pressing resume button caused power off the entire system, never resumed :-( We couldn't see why this happened, but after made fix suspend code this problem has gone. The cause is still unkown... # I guess it related with i/o interrupt? Anyway, now apm -Z VS PMEV_STANDBYREQ event, apm -z VS PMEV_STANDBYREQ or some events are handled equally by APM device driver (I think that is the point). > > : - Added adjustment for segment size limits informed by APM BIOS. Following > > : patch for apm_init.S and make in /sys/i386/apm/apm_init/ to generate > > : apm_init.inc are required if VM86 isn't enabled in your kernel. > > > > These look good to me. > > They're redundant; vm86 should be non-optional. I think so too on 3.0/4.0, but 2.2.8... I believe that vm86 provide alot of advantage against apm_init.S especially on probing APM BIOS and debugging. Could you understand what I tried to say? Sorry for my poor english. # BTW, I'm quite new for PAO code :-) , don't know # well the history and technical details on PAO, # so please don't give me quiestions on this point. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Feb 14 20:55:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00778 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 20:55:17 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from dingo.cdrom.com (castles146.castles.com [208.214.165.146]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00771 for ; Sun, 14 Feb 1999 20:55:15 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id UAA07920; Sun, 14 Feb 1999 20:50:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902150450.UAA07920@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mitsuru IWASAKI cc: mike@smith.net.au, imp@village.org, valsho@yahoo.com, mobile@FreeBSD.ORG, nate@mt.sri.com Subject: Re: apm & current In-reply-to: Your message of "Mon, 15 Feb 1999 13:36:17 +0900." <199902150438.NAA07446@tasogare.imasy.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Feb 1999 20:50:25 -0800 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > : Adding to this, I noticed many other problems in apm code, such as > > > : - Fixed segment description for APM. The limit granularity should be > > > : specified in bytes, not pages. > > > > > > This looks good. > > > > I curse myself for missing the patch here. The segment limits are only > > ever specified in bytes as far as I can tell; we should be using vm86 > > all the time to get the APM information now. > > The proper way to fix this is to correct APM entry of > gdt_segs[] in /sys/i386/i386/machdep.c, I think. The APM segments are correctly set up in the #ifdef VM86 case in apmprobe. They definitely should not be set up anywhere outside of the APM code. > > > : - Try to limit the number of apm_bios_call() executing to only one > > > : at the same time, watching busy state made by previous call and > > > : waiting if necessary. > > > > > > I wonder how this can happen, but it couldn't hurt. > > > > It can't happen, until the SMP giant kernel lock goes away, and at that > > point it should be fixed to use a suitable SMP locking construct. > > Don't add any other code to obfuscate this. > > The APM BIOS calls invoked by apm_timeout() every seconds > VS BIOS calls via ioctl invoked by other APM application > like wmapm (WindowMaker stuff) or apm(8) seem to bump, > but it is no serious matter as Warner Losh mentioned. > I saw this symptom on 2.2.8 with PAO, but never seen > on 3.0 so far. Ah, you're concerned with apm_bios_call not being reentrant. Understood, and yes, it should use a simple lock and sleep on it. > > > : - Made apm_suspend() and apm_standby() be invoked by apm_timeout() in order to > > > : obtain stablities. > > > > > > What stabilities are these? I'm curious. > > > > Likewise. I'm not sure that hanging these off apm_timeout is bad, but > > I'm puzzled as to what this hopes to gain. It strikes me that this > > may result in pending disk I/O etc. which will be lost by the suspend/ > > standby. > > Actually, these changes was started from standby. All of our > laptops (Sharp PC-9329T, Toshiba SS3010 and Hitachi Chandra2) > could not change to standby state all the time, like > apm -Z -> LCD blinking 2 or 3 times -> resume immediately. > We made alot of try & errors, and found out one of the solutions, > to invoked by apm_timeout() in kernel has some advantages against > APM BIOS call directry via ioctl. > I don't think this is the best solution, there may be better ways. I'm primarily concerned with I/O that may be pending when the timeout occurs. I think that the suspend operation should spin waiting for I/O that's in progress to complete. > Could you understand what I tried to say? > Sorry for my poor english. No problems at all, and thankyou very much for taking the effort to work on this code and talk about it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Feb 14 20:57:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA01007 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 20:57:47 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from sloth.cs.unm.edu (sloth.cs.unm.edu [198.59.151.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA00994 for ; Sun, 14 Feb 1999 20:57:44 -0800 (PST) (envelope-from colinj@cs.unm.edu) Received: from waimea.cs.unm.edu ([198.83.92.103]) by sloth.cs.unm.edu with esmtp (Exim 2.10 #1) id 10CG6N-0001rp-00 for freebsd-mobile@freebsd.org; Sun, 14 Feb 1999 21:57:47 -0700 Received: from localhost (colinj@localhost) by waimea.cs.unm.edu (980427.SGI.8.8.8/8.8.8) with ESMTP id VAA46123 for ; Sun, 14 Feb 1999 21:57:40 -0700 (MST) (envelope-from colinj@cs.unm.edu) X-Authentication-Warning: waimea.cs.unm.edu: colinj owned process doing -bs Date: Sun, 14 Feb 1999 21:57:39 -0700 From: Colin Eric Johnson To: freebsd-mobile@FreeBSD.ORG Subject: apm and -stable Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm running -stable and I'm having some trouble with apm. I can get things to suspend fine if I do not have any PCMCIA cards in the machine. If I do have a pc-card in then the machine won't suspend and eventually comes back up. This is the case if I don't have X running. If I do have X running then my ability to suspend is mixed all of the time, that is, I get the same behavior if a pc-card is in and a good suspension when no card is in only some of the time. Either the machine won't suspend at all or it won't come back from being suspended. My attempts to power off with halt -p and shutdown -p always end up with a "press any key to reboot" message instead of powering the machine down. So, what am I doing wrong? This is on a Dell Lattitude CPi here's the line from my kernel config device apm0 at isa? flags 0x31 # Advanced Power Management and from rc.conf apm_enable="YES" # Set to YES if you want APM enabled. uname -a and dmesg follow: trurl 6 % uname -a FreeBSD trurl.lternet.edu 3.1-BETA FreeBSD 3.1-BETA #1: Wed Feb 10 21:13:59 MST 1999 colinj@trurl.lternet.edu:/usr/src/sys/compile/TRURL i386 trurl 5 % dmesg Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-BETA #1: Wed Feb 10 21:13:59 MST 1999 colinj@trurl.lternet.edu:/usr/src/sys/compile/TRURL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (267.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping=0 Features=0x183f9ff> real memory = 134217728 (131072K bytes) avail memory = 127852544 (124856K bytes) Preloaded elf kernel "kernel" at 0xf0299000. Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 vga0: rev 0x01 int a irq 11 on pci0.2.0 pcic0: rev 0x01 int a irq 11 on pci0.3.0 pcic1: rev 0x01 int b irq 11 on pci0.3.1 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip2: rev 0x01 on pci0.7.3 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface pcm0 at 0x52c irq 5 drq 1 flags 0xa613 on isa mss_attach 0 at 0x52c irq 5 dma 1:3 flags 0xa613 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, intr, dma, iordis atapi1.0: unknown phase atapi1.0: unknown phase atapi1.0: unknown phase atapi1.0: unknown phase atapi1.0: unknown phase ep0 not found at 0x300 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface apm0 flags 0x31 on isa apm: found APM BIOS version 1.2 PC-Card VLSI 82C146 (5 mem & 2 I/O windows) pcic: controller irq 3 Initializing PC-card drivers: ep changing root device to wd0s2a Card inserted, slot 0 sio3: type 16550A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Feb 14 23:00:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14441 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 23:00:21 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from hunter.Sisis.de (hunter.Sisis.de [193.31.11.194]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA14432 for ; Sun, 14 Feb 1999 23:00:15 -0800 (PST) (envelope-from Matthias.Apitz@Sisis.de) Received: (from mail@localhost) by hunter.Sisis.de (8.6.9/8.6.12) id IAA05053 for ; Mon, 15 Feb 1999 08:04:08 +0100 Received: from hermes.sisis.de(193.31.10.38) by hunter.Sisis.de via smap (V1.3) id sma005051; Mon Feb 15 08:04:03 1999 Received: from almare.Sisis.de (almare.sisis.de [193.31.10.40]) by hermes.sisis.de (8.8.8/8.8.8) with ESMTP id IAA08500; Mon, 15 Feb 1999 08:03:35 +0100 (CET) (envelope-from guru@almare.Sisis.de) Received: (from guru@localhost) by mail.sisis.de (8.8.8/8.8.8) id HAA01617; Mon, 15 Feb 1999 07:58:36 +0100 (CET) (envelope-from guru) Message-ID: <19990215075835.40475@sisis.de> Date: Mon, 15 Feb 1999 07:58:35 +0100 From: Matthias Apitz To: Steve Emmert Cc: freebsd-mobile@FreeBSD.ORG, Nate Williams Subject: Re: O2 Micro OZ6832/6833 pci-cardbus controller References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=FCuugMFkClbJLl1L X-Mailer: Mutt 0.84e In-Reply-To: ; from Steve Emmert on Sat, Feb 13, 1999 at 10:48:37AM -0800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii On Sat, Feb 13, 1999 at 10:48:37AM -0800, Steve Emmert wrote: > I have recently purchased an IBM Thinkpad that has a O2 Micro- > OZ6832/6833 pci-cardbus controller. I see from the list archives > that there is a patch out there to get this controller working. > Could some kind person E-mail me the patch or direct me to a > site where i could download it. My Thinkpad is running 3.1- > BETA if that makes a difference. Hi Steve, attached below is my patch for O2Micro's OZ6832 CardBus controller. The diff is against 2.2.7 and I don't know if this will work with 3.1 and your 6833 too. Please check it out and let me and the list know. There is also a trick or hack used to identify the chip. Check the comments for details and it may occur that this test will fail for your chip anyway -- so play with it / change it. A better solution should be worked out... Hope it helps. matthias -- firm: matthias.apitz@sisis.de [voc:+49 89 61308 351, fax: +49 89 61308 188] priv: guru@thias.muc.de WWW: http://www.sisis.de/~guru/ Give me UNIX or give me a typewriter. --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="OZ6832.diff" *** pci/pcic_p.h.orig Sat Feb 7 21:38:58 1998 --- pci/pcic_p.h Thu Apr 16 08:00:14 1998 *************** *** 35,40 **** --- 35,41 ---- #define PCI_DEVICE_ID_PCIC_O2MICRO 0x673A1217ul #define PCI_DEVICE_ID_PCIC_TI1130 0xAC12104Cul #define PCI_DEVICE_ID_PCIC_TI1131 0xAC15104Cul + #define PCI_DEVICE_ID_PCIC_OZ6832 0x68321217ul /* CL-PD6832 CardBus defines */ #define CLPD6832_IO_BASE0 0x002c *************** *** 52,54 **** --- 53,73 ---- #define CLPD6832_NUM_REGS 2 /* End of CL-PD6832 defines */ + + /* O2Micro OZ6832 CardBus defines */ + /* matthias.apitz@sisis.de */ + + #define OZ6832_IO_BASE0 0x002c + #define OZ6832_IO_LIMIT0 0x0030 + #define OZ6832_IO_BASE1 0x0034 + #define OZ6832_IO_LIMIT1 0x0038 + #define OZ6832_BRIDGE_CONTROL 0x003c + #define OZ6832_LEGACY_16BIT_IOADDR 0x0044 + + /* O2Micro OZ6832 Configuration constants */ + #define OZ6832_BCR_ISA_IRQ 0x00800000 + #define OZ6832_COMMAND_DEFAULTS 0x00000007 + + #define OZ6832_NUM_REGS 2 + + /* End of O2Micro OZ6832 CardBus defines */ *** pci/pcic_p.c.orig Sat Feb 7 21:42:29 1998 --- pci/pcic_p.c Fri Apr 17 07:47:37 1998 *************** *** 29,34 **** --- 29,40 ---- * $Id: pcic_p.c,v 1.4.2.2 1998/02/07 20:42:29 nate Exp $ */ + /* + * modified for O2Micro's OZ6832 PCI to CardBus controller + * by Matthias Apitz + * April, 1998 + */ + #include "pci.h" #if NPCI > 0 *************** *** 48,53 **** --- 54,61 ---- static void pcic_pci_attach(pcici_t, int); static void pd6832_legacy_init(pcici_t tag, int unit); + static void oz6832_legacy_init(pcici_t tag, int unit); + static void pcic_pci_printConfig(pcici_t tag, char *s); static struct pci_device pcic_pci_driver = { "pcic", *************** *** 66,71 **** --- 74,80 ---- static char * pcic_pci_probe(pcici_t tag, pcidi_t type) { + switch (type) { case PCI_DEVICE_ID_PCIC_CLPD6729: return ("Cirrus Logic PD6729/6730 PC-Card Controller"); *************** *** 75,80 **** --- 84,91 ---- return ("TI 1130 PCMCIA/CardBus Bridge"); case PCI_DEVICE_ID_PCIC_TI1131: return ("TI 1131 PCI to PCMCIA/CardBus bridge"); + case PCI_DEVICE_ID_PCIC_OZ6832: + return ("O2Micro OZ6832 CardBus bridge"); default: break; } *************** *** 84,90 **** /* * General PCI based card dispatch routine. Right now ! * it only understands the CL-PD6832. */ static void pcic_pci_attach(pcici_t config_id, int unit) --- 95,103 ---- /* * General PCI based card dispatch routine. Right now ! * it only understands the follwoing chips: ! * Cirrus Logic PD6832 ! * O2Micro OZ6832 */ static void pcic_pci_attach(pcici_t config_id, int unit) *************** *** 97,102 **** --- 110,124 ---- case PCI_DEVICE_ID_PCIC_CLPD6832: pd6832_legacy_init(config_id, unit); break; + case PCI_DEVICE_ID_PCIC_OZ6832: + oz6832_legacy_init(config_id, unit); + /* + * no way to print the CardBus soccket regs and + * ExCA regs here for the moment -- we skip the rest + * of the function; + */ + return; + break; } if (bootverbose) { *************** *** 192,196 **** --- 214,306 ---- if (bootverbose) printf("CardBus: Legacy PC-card 16bit I/O address [0x%x]\n", io_port); + } + + /* + * Set up the O2Mirco OZ6832 to look like a ISA based PCMCIA chip (a + * PD672X). This routine is called once per PCMCIA socket. + */ + static void + oz6832_legacy_init(pcici_t tag, int unit) + { + u_long bcr; /* to set interrupts */ + u_short io_port; /* the io_port to map this slot on */ + static int num6832 = 0; /* The number of 6832s initialized */ + + /* + * Some BIOS leave the legacy address uninitialized. This + * insures that the PD6832 puts itself where the driver will + * look. We assume that multiple 6832's should be laid out + * sequentially. We only initialize the first socket's legacy port, + * the other is a dummy. + */ + if (bootverbose) + pcic_pci_printConfig(tag, "as got from BIOS"); + + io_port = PCIC_INDEX_0 + num6832 * OZ6832_NUM_REGS; + if (unit == 0) { + pci_conf_write(tag, OZ6832_LEGACY_16BIT_IOADDR, + io_port & ~PCI_MAP_IO); + } + + /* + * I think this should be a call to pci_map_port, but that + * routine won't map regiaters above 0x28, and the register we + * need to map is 0x44. + */ + + io_port = pci_conf_read(tag, OZ6832_LEGACY_16BIT_IOADDR) + & ~PCI_MAP_IO; + + /* + * Set default operating mode (I/O port space) and allocate + * this socket to the current unit. + */ + + pci_conf_write(tag, PCI_COMMAND_STATUS_REG, OZ6832_COMMAND_DEFAULTS); + + /* + * Set up the card inserted/card removed interrupts to come + * through the isa IRQ. + */ + bcr = pci_conf_read(tag, OZ6832_BRIDGE_CONTROL); + bcr |= OZ6832_BCR_ISA_IRQ; + pci_conf_write(tag, OZ6832_BRIDGE_CONTROL, bcr); + + /* After initializing 2 sockets, the chip is fully configured */ + if (unit == 1) + num6832++; + + if (bootverbose) { + pcic_pci_printConfig(tag, "after oz6832_legacy_init"); + printf("CardBus: Legacy PC-card 16bit I/O address [0x%x]\n", + io_port); + } + } + + /* + * Dump the PCI Config Space + */ + static void + pcic_pci_printConfig(pcici_t config_id, char *s) + { + int i, j; + u_char *p; + u_long *pl; + + printf("PCI Config space %s:\n", s); + for (j = 0; j < 0x98; j += 16) { + printf("%02x: ", j); + for (i = 0; i < 16; i += 4) + printf(" %08x", pci_conf_read(config_id, i+j)); + printf("\n"); + } + /* + * the rest of the function is nonsense at the moment + * because we have no idea how to access the + * Cardbus Socket regs because the addr in 0x10 is NULL + */ + printf("Cardbus Socket registers not available.\n"); + } #endif /* NPCI > 0 */ *** pccard/i82365.h.orig Thu Oct 23 20:44:06 1997 --- pccard/i82365.h Fri Apr 17 17:00:17 1998 *************** *** 45,50 **** --- 45,51 ---- #define PCIC_IBM_KING 9 /* IBM KING PCMCIA Controller */ #define PCIC_PC98 10 /* NEC PC98 PCMCIA Controller */ #define PCIC_TI1130 11 /* TI PCI1130 CardBus */ + #define PCIC_OZ6832 12 /* O2Micro 6832 CardBus */ /* * Address of the controllers. Each controller can manage *************** *** 87,92 **** --- 88,95 ---- #define PCIC_TIME_CMD1 0x3e #define PCIC_TIME_RECOV1 0x3f + #define PCIC_O2MICRO_MCTRL_B 0x39 /* O2Micro Mode Control Register B */ + #define PCIC_SLOT_SIZE 0x40 /* Size of register set for one slot */ /* Now register bits, ordered by reg # */ *************** *** 94,99 **** --- 97,103 ---- /* For Identification and Revision (PCIC_ID_REV) */ #define PCIC_INTEL0 0x82 /* Intel 82365SL Rev. 0; Both Memory and I/O */ #define PCIC_INTEL1 0x83 /* Intel 82365SL Rev. 1; Both Memory and I/O */ + #define PCIC_O2MICRO 0x87 /* O2Micro OZ6832; Both Memory and I/O */ #define PCIC_IBM1 0x88 /* IBM PCIC clone; Both Memory and I/O */ #define PCIC_IBM2 0x89 /* IBM PCIC clone; Both Memory and I/O */ #define PCIC_IBM3 0x8a /* IBM KING PCIC clone; Both Memory and I/O */ *** pccard/pcic.c.orig Sat Nov 15 15:11:34 1997 --- pccard/pcic.c Sat Apr 18 07:58:27 1998 *************** *** 33,38 **** --- 33,45 ---- * by Noriyuki Hosobuchi */ + /* + * modified for O2Micro's OZ6832 PCI to CardBus controller + * by Matthias Apitz + * April, 1998 + */ + + #include #include #include *************** *** 90,95 **** --- 97,103 ---- static unsigned pcic_imask; static struct slot_ctrl cinfo; + static void dump_register_table(struct pcic_slot *sp, char *s); /* * Internal inline functions for accessing the PCIC. *************** *** 538,543 **** --- 546,562 ---- * of slot 1. Assume it's the only PCIC whose vendor ID is 0x84, * contact Nate Williams if incorrect. */ + + /* + * O2Micro's OZ6832 comes along with a vendor ID 0x82 and + * mostly works like an Intel clone. You may detect it as + * an OZ6832 by switching on the O2Micro-mode (see below) + * and see if the vendor ID changes to 0x87, contact Matthias + * Apitz if this doesn't work for you. The + * PCIC can't steer out interupts for card status changes, only + * for I/O the steering does work and this also stops to + * work if you enable irq steering for status changes. sigh. + */ int pcic_probe(void) { *************** *** 546,551 **** --- 565,572 ---- struct slot *slt; struct pcic_slot *sp; unsigned char c; + unsigned char o2mode; + unsigned char save; static int maybe_vlsi = 0; /* Determine the list of free interrupts */ *************** *** 610,616 **** --- 631,668 ---- * 82365 or clones. */ case 0x82: + /* + * first let's look for an O2Micro OZ6832 CardBus + * controller... + * + * setting the two bits [1:0] in the register + * "O2Micro control B" at offset 39h to the value + * 0x02 should switch the PCIC_ID_REV from 0x82 + * to 0x87 (PCIC_O2MICRO) + */ + #ifdef PCIC_DEBUG + dump_register_table(sp, "pcic_probe() for O2Micro"); + #endif + save = sp->getb(sp, PCIC_O2MICRO_MCTRL_B); + clrb(sp, PCIC_O2MICRO_MCTRL_B, 0x01); + setb(sp, PCIC_O2MICRO_MCTRL_B, 0x02); + o2mode = sp->getb(sp, PCIC_ID_REV); + /* restore the old value and see what o2mode has ... */ + sp->putb(sp, PCIC_O2MICRO_MCTRL_B, save); + if(o2mode == PCIC_O2MICRO) { + printf("pcic: found an O2Micro OZ6832 CardBus controller\n"); + printf("pcic: PCIC_ID_REV was switchable to 0x%x\n", o2mode); + sp->controller = PCIC_OZ6832; + sp->revision = c & 1; + break; + } + /* + * ... fall through if not an OZ6832 + */ case 0x83: + #ifdef PCIC_DEBUG + dump_register_table(sp, "pcic_probe() for 82365 clone"); + #endif sp->controller = PCIC_I82365; sp->revision = c & 1; /* *************** *** 670,675 **** --- 722,730 ---- } } switch(sp->controller) { + case PCIC_OZ6832: + cinfo.name = "O2Micro OZ6832"; + break; case PCIC_I82365: cinfo.name = "Intel 82365"; break; *************** *** 703,712 **** } #ifndef PCIC_NOCLRREGS /* ! * clear out the registers. */ ! for (i = 2; i < 0x40; i++) ! sp->putb(sp, i, 0); #endif /* PCIC_NOCLRREGS */ /* * OK it seems we have a PCIC or lookalike. --- 758,770 ---- } #ifndef PCIC_NOCLRREGS /* ! * clear out the registers if no O2Micro chip */ ! if(sp->controller != PCIC_OZ6832) { ! printf("pcic: zero out for all ExCA regs\n"); ! for (i = 2; i < 0x40; i++) ! sp->putb(sp, i, 0); ! } #endif /* PCIC_NOCLRREGS */ /* * OK it seems we have a PCIC or lookalike. *************** *** 754,763 **** pccard_event(sp->slt, card_inserted); } /* ! * Assign IRQ for slot changes */ ! if (pcic_irq > 0) ! sp->putb(sp, PCIC_STAT_INT, (pcic_irq << 4) | 0xF); } #ifdef PC98 if (validslots == 0) { --- 812,838 ---- pccard_event(sp->slt, card_inserted); } /* ! * Assign IRQ for slot changes ! * ! * the folks @ o2micro.com say: we can't generate ! * ISA IRQ's for status changes in OZ6832 ... ! * for the moment we simple set PCIC_STAT_INT to 0xf ! * and rely on the polling in the driver; */ ! if (pcic_irq > 0) { ! if(sp->controller == PCIC_OZ6832) { ! printf("pcic: OZ6832 can't steer irqs for slot changes -- irq unused\n"); ! sp->putb(sp, PCIC_STAT_INT, 0x0f); ! } ! else ! sp->putb(sp, PCIC_STAT_INT, (pcic_irq << 4) | 0xF); ! } ! /* ! * Dump the ExCA after IRQ for slot changes ! */ ! #ifdef PCIC_DEBUG ! dump_register_table(sp, "set PCIC_STAT_INT"); ! #endif } #ifdef PC98 if (validslots == 0) { *************** *** 972,982 **** return; } #endif if (irq == 0) clrb(sp, PCIC_INT_GEN, 0xF); ! else sp->putb(sp, PCIC_INT_GEN, ! (sp->getb(sp, PCIC_INT_GEN) & 0xF0) | irq); } /* --- 1047,1065 ---- return; } #endif + #ifdef PCIC_DEBUG + printf("pcic: irq=%d mapped.\n", irq); + #endif if (irq == 0) clrb(sp, PCIC_INT_GEN, 0xF); ! else { sp->putb(sp, PCIC_INT_GEN, ! (sp->getb(sp, PCIC_INT_GEN) & 0xF0) | irq ); ! } ! #ifdef PCIC_DEBUG ! dump_register_table(sp, "pcic_mapirq()"); ! #endif ! } /* *************** *** 1051,1056 **** --- 1134,1140 ---- /* * PCIC timer, it seems that we lose interrupts sometimes + * and we don't get interrupts for the OZ6832 at all ... * so poll just in case... */ static void *************** *** 1073,1078 **** --- 1157,1163 ---- unsigned char chg; struct pcic_slot *sp = pcic_slots; + #ifdef PC98 if (sp->controller == PCIC_PC98) { slot = 0; *************** *** 1112,1121 **** pcic_resume(struct slot *slt) { struct pcic_slot *sp = slt->cdata; if (pcic_irq > 0) ! sp->putb(sp, PCIC_STAT_INT, (pcic_irq << 4) | 0xF); if (sp->controller == PCIC_PD672X) { setb(sp, PCIC_MISC1, PCIC_SPKR_EN); setb(sp, PCIC_MISC2, PCIC_LPDM_EN); } } --- 1197,1234 ---- pcic_resume(struct slot *slt) { struct pcic_slot *sp = slt->cdata; + if (pcic_irq > 0) ! if(sp->controller == PCIC_OZ6832) { ! printf("pcic: OZ6832 can't steer irqs for slot changes -- irq unused\n"); ! sp->putb(sp, PCIC_STAT_INT, 0x0f); ! } ! else ! sp->putb(sp, PCIC_STAT_INT, (pcic_irq << 4) | 0xF); ! if (sp->controller == PCIC_PD672X) { setb(sp, PCIC_MISC1, PCIC_SPKR_EN); setb(sp, PCIC_MISC2, PCIC_LPDM_EN); + } + } + + + /* + * dump all ExCA registers from 800h to 83Fh + */ + void dump_register_table(struct pcic_slot *sp, char *s) + { + unsigned char c; + unsigned char *p; + unsigned char regs[16]; + int i, j; + + printf("\nExCA registers in %s:\n", s); + + for (i = 0; i < 0x40; i += 16) { + for(j=0; j < 16; j++) + regs[j] = sp->getb(sp, i+j); + p = regs; + printf("%02x: %16D\n", i, p, " "); } } --FCuugMFkClbJLl1L-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Feb 14 23:22:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17138 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 23:22:44 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA17129 for ; Sun, 14 Feb 1999 23:22:42 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 10CIMR-0004TR-00; Mon, 15 Feb 1999 00:22:31 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.2/8.8.3) with ESMTP id AAA35191; Mon, 15 Feb 1999 00:24:47 -0700 (MST) Message-Id: <199902150724.AAA35191@harmony.village.org> To: Mitsuru IWASAKI Subject: Re: apm & current Cc: mike@smith.net.au, valsho@yahoo.com, mobile@FreeBSD.ORG, nate@mt.sri.com In-reply-to: Your message of "Mon, 15 Feb 1999 13:36:17 +0900." <199902150438.NAA07446@tasogare.imasy.or.jp> References: <199902150438.NAA07446@tasogare.imasy.or.jp> <199902142124.NAA05491@dingo.cdrom.com> Date: Mon, 15 Feb 1999 00:24:46 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199902150438.NAA07446@tasogare.imasy.or.jp> Mitsuru IWASAKI writes: : If you want see this, please try to run this script : as many as possible and tail -f /var/log/messages : with the original code :-) : : #!/bin/sh : while true : do : apm > /dev/null & : done I'll give that a try. : Actually, these changes was started from standby. All of our : laptops (Sharp PC-9329T, Toshiba SS3010 and Hitachi Chandra2) could : not change to standby state all the time, like apm -Z -> LCD : blinking 2 or 3 times -> resume immediately. We made alot of try & : errors, and found out one of the solutions, to invoked by : apm_timeout() in kernel has some advantages against APM BIOS call : directry via ioctl. I don't think this is the best solution, there : may be better ways. OK. I've seen this too (the apm -Z resuming "soon"). I'm not sure what caused that. I suspected at the time it was an interrupt or timeout that caused the wakeup. Maybe the right solution would be to mask the timeout interrupts before suspending, then unmask them after we get back from a suspend. I think that there is a race here that the delay just codes around. Just a thought. Was that one of the things that you tried? Or maybe we need just an splhigh() in apm_suspend: Instead of: if (apm_int(&eax, &ebx, &ecx, &edx)) { printf("Entire system suspend failure: errcode = %ld\n", 0xff & (eax >> 8)); return 1; } return 0; have unsigned s = splhigh(); if (apm_int(&eax, &ebx, &ecx, &edx)) { printf("Entire system suspend failure: errcode = %ld\n", 0xff & (eax >> 8)); splx(s); return 1; } splx(s); return 0; This might be a much simpler solution. I don't recall, howeer, if splhigh() really disables interrupts or just defers them until later. It might be a rare case for cli/sti: __asm __volatile("cli" : : : "memory"); if (apm_int(&eax, &ebx, &ecx, &edx)) { printf("Entire system suspend failure: errcode = %ld\n", 0xff & (eax >> 8)); __asm __volatile("sti" : : : "memory"); return 1; } __asm __volatile("sti" : : : "memory"); return 0; But I worry that not all APM bioses can handle waking up from this condition. The APM 1.2 document is silent on this issue, as far as I can tell... : On suspend, some machies (DEC HiNote Ultra II. etc) had problem : with resume from suspend. After apm -z, pressing resume button : caused power off the entire system, never resumed :-( : We couldn't see why this happened, but after made fix suspend : code this problem has gone. The cause is still unkown... : # I guess it related with i/o interrupt? That's my guess also. : Anyway, now apm -Z VS PMEV_STANDBYREQ event, apm -z VS : PMEV_STANDBYREQ or some events are handled equally : by APM device driver (I think that is the point). I'm sorry, but I'm not sure what you are getting at here. : I believe that vm86 provide alot of advantage against : apm_init.S especially on probing APM BIOS and debugging. Yes. It does. I've found things are more stable. : Could you understand what I tried to say? : Sorry for my poor english. Yes. You have communicated well enough that I understand most of what the code changes are trying to accomplish. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sun Feb 14 23:24:43 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA17421 for freebsd-mobile-outgoing; Sun, 14 Feb 1999 23:24:43 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA17415 for ; Sun, 14 Feb 1999 23:24:41 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 10CIOS-0004TT-00; Mon, 15 Feb 1999 00:24:36 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.2/8.8.3) with ESMTP id AAA35205; Mon, 15 Feb 1999 00:26:52 -0700 (MST) Message-Id: <199902150726.AAA35205@harmony.village.org> To: Mike Smith Subject: Re: apm & current Cc: Mitsuru IWASAKI , valsho@yahoo.com, mobile@FreeBSD.ORG, nate@mt.sri.com In-reply-to: Your message of "Sun, 14 Feb 1999 20:50:25 PST." <199902150450.UAA07920@dingo.cdrom.com> References: <199902150450.UAA07920@dingo.cdrom.com> Date: Mon, 15 Feb 1999 00:26:52 -0700 From: Warner Losh Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199902150450.UAA07920@dingo.cdrom.com> Mike Smith writes: : I'm primarily concerned with I/O that may be pending when the timeout : occurs. I think that the suspend operation should spin waiting for : I/O that's in progress to complete. Yes. I hadn't thought of that. There are some wrinkles that we'll have to deal with. The APM 1.2 spec says we need to continue polling once per second while we're doing a suspend or standby operation to ensure that a critical suspend event doesn't come in. If it does, we have 5 seconds to acknowledge it (which will cause an immediate suspend if I read correctly). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Mon Feb 15 11:18:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17052 for freebsd-mobile-outgoing; Mon, 15 Feb 1999 11:18:26 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17031 for ; Mon, 15 Feb 1999 11:18:23 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (ppp13.imasy.or.jp [202.227.24.23]) by tasogare.imasy.or.jp (8.9.3+3.1W/3.7W-tasogare/smtpfeed 0.92) with ESMTP id EAA25436; Tue, 16 Feb 1999 04:18:18 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199902151918.EAA25436@tasogare.imasy.or.jp> To: imp@village.org Cc: iwasaki@jp.FreeBSD.org, mike@smith.net.au, valsho@yahoo.com, mobile@FreeBSD.ORG, nate@mt.sri.com Subject: Re: apm & current In-Reply-To: Your message of "Mon, 15 Feb 1999 00:24:46 -0700" <199902150724.AAA35191@harmony.village.org> References: <199902150724.AAA35191@harmony.village.org> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 16 Feb 1999 04:15:52 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 81 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just now, I understood why stanby was failed all the time, and how to change system state to standby w/o our patches. The console driver prevented our laptops from changing to standby state :-( In normal standby operation, we typed like this: % apm -Z(CR) [] <--- cursor position is here! and soon, % apm -Z % [] <--- prompt was displayed and cursor position have been moved! There was a race here. Following commands are almost equivalent to the effect of our patches from point of view of giving console driver enough time. % sleep 2 && apm -Z & Now I understand that our patch give console driver enough time to complete its process, then console driver quit disturbing standby. > the delay just codes around. Just a thought. Was that one of the > things that you tried? Or maybe we need just an splhigh() in > apm_suspend: [snip] > unsigned s = splhigh(); [snip] > __asm __volatile("cli" : : : "memory"); Yes, I already tried both of them. Using "cli" was implemented in apm_setup.s ("pushfl", "cli", "lcall", "setc [to get carry flag value]", then "popfl"). > But I worry that not all APM bioses can handle waking up from this > condition. The APM 1.2 document is silent on this issue, as far as I > can tell... As our conclusion, this cli hack (or splhigh()) doesn't make us happy, standby was still failed. And the situation was getting worse because sometime the system froze... > : Anyway, now apm -Z VS PMEV_STANDBYREQ event, apm -z VS Sorry, typo here. > : PMEV_STANDBYREQ or some events are handled equally PMEV_SUSPENDREQ > : by APM device driver (I think that is the point). > > I'm sorry, but I'm not sure what you are getting at here. What I was trying to explain is that; There are tow ways to suspend the system as you know, one is to execute command apm -z (or zzz) which posted to APM device driver via ioctl, another is pressing hotkeys (such as Fn+F12 on my system) or APM BIOS timeout which posted to APM device driver as APM events. The standby also. However, thier proccesses are quit different; [apm -z ] -> ioctl -> apmioctl -> apm_suspend -> apm_suspend_system -> apm_int -> apm_bios_call -> [suspend] [hotkeys] -> apm_timeout -> apm_processevent -> apm_getevent -> apm_suspend -> apm_suspend_system -> apm_int -> apm_bios_call -> [suspend] The patches is trying to change these sequence, and suspend operation to be handled equally by APM driver as follows; [apm -z ] -> ioctl -> apmioctl -> apm_suspend -> [register suspend request] [hotkeys] -> apm_timeout -> apm_processevent -> apm_getevent -> apm_suspend -> [register suspend request] After register suspend request, the rest of sequence is the same; [apm_timeout] -> apm_do_suspend -> apm_suspend_system -> apm_int -> apm_bios_call -> [suspend] And, I've forgotten to tell you that when we made that patches, I referred to the APM code from NetBSD and Linux. Especially NetBSD's one gave us alot of ideas. Both of them follows this style if I remember correctly. > : I believe that vm86 provide alot of advantage against > : apm_init.S especially on probing APM BIOS and debugging. > > Yes. It does. I've found things are more stable. Oh that work was done by you, great! Thanks alot and I must respect your efforts. # What time is it? Ah, I need to go to bed!...zzz...apm -z... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 05:10:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA16310 for freebsd-mobile-outgoing; Tue, 16 Feb 1999 05:10:50 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA16304 for ; Tue, 16 Feb 1999 05:10:47 -0800 (PST) (envelope-from earnoth@UDel.Edu) Received: from localhost (earnoth@localhost) by copland.udel.edu (8.8.8/8.8.8) with ESMTP id IAA29504 for ; Tue, 16 Feb 1999 08:10:48 -0500 (EST) Date: Tue, 16 Feb 1999 08:10:48 -0500 (EST) From: Eric I Arnoth To: mobile@FreeBSD.ORG Subject: new laptop, pcmcia slots In-Reply-To: <199902150724.AAA35191@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm in the forced position at this moment to buy a new laptop, either old or low-end new. Before I do, however, I want to make certain I won't make the same mistake as I did with my current COMPAQ laptop. My current problem is that the PCCard (PCMCIA) slots are apparently proprietary in my model/make (curse Compaq to hell ;) and I have been unable to use the ethernet card (3Com 3c589D) because of either that, or plug&play issues. (On my Compaq, one cannot turn of the PnP in the BIOS.) Would everyone and anyone on the list please tell me of the laptops they are aware of, both make and model, which are PCMCIA-trouble-free? I would greatly appreciate such help, and I will be sure to consult the PAO homepage and get that list of experiences as well. Thank you kindly for your time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 05:29:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA17705 for freebsd-mobile-outgoing; Tue, 16 Feb 1999 05:29:08 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from olsen.capsl.udel.edu (olsen.capsl.udel.edu [128.4.10.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA17700 for ; Tue, 16 Feb 1999 05:29:06 -0800 (PST) (envelope-from heber@elmasri.capsl.udel.edu) Received: from elmasri.capsl.udel.edu (elmasri.capsl.udel.edu [128.4.10.24]) by olsen.capsl.udel.edu (8.9.1/8.9.1) with SMTP id IAA03485 for ; Tue, 16 Feb 1999 08:29:05 -0500 (EST) Date: Tue, 16 Feb 1999 08:29:04 -0500 (EST) From: Gerd Heber To: mobile@FreeBSD.ORG Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org folks, can anybody drop me a kernel config line (sio...) which properly detects the infrared port on a Libretto 110CT? thanks gerd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 05:37:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA18178 for freebsd-mobile-outgoing; Tue, 16 Feb 1999 05:37:08 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA18102 for ; Tue, 16 Feb 1999 05:35:53 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (tiburon [158.227.6.111]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id OAA15867 for ; Tue, 16 Feb 1999 14:35:13 +0100 (MET) Message-ID: <36C97411.EA4EF18C@we.lc.ehu.es> Date: Tue, 16 Feb 1999 14:35:13 +0100 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dept. de Electricidad y Electronica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-STABLE i386) MIME-Version: 1.0 To: freebsd-mobile@FreeBSD.ORG Subject: Is the IBM Etherjet 10/100 card supported? Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The subject says all ;-). A colleague of mine owns an IBM Thinkpad with an Etherjet 10/100 PCMCIA. This card is not detected by teh "ze" driver, nor it is listed in /etc/pccard.conf. Is this card supported by FreeBSD (plain or PAO)? TIA, -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@es.FreeBSD.ORG Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 06:37:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA24701 for freebsd-mobile-outgoing; Tue, 16 Feb 1999 06:37:29 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from ns.skylink.it (ns.skylink.it [194.177.113.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA24686 for ; Tue, 16 Feb 1999 06:37:22 -0800 (PST) (envelope-from dirkx@webweaving.org) Received: from kim.ispra.webweaving.org (va-179.skylink.it [194.177.113.179]) by ns.skylink.it (8.9.1/8.8.8) with ESMTP id PAA04589; Tue, 16 Feb 1999 15:36:39 +0100 Received: from webweaving.org (baveno.ispra.webweaving.org [10.0.0.5]) by kim.ispra.webweaving.org (8.8.8/8.8.5) with ESMTP id OAA04163; Tue, 16 Feb 1999 14:32:59 GMT X-Passed: MX on Ispra.WebWeaving.org Tue, 16 Feb 1999 14:32:59 GMT and masked X-No-Spam: Neither the receipients nor the senders email address(s) are to be used for Unsolicited (Commercial) Email without the explicit written consent of either party; as a per-message fee is incurred for inbound and outbound traffic to the originator. Posted-Date: Tue, 16 Feb 1999 14:32:59 GMT Message-ID: <36C9EF2A.61AF4459@webweaving.org> Date: Tue, 16 Feb 1999 14:20:26 -0800 From: Dirk-Willem van Gulik Reply-To: dirkx@webweaving.org Organization: WebWeaving X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: nl,en,de,it,fr MIME-Version: 1.0 To: Eric I Arnoth CC: mobile@FreeBSD.ORG Subject: Re: new laptop, pcmcia slots References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Eric I Arnoth wrote: > I'm in the forced position at this moment to buy a new laptop, either old > or low-end new. Before I do, however, I want to make certain I won't make > the same mistake as I did with my current COMPAQ laptop. My current > problem is that the PCCard (PCMCIA) slots are apparently proprietary in my > model/make (curse Compaq to hell ;) and I have been unable to use the > ethernet card (3Com 3c589D) because of either that, or plug&play issues. > (On my Compaq, one cannot turn of the PnP in the BIOS.) > > Would everyone and anyone on the list please tell me of the laptops they > are aware of, both make and model, which are PCMCIA-trouble-free? I would > greatly appreciate such help, and I will be sure to consult the PAO > homepage and get that list of experiences as well. Thank you kindly for > your time. If you go to these PAO pages, check out the survey; it is very comprehensive and quite up to date (for us europeans that is :-). http://jaz.jp.freebsd.org/PAO/PAO/docs/LAPTOP_SURVEY/LTS.txt Obviously there is a difference between FreeBSD 3, 4 support and PAO, but the differences are getting smaller all the time. Dw To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 07:02:16 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27564 for freebsd-mobile-outgoing; Tue, 16 Feb 1999 07:02:16 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from arthur.axion.bt.co.uk (arthur.axion.bt.co.uk [132.146.5.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27543 for ; Tue, 16 Feb 1999 07:02:10 -0800 (PST) (envelope-from caroline.beauchamps@bt-sys.bt.co.uk) Received: from rambo (actually rambo.futures.bt.co.uk) by arthur (local) with SMTP; Tue, 16 Feb 1999 15:01:25 +0000 Received: from mussel.futures.bt.co.uk (actually mussel) by rambo with SMTP (PP); Tue, 16 Feb 1999 15:05:36 +0000 Received: by mussel.futures.bt.co.uk with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62) id <01BE59BC.5ECB2D50@mussel.futures.bt.co.uk>; Tue, 16 Feb 1999 14:55:19 -0000 Message-ID: From: Caroline Beauchamps To: "'Eric I Arnoth'" Cc: "'mobile@FreeBSD.ORG'" Subject: RE: new laptop, pcmcia slots Date: Tue, 16 Feb 1999 15:07:08 -0000 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.996.62 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am using a Dell Latitude, and it's working fine with PCMCIA cards. good luck Regards, Caroline >---------- >From: Dirk-Willem van Gulik[SMTP:dirkx@webweaving.org] >Sent: 16 February 1999 22:20 >To: Eric I Arnoth >Cc: mobile@FreeBSD.ORG >Subject: Re: new laptop, pcmcia slots > > > >Eric I Arnoth wrote: > >> I'm in the forced position at this moment to buy a new laptop, either old >> or low-end new. Before I do, however, I want to make certain I won't make >> the same mistake as I did with my current COMPAQ laptop. My current >> problem is that the PCCard (PCMCIA) slots are apparently proprietary in my >> model/make (curse Compaq to hell ;) and I have been unable to use the >> ethernet card (3Com 3c589D) because of either that, or plug&play issues. >> (On my Compaq, one cannot turn of the PnP in the BIOS.) >> >> Would everyone and anyone on the list please tell me of the laptops they >> are aware of, both make and model, which are PCMCIA-trouble-free? I would >> greatly appreciate such help, and I will be sure to consult the PAO >> homepage and get that list of experiences as well. Thank you kindly for >> your time. > >If you go to these PAO pages, check out the survey; it is very comprehensive >and quite up to date (for us europeans that is :-). > > http://jaz.jp.freebsd.org/PAO/PAO/docs/LAPTOP_SURVEY/LTS.txt > >Obviously there is a difference between FreeBSD 3, 4 support and PAO, but >the differences are getting smaller all the time. > >Dw > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-mobile" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 11: 8:50 1999 Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21575 for ; Tue, 16 Feb 1999 11:08:47 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id LAA29080; Tue, 16 Feb 1999 11:08:58 -0800 (PST) (envelope-from ulf) Message-ID: <19990216110858.H1580@TelcoSucks.org> Date: Tue, 16 Feb 1999 11:08:58 -0800 From: Ulf Zimmermann To: Eric I Arnoth , mobile@FreeBSD.ORG Subject: Re: new laptop, pcmcia slots Reply-To: ulf@Alameda.net References: <199902150724.AAA35191@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Eric I Arnoth on Tue, Feb 16, 1999 at 08:10:48AM -0500 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Feb 16, 1999 at 08:10:48AM -0500, Eric I Arnoth wrote: > I'm in the forced position at this moment to buy a new laptop, either old > or low-end new. Before I do, however, I want to make certain I won't make > the same mistake as I did with my current COMPAQ laptop. My current > problem is that the PCCard (PCMCIA) slots are apparently proprietary in my > model/make (curse Compaq to hell ;) and I have been unable to use the > ethernet card (3Com 3c589D) because of either that, or plug&play issues. > (On my Compaq, one cannot turn of the PnP in the BIOS.) > > Would everyone and anyone on the list please tell me of the laptops they > are aware of, both make and model, which are PCMCIA-trouble-free? I would > greatly appreciate such help, and I will be sure to consult the PAO > homepage and get that list of experiences as well. Thank you kindly for > your time. I personaly liked the Hitachi M series or now the Visionbook Plus or Pro series. the M and Plus have built in 10mbit/sec PCI ethernet plus modem. the Pro has 10/100 plus modem. No PCMCIA stuff. Hardware on the M was supported last time I used it with FreeBSD. Not sure what ethernet chip is in the Plus or Pro. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 11:10: 9 1999 Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA21964 for ; Tue, 16 Feb 1999 11:10:04 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id LAA29366; Tue, 16 Feb 1999 11:09:58 -0800 (PST) (envelope-from ulf) Message-ID: <19990216110958.I1580@TelcoSucks.org> Date: Tue, 16 Feb 1999 11:09:58 -0800 From: Ulf Zimmermann To: "Jose M. Alcaide" , freebsd-mobile@FreeBSD.ORG Subject: Re: Is the IBM Etherjet 10/100 card supported? Reply-To: ulf@Alameda.net References: <36C97411.EA4EF18C@we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.93.2i In-Reply-To: <36C97411.EA4EF18C@we.lc.ehu.es>; from Jose M. Alcaide on Tue, Feb 16, 1999 at 02:35:13PM +0100 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Feb 16, 1999 at 02:35:13PM +0100, Jose M. Alcaide wrote: > The subject says all ;-). A colleague of mine owns an IBM Thinkpad > with an Etherjet 10/100 PCMCIA. This card is not detected by > teh "ze" driver, nor it is listed in /etc/pccard.conf. Is this > card supported by FreeBSD (plain or PAO)? Is it a 16 bit or a 32 bit card ? If it is 32bit, they are not supported at all. 16 bit should at least detected when insert. > > TIA, > -- JMA > ----------------------------------------------------------------------- > José Mª Alcaide | mailto:jose@we.lc.ehu.es > Universidad del País Vasco | mailto:jmas@es.FreeBSD.ORG > Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose > Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 > 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 > ----------------------------------------------------------------------- > "Go ahead... make my day." - H. Callahan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 11:31: 7 1999 Received: from isds.duke.edu (davinci.isds.duke.edu [152.3.22.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23968 for ; Tue, 16 Feb 1999 11:30:56 -0800 (PST) (envelope-from sto@stat.Duke.EDU) Received: from cayenne.isds.duke.edu (cayenne.isds.duke.edu [152.3.22.11]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id OAA14355 for ; Tue, 16 Feb 1999 14:30:55 -0500 (EST) Received: (from sto@localhost) by cayenne.isds.duke.edu (8.8.8/8.8.8) id OAA16114 for freebsd-mobile@FreeBSD.ORG; Tue, 16 Feb 1999 14:30:54 -0500 (EST) Message-ID: <19990216143052.A6818@stat.Duke.EDU> Date: Tue, 16 Feb 1999 14:30:52 -0500 From: "Sean O'Connell" To: FreeBSD mobile Subject: HP Omnibook 900 Reply-To: "Sean O'Connell" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi All- I have a couple of faculty members who are really excited about these laptops. I was wondering if anyone has had the opportunity to play with them under FreeBSD. The HP website is decidely thin on hardware info (they acutally do mention that the vid card is a 256-bit NeoMagic card), so I called the tech support number. The following is a bit sketchy (mostly because the guy wasn't too sure what I was after), but this is what they claim: Pccard controller: TI PCI 1225 Video card: NeoMagic NMG5 (2.5MB ram) Sound: 16bit builtin mumble, mumble, mumble wave table Can I make the 1225 work like either the 1130 or 1131? Is this NMG5 the same as the NeoMagic 2200 (MagicMedia256AV) which is supported under XFree86? I am not holding out much hope for the sound card. Thanks for any insight. S -- ------------------------------------------------------------------------- Sean O'Connell Email: sean@stat.Duke.EDU Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 Not only am I highly allergic to perfume; it is an environmental toxin! http://www.supernet.net/~jackibar/perfume.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 11:53:54 1999 Received: from k12-nis-2.bbn.com (K12-NIS-2.BBN.COM [128.89.6.195]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA26257 for ; Tue, 16 Feb 1999 11:53:52 -0800 (PST) (envelope-from dm@k12-nis-2.bbn.com) Received: from k12-nis-2.bbn.com (dm@LOCALHOST.BBN.COM [127.0.0.1]) by k12-nis-2.bbn.com (8.9.0/8.9.0) with ESMTP id OAA13389; Tue, 16 Feb 1999 14:52:14 -0500 (EST) Message-Id: <199902161952.OAA13389@k12-nis-2.bbn.com> To: ulf@alameda.net cc: Eric I Arnoth , mobile@freebsd.org Subject: Re: new laptop, pcmcia slots In-reply-to: Your message of "Tue, 16 Feb 1999 11:08:58 PST." <19990216110858.H1580@TelcoSucks.org> Date: Tue, 16 Feb 1999 14:52:13 -0500 From: david mankins Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Date: Tue, 16 Feb 1999 11:08:58 -0800 From: Ulf Zimmermann To: Eric I Arnoth , mobile@FreeBSD.ORG Subject: Re: new laptop, pcmcia slots I personaly liked the Hitachi M series or now the Visionbook Plus or Pro series. the M and Plus have built in 10mbit/sec PCI ethernet plus modem. the Pro has 10/100 plus modem. No PCMCIA stuff. Hardware on the M was supported last time I used it with FreeBSD. Not sure what ethernet chip is in the Plus or Pro. The Visionbook Pro has PCMCIA, but it's on a TI 1131 PCI to PCMCIA CardBus bridge, which wasn't supported under Freebsd 2.2.6. I haven't looked to see if it is supported in later versions (while the Visionbook has built-in ethernet and built-in modem, I was hoping to use the PCMCIA card for Wavelan wireless LAN, and could not; my project is currently using a modified 2.2.6, and I wasn't willing to wander too far from it). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 13:20:45 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 5E46310F8A for ; Tue, 16 Feb 1999 13:20:40 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id VAA22539; Tue, 16 Feb 1999 21:20:39 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Tue, 16 Feb 1999 21:19:39 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: References: <199902150724.AAA35191@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 16 Feb 1999 21:19:37 +0000 To: Eric I Arnoth From: Bob Bishop Subject: Re: new laptop, pcmcia slots Cc: mobile@FreeBSD.ORG Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 8:10 am -0500 16/2/99, Eric I Arnoth wrote: >Would everyone and anyone on the list please tell me of the laptops they >are aware of, both make and model, which are PCMCIA-trouble-free? I've had no problems with IBM ThinkPad 365XD. Early BIOS versions are allegedly suspect, but it's flashable. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 13:43:47 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id ECD6111009 for ; Tue, 16 Feb 1999 13:43:41 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (lxpxeu.lx.ehu.es [158.227.99.224]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id WAA17146; Tue, 16 Feb 1999 22:43:32 +0100 (MET) Message-ID: <36C9E683.26B0F1D8@we.lc.ehu.es> Date: Tue, 16 Feb 1999 22:43:31 +0100 From: "Jose M. Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-STABLE i386) MIME-Version: 1.0 To: ulf@Alameda.net Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Is the IBM Etherjet 10/100 card supported? References: <36C97411.EA4EF18C@we.lc.ehu.es> <19990216110958.I1580@TelcoSucks.org> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ulf Zimmermann wrote: > > On Tue, Feb 16, 1999 at 02:35:13PM +0100, Jose M. Alcaide wrote: > > The subject says all ;-). A colleague of mine owns an IBM Thinkpad > > with an Etherjet 10/100 PCMCIA. This card is not detected by > > teh "ze" driver, nor it is listed in /etc/pccard.conf. Is this > > card supported by FreeBSD (plain or PAO)? > > Is it a 16 bit or a 32 bit card ? If it is 32bit, they are not supported at > all. 16 bit should at least detected when insert. > It is a 32 bit card. Bad luck... :-( Thanks, -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@es.FreeBSD.ORG Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 16:39:23 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp2.a2000.nl (spartacus.a2000.nl [62.108.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 721A310F76 for ; Tue, 16 Feb 1999 16:39:12 -0800 (PST) (envelope-from alexlh@funk.org) Received: from node1484.a2000.nl ([62.108.20.132] helo=funk.org) by smtp2.a2000.nl with esmtp (Exim 2.02 #4) id 10Cv1D-0005th-00 for freebsd-mobile@freebsd.org; Wed, 17 Feb 1999 01:39:11 +0100 Message-ID: <36CA0FC2.78DAC84A@funk.org> Date: Wed, 17 Feb 1999 01:39:30 +0100 From: Alex Le Heux X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Subject: freeze at boot on Sony Vaio PCG-C1 on 3.1-REL Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, 3.1-REL freezes at boottime on my Vaio PCG-C1 when I compile a kernel with pccard support. The pccard support was the only change I made to the GENERIC config file. It freezes during the probe right after the npx0 device. Also, the ze driver sees my 3com 589, but then says "ze0 not found at 0x300" Does anyone have any ideas how to get this working? Alex -- "Ik zit op m'n kromme, akelige broertje te wachten. Die heeft zich opgesloten in de server ruimte, en die weigert eruit te komen." - Bart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 17:43:34 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (Postfix) with ESMTP id 9960A11353 for ; Tue, 16 Feb 1999 17:42:48 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.yy.cs.keio.ac.jp (lavender.rad.cc.keio.ac.jp [131.113.16.115]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id KAA08093; Wed, 17 Feb 1999 10:42:42 +0900 (JST) Received: (from sanpei@localhost) by lavender.yy.cs.keio.ac.jp (8.8.8/3.7W) id KAA02167; Wed, 17 Feb 1999 10:42:42 +0900 (JST) Date: Wed, 17 Feb 1999 10:42:42 +0900 (JST) Message-Id: <199902170142.KAA02167@lavender.yy.cs.keio.ac.jp> To: sean@stat.Duke.EDU Cc: freebsd-mobile@FreeBSD.ORG, sanpei@sanpei.org Subject: Re: HP Omnibook 900 In-Reply-To: Your message of "Wed, 17 Feb 1999 04:30:52 JST". <19990216143052.A6818@stat.Duke.EDU> From: sanpei@sanpei.org (MIHIRA Yoshiro) X-Mailer: mnews [version 1.21] 1997-12/23(Tue) Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org sean@stat.Duke.EDU wrote >> Pccard controller: TI PCI 1225 >> Video card: NeoMagic NMG5 (2.5MB ram) >> Sound: 16bit builtin mumble, mumble, mumble wave table >> >> Can I make the 1225 work like either the 1130 or 1131? I think current pcic code(sys/pci/pcic_p.c and sys/pccard/pcic.c) does not support TI chips. Only print out detech message. And my NOTE has TI PCI-1220, but detect PC-Card VLSI 82C146 and some time I can use PC-Card, but generally can't..... FROM dmesg: PC-Card VLSI 82C146 (5 mem & 2 I/O windows) pcic: controller irq 3 Initializing PC-card drivers: ed Does some one merge TI PCI chip_code from PAO? or Does some one have any opinion about TI CardBus Chip? ---- Cheers. MIHIRA Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Tue Feb 16 18: 5: 7 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 2C2C210E6F for ; Tue, 16 Feb 1999 18:04:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA02050; Tue, 16 Feb 1999 17:59:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902170159.RAA02050@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jose M. Alcaide" Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: Is the IBM Etherjet 10/100 card supported? In-reply-to: Your message of "Tue, 16 Feb 1999 14:35:13 +0100." <36C97411.EA4EF18C@we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Tue, 16 Feb 1999 17:59:20 -0800 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The subject says all ;-). A colleague of mine owns an IBM Thinkpad > with an Etherjet 10/100 PCMCIA. This card is not detected by > teh "ze" driver, nor it is listed in /etc/pccard.conf. Is this > card supported by FreeBSD (plain or PAO)? No. It's likely to be an 82558 derivative, but it's going to require = someone to actually do the work to support it. -- = \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Feb 17 7:48:57 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from stclairc.on.ca (mail.stclairc.on.ca [192.139.208.1]) by hub.freebsd.org (Postfix) with ESMTP id 2EC5210FED for ; Wed, 17 Feb 1999 07:48:41 -0800 (PST) (envelope-from tbothwel@stclairc.on.ca) Received: by gateway.stclairc.on.ca id <19754>; Wed, 17 Feb 1999 10:45:54 -0500 Message-Id: <99Feb17.104554est.19754@gateway.stclairc.on.ca> From: "Tim Bothwell" To: "Jose M. Alcaide" , "Mike Smith" Cc: Subject: Re: Is the IBM Etherjet 10/100 card supported? Date: Wed, 17 Feb 1999 10:47:06 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-Msmail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-Mimeole: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----Original Message----- From: Mike Smith To: Jose M. Alcaide Cc: freebsd-mobile@FreeBSD.ORG Date: Tuesday, February 16, 1999 9:01 PM Subject: Re: Is the IBM Etherjet 10/100 card supported? > The subject says all ;-). A colleague of mine owns an IBM Thinkpad > with an Etherjet 10/100 PCMCIA. This card is not detected by > teh "ze" driver, nor it is listed in /etc/pccard.conf. Is this > card supported by FreeBSD (plain or PAO)? >No. It's likely to be an 82558 derivative, but it's going to require >someone to actually do the work to support it. I saw a driver for linux that supported this card, how difficult would it be to port it? -tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Feb 17 14:45:52 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from dingo.cdrom.com (castles340.castles.com [208.214.167.40]) by hub.freebsd.org (Postfix) with ESMTP id D80D41127F for ; Wed, 17 Feb 1999 14:45:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01178; Wed, 17 Feb 1999 14:40:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902172240.OAA01178@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Tim Bothwell" Cc: "Jose M. Alcaide" , "Mike Smith" , freebsd-mobile@FreeBSD.ORG Subject: Re: Is the IBM Etherjet 10/100 card supported? In-reply-to: Your message of "Wed, 17 Feb 1999 10:47:06 EST." <99Feb17.104554est.19754@gateway.stclairc.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 17 Feb 1999 14:40:44 -0800 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > -----Original Message----- > From: Mike Smith > To: Jose M. Alcaide > Cc: freebsd-mobile@FreeBSD.ORG > Date: Tuesday, February 16, 1999 9:01 PM > Subject: Re: Is the IBM Etherjet 10/100 card supported? > > > > The subject says all ;-). A colleague of mine owns an IBM Thinkpad > > with an Etherjet 10/100 PCMCIA. This card is not detected by > > teh "ze" driver, nor it is listed in /etc/pccard.conf. Is this > > card supported by FreeBSD (plain or PAO)? > > >No. It's likely to be an 82558 derivative, but it's going to require > >someone to actually do the work to support it. > > I saw a driver for linux that supported this card, how difficult would it be > to port it? Not hard, presuming you have some experience. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Feb 17 14:58:16 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (Postfix) with ESMTP id C339811175 for ; Wed, 17 Feb 1999 14:58:05 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id VAA01828; Wed, 17 Feb 1999 21:11:27 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00694; Wed, 17 Feb 1999 08:40:56 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199902170840.IAA00694@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Alex Le Heux Cc: freebsd-mobile@FreeBSD.ORG Subject: Re: freeze at boot on Sony Vaio PCG-C1 on 3.1-REL In-reply-to: Your message of "Wed, 17 Feb 1999 01:39:30 +0100." <36CA0FC2.78DAC84A@funk.org> Date: Wed, 17 Feb 1999 08:40:55 +0000 From: Brian Somers Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > 3.1-REL freezes at boottime on my Vaio PCG-C1 when I compile a kernel > with pccard support. > > The pccard support was the only change I made to the GENERIC config > file. > > It freezes during the probe right after the npx0 device. Thinks work ok on my Vaio PCG-747... what was your *one* change ? Did you add apm, pcic0 and pcic1 devices and the card0 controller ? > Also, the ze driver sees my 3com 589, but then says "ze0 not found at > 0x300" The ze driver doesn't do 589s to my knowledge. Try the zp driver, or even better, as you're building your own kernel, add the ep driver for proper support: device ep0 at isa? port 0x300 net irq 11 vector epintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 and also ``disable'' sio1 - otherwise it'll screw up IRQ 3 and your card controller will fail (this may have been fixed lately). > Does anyone have any ideas how to get this working? I'm assuming our hardware is at least similar - I may be wrong. The 747 is a full-blown A4 laptop. Yours may be a palm top for all I know.... YMMV. > Alex > > -- > "Ik zit op m'n kromme, akelige broertje te wachten. Die heeft zich > opgesloten in de server ruimte, en die weigert eruit te komen." > > - Bart -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Wed Feb 17 17:22:31 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (Postfix) with ESMTP id D2EC511663 for ; Wed, 17 Feb 1999 17:22:16 -0800 (PST) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with ESMTP id SAA04980 for ; Wed, 17 Feb 1999 18:22:06 -0700 (MST) (envelope-from handy@lambic.physics.montana.edu) Date: Wed, 17 Feb 1999 18:22:06 -0700 (MST) From: Brian Handy To: freebsd-mobile@freebsd.org Subject: D-Link pccard.conf entry Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Here's the pccard.conf NE2000-clone-entry-of-the-week: # D-link NE2000 clone card "D-Link" "DE-660" config 0x20 "ed0" 10 0x10 insert echo D-Link NE2000 inserted insert /etc/pccard_ether ed0 link0 -link1 remove echo D-Link NE2000 removed remove /sbin/ifconfig ed0 delete Happy trails, Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Feb 18 6:29:14 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by hub.freebsd.org (Postfix) with ESMTP id 5FCB811424 for ; Thu, 18 Feb 1999 06:29:03 -0800 (PST) (envelope-from earnoth@UDel.Edu) Received: from compaq.my.local.net (lapdog.duch.udel.edu [128.175.54.5]) by copland.udel.edu (8.8.8/8.8.8) with SMTP id JAA08784 for ; Thu, 18 Feb 1999 09:29:05 -0500 (EST) Date: Thu, 18 Feb 1999 09:28:14 -0500 (EST) From: "Eric I. Arnoth" X-Sender: earnoth@compaq.my.local.net To: freebsd-mobile@freebsd.org Subject: new laptop, which system? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My many thanks to all of you who sent me information on what laptops would be FreeBSD friendly. I have read the suggestions, searched the web for more details, and performed extensive price comparisons. Now that I have selected the new laptop I will buy, I find myself wondering which version of FreeBSD should I install. Which would be wiser to install on a fresh system, 3.1 (3.0?) stable, or the PAO 2.2.8? I notice that there is no PAO install disk for 3.x, and I certainly want to install the right version since I have a clean slate to start from. Thanks again for all the emails everyone sent. It is very gratifying to have recieved such kindly assistance in my moment of crisis. ////// ///// Eric I. Arnoth // // // ==================== ///////////////////// earnoth@udel.edu // // // Renaissance Quanta - ////// // // http://udel.edu/~earnoth/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Feb 18 7:25:53 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by hub.freebsd.org (Postfix) with ESMTP id DF5EA11604 for ; Thu, 18 Feb 1999 07:25:01 -0800 (PST) (envelope-from earnoth@UDel.Edu) Received: from compaq.my.local.net (lapdog.duch.udel.edu [128.175.54.5]) by copland.udel.edu (8.8.8/8.8.8) with SMTP id KAA24766; Thu, 18 Feb 1999 10:24:51 -0500 (EST) Date: Thu, 18 Feb 1999 10:24:00 -0500 (EST) From: "Eric I. Arnoth" X-Sender: earnoth@compaq.my.local.net To: Gianmarco Giovannelli Cc: mobile@freebsd.org Subject: Re: new laptop, which system? In-Reply-To: <4.1.19990218162613.0098be10@194.184.65.4> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 18 Feb 1999, Gianmarco Giovannelli wrote: > At 09.28 18/02/99 -0500, you wrote: > If you are brave enough I'd suggest go for 4.0-current, but if you use for > a production env. I strongly suggest 3.1-stable. I have no problem at all > at running FreeBSD 4.0-current on my Libretto 50ct and Ast, but I am using > them for fun ... if a day there is a problem is not a critical iussue. > > 2.2.x-stable branch is out of discussion... Bravado has nothing to do with it, my system is mission-critical for my graduate degree. ;) I take it then that 3.1-stable covers all the bases with respect to laptop-support that PAO 2.2.8 does? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Feb 18 7:27:32 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (Postfix) with ESMTP id C7C14115FD for ; Thu, 18 Feb 1999 07:21:56 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem20.masternet.it [194.184.65.30]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id QAA26346; Thu, 18 Feb 1999 16:21:01 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <4.1.19990218162613.0098be10@194.184.65.4> X-Sender: gmarco@scotty.masternet.it X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 18 Feb 1999 16:29:27 +0100 To: "Eric I. Arnoth" From: Gianmarco Giovannelli Subject: Re: new laptop, which system? Cc: mobile@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 09.28 18/02/99 -0500, you wrote: >My many thanks to all of you who sent me information on what laptops would >be FreeBSD friendly. I have read the suggestions, searched the web for >more details, and performed extensive price comparisons. Now that I have >selected the new laptop I will buy, I find myself wondering which version >of FreeBSD should I install. Which would be wiser to install on a fresh >system, 3.1 (3.0?) stable, or the PAO 2.2.8? I notice that there is no >PAO install disk for 3.x, and I certainly want to install the right >version since I have a clean slate to start from. Thanks again for all >the emails everyone sent. It is very gratifying to have recieved such >kindly assistance in my moment of crisis. If you are brave enough I'd suggest go for 4.0-current, but if you use for a production env. I strongly suggest 3.1-stable. I have no problem at all at running FreeBSD 4.0-current on my Libretto 50ct and Ast, but I am using them for fun ... if a day there is a problem is not a critical iussue. 2.2.x-stable branch is out of discussion... Best Regards, Gianmarco Giovannelli , "Unix expert since yesterday" http://www.giovannelli.it/~gmarco http://www2.masternet.it To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Feb 18 13:26:57 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id 5555C116A1 for ; Thu, 18 Feb 1999 13:26:27 -0800 (PST) (envelope-from kent@tfd.com) Received: from sneezy.tfd.com (sneezy.tfd.com [10.9.200.10]) by rtp.tfd.com (8.8.6/8.7.3) with SMTP id QAA08556 for ; Thu, 18 Feb 1999 16:27:16 -0500 (EST) Received: by sneezy.tfd.com id AA10221 (5.65b/IDA-1.4.3 for freebsd-mobile@freebsd.org); Thu, 18 Feb 99 16:29:26 -0500 Date: Thu, 18 Feb 99 16:29:26 -0500 From: Kent Hauser Message-Id: <9902182129.AA10221@sneezy.tfd.com> To: freebsd-mobile@freebsd.org Subject: a "stable" bsd for laptops Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, I'm searching for a "stable" bsd version for my laptop. For a while, I was running BSD 2.1, but last year after I upgraded to 2.2-current version (I don't remember the dat), NFS mounts stopped working. As this finally got tiresome, last week I tried upgrading to 3.0-stable (the snap from 0208), but after the ELF upgrade, I got messages about the firewall being enabled, but no rules. I tried to add rules with ipfw, but got an "operation not supported" (or something). So I tried a full install (starting from floppy boot). Same result. So I tried 3.1-BETA (0214 snap). The install hangs after mounting the distribution directory from my SunOS (4.1.4) host. So instead of further guessing, I'm hoping for suggestions. Hardware: TI5020 laptop (pentium 75) Networking: 3M 3C589C. What FreeBSD version am I most likely to be able to use with above? Thanks.. Kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Thu Feb 18 22:15:49 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from smtp2.a2000.nl (spartacus.a2000.nl [62.108.1.20]) by hub.freebsd.org (Postfix) with ESMTP id 1BBD911540 for ; Thu, 18 Feb 1999 22:15:45 -0800 (PST) (envelope-from alexlh@funk.org) Received: from node1484.a2000.nl ([62.108.20.132] helo=funk.org) by smtp2.a2000.nl with esmtp (Exim 2.02 #4) id 10DjDy-0000pT-00; Fri, 19 Feb 1999 07:15:42 +0100 Message-ID: <36CD01C4.B20DA339@funk.org> Date: Fri, 19 Feb 1999 07:16:36 +0100 From: Alex Le Heux X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Eric I. Arnoth" , freebsd-mobile@freebsd.org Subject: Re: new laptop, which system? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Eric I. Arnoth" wrote: > > On Thu, 18 Feb 1999, Gianmarco Giovannelli wrote: > > > At 09.28 18/02/99 -0500, you wrote: > > If you are brave enough I'd suggest go for 4.0-current, but if you use for > > a production env. I strongly suggest 3.1-stable. I have no problem at all > > at running FreeBSD 4.0-current on my Libretto 50ct and Ast, but I am using > > them for fun ... if a day there is a problem is not a critical iussue. > > > > 2.2.x-stable branch is out of discussion... > Bravado has nothing to do with it, my system is mission-critical for my > graduate degree. ;) I take it then that 3.1-stable covers all the bases > with respect to laptop-support that PAO 2.2.8 does? Almost, but not quite. I've just installed 2.2.8-PAO again, as neither 3.1 or 4.0 would have anything to do the with cardbus slots on my Sony Vaio PCG-C1. When I get back from the trip I'll go on in a few hours I'll see if I can get either of them working. The lesson learned here is not to try upgrade the os on your laptop right before you plan to take it on a trip to far away... 2.2.8-PAO worked out of the box though... Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Feb 19 0:33:49 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from sloth.cs.unm.edu (sloth.cs.unm.edu [198.59.151.21]) by hub.freebsd.org (Postfix) with ESMTP id 5C43211637 for ; Fri, 19 Feb 1999 00:33:47 -0800 (PST) (envelope-from colinj@cs.unm.edu) Received: from waimea.cs.unm.edu ([198.83.92.103]) by sloth.cs.unm.edu with esmtp (Exim 2.10 #1) id 10DlNc-00070m-00 for freebsd-mobile@freebsd.org; Fri, 19 Feb 1999 01:33:48 -0700 Received: from localhost (colinj@localhost) by waimea.cs.unm.edu (980427.SGI.8.8.8/8.8.8) with ESMTP id BAA30624 for ; Fri, 19 Feb 1999 01:33:51 -0700 (MST) (envelope-from colinj@cs.unm.edu) X-Authentication-Warning: waimea.cs.unm.edu: colinj owned process doing -bs Date: Fri, 19 Feb 1999 01:33:50 -0700 From: Colin Eric Johnson To: freebsd-mobile@freebsd.org Subject: Speak Freely? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone gotten speak freely to work on a Dell Lattitude CPi? Sound out works fine, I'm not sure what to use to test sound in. I'm not getting anything from sfspeaker or sfmike. Colin E. Johnson | colinj@unm.edu | http://www.unm.edu/~colinj/ The scum also rises. -- Dr. Hunter S. Thompson FreeBSD trurl.lternet.edu 3.1-STABLE FreeBSD 3.1-STABLE #3: Tue Feb 16 09:42:01 MST 1999 colinj@trurl.lternet.edu:/usr/src/sys/compile/TRURL i386 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Feb 19 7:39:40 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from darkstar.inetu.net (darkstar.inetu.net [207.18.13.192]) by hub.freebsd.org (Postfix) with ESMTP id 385F6117E2 for ; Fri, 19 Feb 1999 07:39:36 -0800 (PST) (envelope-from kerberus@inetu.net) Received: from inetu.net (root@localhost [127.0.0.1]) by darkstar.inetu.net (8.8.8/8.8.8) with ESMTP id KAA00909 for ; Fri, 19 Feb 1999 10:39:30 GMT (envelope-from kerberus@inetu.net) Message-ID: <36CD3F61.5AD3AE3D@inetu.net> Date: Fri, 19 Feb 1999 10:39:29 +0000 From: Kerberus Reply-To: kerberus@inetu.net Organization: INetU, Inc. X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Subject: Laptop problems Content-Type: multipart/alternative; boundary="------------D7D2F4B35001DF6DCF7CC17F" Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --------------D7D2F4B35001DF6DCF7CC17F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have a CTX EasyBook laptop with an AMD K6 3D 300Mhz CPU, 32mg memory, 20x cdrom, Toshiba MK2109 MAT 2 gig disk, 2 PCMCIA slots, 2 USB Ports, an Infrared controller, internal modem, serial port, paralell port, and a NeoMagic video card, did i forget anything.... those are the specs. the hard drive is primary on the primary controller, the cdrom drive is primary on the secondary controller, which i found quite odd.... first when booting everything is found, but there is a long pause during its attempt trying to decipher my cdrom or cd the controller, but it does get passed it finally after a few minits, also on the initial install while booting with the 2.2.8-RELEASE floppy it gave the following error and locked up solid, atapi1.0: invalid command phase, ireason=0xd0, status=d0, error=d0 this is debug information. I have to disable the cdrom in the bios, in order for sysinstall to run, and install from a dos partition. so finally i get it installed and re-enable the cdrom and boot, still long pause 2-3 minits, then finally a login, curiosity kills me i run sysinstall ( I know better ) locked up solid while probing for devices. Ok so how do i stop the pause, and prevent sysinstall from locking up on the cdrom so i can actually use the damn thing ??? and lastly since this is a laptop, i needed to patch with the PAO patch, to enable my NETGEAR ethernet card. ( it works fine on my other CTX ) so i know its not the card, but when it now boots it initializes then errors out with "/kernel: ed0: device timeout" the Ethernet PCMCIA card is a NETGEAR FA410TX this doesnt happen on the other laptop.... ok so im done i have four problems 1: how can i stop this damn long pause 2: how do i prevent sysinstall probing for devices and locking up or fix the cdrom error 3: how can i enable my cdrom to actually work 4: get my ethernet card to stop timing out so i can use it Thanks in Advance, Almost Happy CTX Laptop PS the ps/2 mouse and Xwindows actually do run on this thing nicely, but i need either the network connectivity or a working cdrom to install any ports .....!!!! jeeeez!! go figure. -- OhhhNooooo --------------D7D2F4B35001DF6DCF7CC17F Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit  

I have a CTX EasyBook laptop with an AMD K6 3D 300Mhz CPU, 32mg
memory,
20x cdrom, Toshiba MK2109 MAT 2 gig disk, 2 PCMCIA slots, 2 USB
Ports,
an Infrared controller, internal modem, serial port, paralell port, and
a NeoMagic video card, did i forget anything.... those are the specs.

the hard drive is primary on the primary controller, the cdrom drive is
primary on the secondary controller, which i found quite odd....

first when booting everything is found, but there is a long pause during its attempt trying to decipher my cdrom or cd the controller,
but it does get passed it finally after a few minits, also on the
initial install while booting with the 2.2.8-RELEASE floppy it gave the
following error and locked up solid,

atapi1.0: invalid command phase, ireason=0xd0,
status=d0<busy,ready,opdone>, error=d0

this is debug information.

I have to disable the cdrom in the bios, in order for sysinstall to run,
and install from a dos partition. so finally i get it installed and
re-enable the cdrom and boot, still long pause 2-3 minits, then finally
a login, curiosity kills me i run sysinstall ( I know better ) locked up
solid while probing for devices. Ok so how do i stop the pause, and
prevent sysinstall from locking up on the cdrom so i can actually use
the damn thing ??? and lastly since this is a laptop, i needed to patch
with the PAO patch, to enable my NETGEAR ethernet card. ( it works fine
on my other CTX ) so i know its not the card, but when it now boots it
initializes then errors out with

"/kernel: ed0: device timeout"

the Ethernet PCMCIA card is a NETGEAR FA410TX
this doesnt happen on the other laptop.... ok so im done i have four
problems

1: how can i stop this damn long pause
2: how do i prevent sysinstall probing for devices and locking up or fix
    the cdrom error
3: how can i enable my cdrom to actually work
4: get my ethernet card to stop timing out so i can use it

Thanks in Advance,

Almost Happy CTX Laptop

PS the ps/2 mouse and Xwindows actually do run on this thing nicely, but
i need either the network connectivity or a working cdrom to install any
ports .....!!!! jeeeez!! go figure.
  

-- 
OhhhNooooo
  --------------D7D2F4B35001DF6DCF7CC17F-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Fri Feb 19 20:56:46 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id 32F5510E6E for ; Fri, 19 Feb 1999 20:56:42 -0800 (PST) (envelope-from kent@tfd.com) Received: (from kent@localhost) by rtp.tfd.com (8.8.6/8.7.3) id XAA10422 for mobile@freebsd.org; Fri, 19 Feb 1999 23:57:26 -0500 (EST) Date: Fri, 19 Feb 1999 23:57:26 -0500 (EST) From: Kent Hauser Message-Id: <199902200457.XAA10422@rtp.tfd.com> To: mobile@freebsd.org Subject: Problems installing with the zp0 driver Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm having real troubles installing from the boot floppy with the zp0 driver (and my '589C pcmcia card). Hangs after about a half-a-dozen hunks. I'm trying to install via NFS from a SunOS 4.1.4 host (over 10baseT if that matters). Suggestions? workarounds? Host: TI5020 (pentium P75) OS Vers: 3.0-stable, 3.1-beta, 4.0-current. Thanks. Kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Feb 20 10:14:30 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from Bespin.worldnet.net (bespin.worldnet.net [195.3.3.4]) by hub.freebsd.org (Postfix) with ESMTP id 0F8D211882 for ; Sat, 20 Feb 1999 10:14:24 -0800 (PST) (envelope-from pcasidy@worldnet.fr) Received: from greatoak.home (p14-026.province.worldnet.fr [195.3.14.26]) by Bespin.worldnet.net (8.8.8/8.8.8) with ESMTP id TAA27229 for ; Sat, 20 Feb 1999 19:12:44 +0100 (CET) Received: (from pcasidy@localhost) by greatoak.home (8.8.8/8.8.8) id TAA00913 for freebsd-mobile@freebsd.org; Sat, 20 Feb 1999 19:04:03 +0100 (CET) (envelope-from pcasidy) Message-Id: <199902201804.TAA00913@greatoak.home> Date: Sat, 20 Feb 1999 19:04:03 +0100 (CET) From: Philippe CASIDY To: freebsd-mobile@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Feb 20 11:36:39 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (Postfix) with ESMTP id 6D9BC11912 for ; Sat, 20 Feb 1999 11:35:23 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id MAA24268; Sat, 20 Feb 1999 12:35:14 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id MAA24986; Sat, 20 Feb 1999 12:35:10 -0700 Date: Sat, 20 Feb 1999 12:35:10 -0700 Message-Id: <199902201935.MAA24986@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nathan Dorfman Cc: mobile@FreeBSD.ORG Subject: Re: pccard problems In-Reply-To: <19990220135357.A783@rtfm.net> References: <19990220135357.A783@rtfm.net> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ Moved to -mobile ] > a) it doesn't recognize card inserts/removes. the only way to get it to > see a card as present is if the card is inserted at the time pcic is loaded See the mobile archives for how to fix this. The bottom line is that either FreeBSD does not correctly setup the PCIC to generate interrupts at insertion/removal, or the PCIC is busted. (Or both). (The fix is trivial, but I don't remember where it is off the top of my head.) > b) allocate_driver() (userland calls the PIOCSDRV ioctl, which in turn > calls this) locks up the machine in a very interesting way. The LED for > the slot in question goes on, and the machine stops responding. Weird. > At this > point, I can't do *anything*, not even Ctrl+PrintScreen to drop to DDB. > Now, if I eject the card in question, the system returns to normal. > The ioctl(PIOCSDRV) returns errno 6 (ENXIO - No such device or address). > This seems to indicate that find_driver("ed0") returns 0. I also get > a few console messages: > > ed0: Unload > Return IRQ=11 It appears that the probe is someone 'stuck' or something. More kernel debugging may be necessary, such as setting breakpoints and such using remote-GDB. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Feb 20 11:52:31 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from hyperhost.net (ether.lightrealm.com [207.159.132.5]) by hub.freebsd.org (Postfix) with ESMTP id 8828F1198C for ; Sat, 20 Feb 1999 11:48:07 -0800 (PST) (envelope-from patseal@hyperhost.net) Received: from port3.annex8.radix.net (port3.annex8.radix.net [205.252.108.3]) by hyperhost.net (8.8.5/8.8.5) with ESMTP id OAA25604 for ; Sat, 20 Feb 1999 14:48:05 -0500 (EST) Date: Sat, 20 Feb 1999 14:47:59 -0500 (EST) From: Patrick Seal To: freebsd-mobile@FreeBSD.ORG Subject: 3COM pccard Modem Works! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just so you know, a small hack to pccard.conf will allow the 3COM 3CCM156 pccard modem to work under 3.1-STABLE here's the similar already existing entry: # 3com/USR/Megahertz 3CCM556 card "3Com" "3CXM/3CCM556" config 0x23 "sio2" 10 insert echo 3Com PCMCIA 56K Modem inserted remove echo 3Com PCMCIA 56K Modem removed here's the new entry: # 3com/USR/Megahertz 3CCM156 card "3COM" "3CCM156" config 0x23 "sio2" 10 insert echo 3Com PCMCIA 56K Modem inserted remove echo 3Com PCMCIA 56K Modem removed ------------------------------------ _____________________________________ Patrick Seal |"Microsoft isn't evil, they just make | really crappy operating systems." Hyperhost - http://www.hyperhost.net| -Linus Torvalds hosting and Design http://www.freebsd.org - http://www.linux.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Feb 20 13:49:27 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from mail4.bellatlantic.net (mail4.bellatlantic.net [151.197.0.38]) by hub.freebsd.org (Postfix) with ESMTP id 5DD1911931 for ; Sat, 20 Feb 1999 13:49:18 -0800 (PST) (envelope-from dougc1@bellatlantic.net) Received: from doug (client-151-197-32-17.bellatlantic.net [151.197.32.17]) by mail4.bellatlantic.net (8.8.5/8.8.5) with SMTP id QAA24385 for ; Sat, 20 Feb 1999 16:50:48 -0500 (EST) From: "Doug" To: Subject: compaq smartstations Date: Sat, 20 Feb 1999 16:49:49 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2212 (4.71.2419.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Has anyone used freebsd on a Compaq LTE ELITE 4/75CX with the smartstation dock station? I can't figure out how to get it to reconigze the built in ethernet card during install. Any responses would be helpful. Thanks Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Feb 20 16: 0:12 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by hub.freebsd.org (Postfix) with ESMTP id 73449119F5 for ; Sat, 20 Feb 1999 16:00:05 -0800 (PST) (envelope-from earnoth@UDel.Edu) Received: from host75-184.student.udel.edu (host75-184.student.udel.edu [128.175.75.184]) by copland.udel.edu (8.8.8/8.8.8) with ESMTP id SAA18392; Sat, 20 Feb 1999 18:56:21 -0500 (EST) Date: Sat, 20 Feb 1999 15:59:21 -0500 (EST) From: "Eric I. Arnoth" X-Sender: earnoth@conn75-184.conn.udel.edu To: Doug Cc: mobile@FreeBSD.ORG Subject: Re: compaq smartstations In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 20 Feb 1999, Doug wrote: > Hi, > > Has anyone used freebsd on a Compaq LTE ELITE 4/75CX with the > smartstation dock station? I can't figure out how to get it to reconigze the > built in ethernet card during install. Any responses would be helpful. > Doug, my input will be anything *but* helpful, I fear. If you've paid attention to my recent mails, you'll know that I was in the market for a new laptop. The main reason for that was the Compaq Presario laptop I had wouldn't let FreeBSD use the 3Com Etherlink III 3c589D PCCard. I've come to learn the hard way that Compaq is tortuously _proprietary_. My hunch is, if I couldn't get a Compaq laptop to cooperate with FBSD on what should have been *standard* hardware, you may have even less luck with a docking station, which is fairly proprietary by its very nature. You may have to take my route and buy a new machine (I chose Toshiba) and sell your Compaq. To those who are curious, btw, my Toshiba build went perfectly. I sized down the installed Windows98 (reasons out of my control necessitate that damned system!) FIPSed the partitioning table, installed FreeBSD via the PCCard mentioned above, and accomplished all that in four hours, including the install of all ports I use. I've been leisurely reconfiguring my FreeBSD 3.1 system now for my work over the course of the day, and am *VERY* pleased with Toshiba as a brand. My only complaint is that the keyboard doesn't have meta-left and meta-right keys (Win keys) at the bottom, and the list key is also uptop. Does anyone know how to configure XKB so that I can make use of those? -Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Feb 20 17:30:21 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from rtp.tfd.com (rtp.tfd.com [198.79.53.206]) by hub.freebsd.org (Postfix) with ESMTP id 5CF7A10E05 for ; Sat, 20 Feb 1999 17:29:59 -0800 (PST) (envelope-from kent@tfd.com) Received: from sneezy.tfd.com (sneezy.tfd.com [10.9.200.10]) by rtp.tfd.com (8.8.6/8.7.3) with SMTP id UAA11177; Sat, 20 Feb 1999 20:30:18 -0500 (EST) Received: by sneezy.tfd.com id AA00387 (5.65b/IDA-1.4.3 for sean@stat.Duke.EDU); Sat, 20 Feb 99 20:32:31 -0500 Date: Sat, 20 Feb 99 20:32:31 -0500 From: Kent Hauser Message-Id: <9902210132.AA00387@sneezy.tfd.com> To: sean@stat.Duke.EDU Subject: Re: Problems installing with the zp0 driver Cc: mobile@freebsd.org Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >On 1999 Feb 19, Kent Hauser (aka kent@tfd.com) wrote: >> >> I'm having real troubles installing from the boot floppy with >> the zp0 driver (and my '589C pcmcia card). Hangs after about >> a half-a-dozen hunks. I'm trying to install via NFS from a >> SunOS 4.1.4 host (over 10baseT if that matters). >> >> Suggestions? workarounds? > >Does installation via ftp work? The only other thing is _maybe_ >a duplex mismatch, but I doubt that...if you are using a switch, >maybe the port is set at full-duplex, but the card only does half. >A duplex mismatch will slow nfs to a crawl. > >Hope this helps, >S > >Hi sean, Thanks for the response. It doesn't work over ftp (to a local server or *.freebsd.org). It will login, read a couple of hunks & hang. My local net is simple -- everything is 10baseT or 10base2 & a single 10 port hub (circa 1991). Nothing to misconfigure. I seem to remember problems with the zp0 driver in FreeBSD 2.1 or so. I seem to remember that I had to run: % while (1) > ifconfig zp0 > sleep 30 > end on one of the vty shells to keep the zp0 interface from hanging. I have always upgraded using the pccard driver (ed0?) since -- until my disk crashed. Now I'm stuck. Any other suggestions? (Maybe option flags on the network config page?). Thanks. Kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message From owner-freebsd-mobile Sat Feb 20 19:23:23 1999 Delivered-To: freebsd-mobile@freebsd.org Received: from darkstar.inetu.net (darkstar.inetu.net [207.18.13.192]) by hub.freebsd.org (Postfix) with ESMTP id 0E9E111AED; Sat, 20 Feb 1999 19:22:48 -0800 (PST) (envelope-from kerberus@inetu.net) Received: from inetu.net ([209.122.155.155]) by darkstar.inetu.net (8.8.8/8.8.8) with ESMTP id WAA00627; Sat, 20 Feb 1999 22:22:41 GMT (envelope-from kerberus@inetu.net) Message-ID: <36CF7C14.DFB5E34F@inetu.net> Date: Sat, 20 Feb 1999 22:23:01 -0500 From: Kerberus X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-mobile@freebsd.org, freebsd-questions@freebsd.org Subject: WHATS WITH THE LIST Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok im so soRry but i need to VENT, whats with the list here and freebsd-mobile... ive tried to get a bit of background on a pcmcia card that works in one ctx laptop but not another ctx laptop...... i get a device timeout error.... its seems like a simple fix, but Ive gotten no support or response what so ever..... and i really dont want to go back to linux on this darn thing i want FreeBSD on it..... 2.2.8-release i just need a bit of help. ANYBODY ANYBODY...???? PLEASE....! Dont make me BEG!!! -------SNIP-------- ORIGINIAL POST----------------- I have a CTX EasyBook laptop with an AMD K6 3D 300Mhz CPU, 32mg memory, 20x cdrom, Toshiba MK2109 MAT 2 gig disk, 2 PCMCIA slots, 2 USB Ports, an Infrared controller, internal modem, serial port, paralell port, and a Neomagic video card, did i forget anything.... those are the specs. the hard drive is primary on the primary controller, the cdrom drive is primary on the secondary controller first when booting everything is found, but there is a long pause during when trying to decipher my cdrom controller, but it does get passed it finally after a few minits, also on the initial install while booting with the 2.2.8-RELEASE floppy it gave the following error and locked up solid, atapi1.0: invalid command phase, ireason=0xd0, status=d0, error=d0 this is debug information. I have to disable the cdrom in the bios, in order for sysinstall to run, and install from a dos partition. so finally i get it installed and re-enable the cdrom and boot, still long pause 2-3 minits, then finally a login, curiosity kills me i run sysinstall ( I know better ) locked up solid while probing for devices. Ok so how do i stop the pause, and prevent sysinstall from locking up on the cdrom so i can actually use the damn thing ??? and lastly since this is a laptop, i needed to patch with the PAO patch, to enable my NETGEAR ethernet card. ( it works fine on my other CTX ) so i know its not the card, but when it now boots it initializes then errors out with "/kernel: ed0: device timeout" the Ethernet PCMCIA card is a NETGEAR FA410TX this doesnt happen on the other laptop.... ok so im done i have three problems 1: how can i stop this damn long pause 2: how do i prevent sysinstall probing for devices and locking up or fix the cdrom error 3: get my ethernet card to stop timing out so i can use it Thanks in Advance, Almost Happy CTX Laptop PS the ps/2 mouse and Xwindows actually do run on this thing nicely, but i net either the network connectivity or a working cdrom to install any ports .....!!!! jeeeez!! go figure. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message