Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
On Friday, July 06, 2012 7:25:55 pm Kaho Toshikazu wrote: > Hello, > > John Baldwin wrote: > > > Almost all systems use one of the IDs we do support as a _CID if not a _HID. > > In fact, in this case it likely seems to be a BIOS bug as it used the same > > value for the _CID and _HID. I suspect it is supposed to be using 0303 as > > its > > _CID. > > I don't think the BIOS should say PNP0303 as a keyboard _CID. > Using _CID may help some systems, but it may not be helpful > for many systems having keyboard probe problem. > I think it's a specification bug made by Microsoft, > same devices connected different type devices should not have > different ID but same ID. Well, my point is that having a _HID and _CID with the same ID is pointless. It really does look like a typo in the BIOS source. > People with this problem can override AML code, > but I don't think it is a bad idea adding other IDs to the list for probing. Adding IDs is cheap, so I'm fine with doing so. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
Hello, John Baldwin wrote: > Almost all systems use one of the IDs we do support as a _CID if not a _HID. > In fact, in this case it likely seems to be a BIOS bug as it used the same > value for the _CID and _HID. I suspect it is supposed to be using 0303 as its > _CID. I don't think the BIOS should say PNP0303 as a keyboard _CID. Using _CID may help some systems, but it may not be helpful for many systems having keyboard probe problem. I think it's a specification bug made by Microsoft, same devices connected different type devices should not have different ID but same ID. > > http://download.microsoft.com/download/5/7/7/577a5684-8a83-43ae-9272-ff260a9c20e2/pnp_legacy.doc > > Note that 030B is listed as reserved in this table, and not a valid keyboard > device. Yes, it's a invalid type, but reserved as a keyborad. I don't know why the BIOS builder puts PNP030B as a keyboard, but it seems to be not a bug. People with this problem can override AML code, but I don't think it is a bad idea adding other IDs to the list for probing. -- k...@elam.kais.kyoto-u.ac.jp ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
On Thursday, July 05, 2012 11:04:07 pm Kaho Toshikazu wrote: > Hello John Baldwin, and all, > > John Baldwin wrote: > > > The system in general in 9.0 and later is more strict about honoring what > > the > > BIOS says in terms of allocating resources, so we have to be more correct > > in > > probing devices. The only wrinkles so far do in fact seem to stem from the > > keyboard controller. > > I don't have any plans for treating unknown ID device's resources. > Many keyboard PNP ID are listed on a file at the below URL, > and FreeBSD doesn't know almost of them. Almost all systems use one of the IDs we do support as a _CID if not a _HID. In fact, in this case it likely seems to be a BIOS bug as it used the same value for the _CID and _HID. I suspect it is supposed to be using 0303 as its _CID. > http://download.microsoft.com/download/5/7/7/577a5684-8a83-43ae-9272-ff260a9c20e2/pnp_legacy.doc Note that 030B is listed as reserved in this table, and not a valid keyboard device. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
El día Thursday, July 05, 2012 a las 05:22:22PM -0400, John Baldwin escribió: > So far I can't think of a non-hackish way to special case keyboard and > mouse controllers, though I'm close to doing so (i.e. just ignore any > device that tries to allocate resources in the "default" range for those > devices unless it is a "known" device ID). > > The patch in this thread should be committed though. And one should close this issue with this: http://www.freebsd.org/cgi/query-pr.cgi?pr=169571 thx for all your helping hands matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
Hello John Baldwin, and all, John Baldwin wrote: > The system in general in 9.0 and later is more strict about honoring what the > BIOS says in terms of allocating resources, so we have to be more correct in > probing devices. The only wrinkles so far do in fact seem to stem from the > keyboard controller. I don't have any plans for treating unknown ID device's resources. Many keyboard PNP ID are listed on a file at the below URL, and FreeBSD doesn't know almost of them. http://download.microsoft.com/download/5/7/7/577a5684-8a83-43ae-9272-ff260a9c20e2/pnp_legacy.doc -- k...@elam.kais.kyoto-u.ac.jp ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
On Thursday, July 05, 2012 4:25:21 pm Matthias Apitz wrote: > El día Thursday, July 05, 2012 a las 07:39:18AM -0400, John Baldwin escribió: > > > On Thursday, July 05, 2012 5:20:35 am Kaho Toshikazu wrote: > > > Hello, > > > > > > > Interesting question remains: why it works in the older revision > > > > r21? > > > > > > I don't know exactly resource management, but ISA_PNP_PROBE() > > > ignores device.hints if acpi unknown device takes resources. > > > I think this problem is related to some acpi changes. > > > > The system in general in 9.0 and later is more strict about honoring what > > the > > BIOS says in terms of allocating resources, so we have to be more correct > > in > > probing devices. The only wrinkles so far do in fact seem to stem from the > > keyboard controller. > > > > Somehow the system should bring up at least console in- and output; if > not you are completely locked out; in my case it was simple, because I > was booting fron an USB key and could tailor the USB booted system to > bring up interface+DHCP+SSH to login via SSH; but without this you are > lost So far I can't think of a non-hackish way to special case keyboard and mouse controllers, though I'm close to doing so (i.e. just ignore any device that tries to allocate resources in the "default" range for those devices unless it is a "known" device ID). The patch in this thread should be committed though. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
El día Thursday, July 05, 2012 a las 07:39:18AM -0400, John Baldwin escribió: > On Thursday, July 05, 2012 5:20:35 am Kaho Toshikazu wrote: > > Hello, > > > > > Interesting question remains: why it works in the older revision r21? > > > > I don't know exactly resource management, but ISA_PNP_PROBE() > > ignores device.hints if acpi unknown device takes resources. > > I think this problem is related to some acpi changes. > > The system in general in 9.0 and later is more strict about honoring what the > BIOS says in terms of allocating resources, so we have to be more correct in > probing devices. The only wrinkles so far do in fact seem to stem from the > keyboard controller. > Somehow the system should bring up at least console in- and output; if not you are completely locked out; in my case it was simple, because I was booting fron an USB key and could tailor the USB booted system to bring up interface+DHCP+SSH to login via SSH; but without this you are lost matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
On Thursday, July 05, 2012 5:20:35 am Kaho Toshikazu wrote: > Hello, > > > Interesting question remains: why it works in the older revision r21? > > I don't know exactly resource management, but ISA_PNP_PROBE() > ignores device.hints if acpi unknown device takes resources. > I think this problem is related to some acpi changes. The system in general in 9.0 and later is more strict about honoring what the BIOS says in terms of allocating resources, so we have to be more correct in probing devices. The only wrinkles so far do in fact seem to stem from the keyboard controller. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
Hello Matthias Apitz, and ML members,
Thanks to upload acpi dump. Your keyboard controller ID is "PNP030B",
and your posted patch may be correct. Please undo your reversion,
and try your patch.
Matthias Apitz wrote:
> > and there is now an entry for "PS2K" (not for "KBC"):
> >
> > Device (PS2K)
> > {
> > Name (_HID, EisaId ("PNP030B"))
> > Name (_CID, EisaId ("PNP030B"))
> > Method (_STA, 0, NotSerialized)
> > {
> > ShiftLeft (0x01, 0x0A, Local0)
> > If (And (IOST, Local0))
> > {
> > Return (0x0F
> >
> > the full file is here: http://www.unixarea.de/acpidump-r21.txt
>
> maybe it helps to add a line like this:
>
> static struct isa_pnp_id atkbdc_ids[] = {
> { 0x0303d041, "Keyboard controller (i8042)" }, /* PNP0303 */
> { 0x2003d041, "Keyboard controller (i8042)" }, /* PNP0320 */
> + { 0x0b03d041, "Keyboard controller (i8042)" }, /* PNP030B */
> { 0 }
>
>
--
k...@elam.kais.kyoto-u.ac.jp
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
Hello, > Interesting question remains: why it works in the older revision r21? I don't know exactly resource management, but ISA_PNP_PROBE() ignores device.hints if acpi unknown device takes resources. I think this problem is related to some acpi changes. -- k...@elam.kais.kyoto-u.ac.jp ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
El día Thursday, July 05, 2012 a las 03:36:22PM +0900, Kaho Toshikazu escribió:
> Hello Matthias Apitz, and ML members,
>
> Thanks to upload acpi dump. Your keyboard controller ID is "PNP030B",
> and your posted patch may be correct. Please undo your reversion,
> and try your patch.
Hello Kaho and all,
Yes! Now it works after inserting the line shown below:
$ dmesg | fgrep kbd
kbd1 at kbdmux0
atkbdc0: port 0x60,0x64 irq 1 on acpi0
atkbd0: irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: irq 12 on atkbdc0
also the mouse works fine;
Thanks for helping me getting to the point. I will later comment the bug
report in the issue tracker.
Interesting question remains: why it works in the older revision r21?
matthias
> > maybe it helps to add a line like this:
> >
> > static struct isa_pnp_id atkbdc_ids[] = {
> > { 0x0303d041, "Keyboard controller (i8042)" }, /* PNP0303 */
> > { 0x2003d041, "Keyboard controller (i8042)" }, /* PNP0320 */
> > + { 0x0b03d041, "Keyboard controller (i8042)" }, /* PNP030B */
> > { 0 }
> >
> >
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e - w http://www.unixarea.de/
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
El día Thursday, July 05, 2012 a las 07:28:33AM +0200, Matthias Apitz escribió:
> and there is now an entry for "PS2K" (not for "KBC"):
>
> Device (PS2K)
> {
> Name (_HID, EisaId ("PNP030B"))
> Name (_CID, EisaId ("PNP030B"))
> Method (_STA, 0, NotSerialized)
> {
> ShiftLeft (0x01, 0x0A, Local0)
> If (And (IOST, Local0))
> {
> Return (0x0F
>
> the full file is here: http://www.unixarea.de/acpidump-r21.txt
maybe it helps to add a line like this:
static struct isa_pnp_id atkbdc_ids[] = {
{ 0x0303d041, "Keyboard controller (i8042)" }, /* PNP0303 */
{ 0x2003d041, "Keyboard controller (i8042)" }, /* PNP0320 */
+ { 0x0b03d041, "Keyboard controller (i8042)" }, /* PNP030B */
{ 0 }
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e - w http://www.unixarea.de/
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
El día Wednesday, July 04, 2012 a las 07:33:08PM +0900, Kaho Toshikazu escribió:
> Hello,
>
> Can you put the file "acpidump-r21.txt" on the Internet?
> When you run `grep "Device" /tmp/acpidump-r21.txt`
> to get device list, can you find "PS2K" or "KBC" or similar word?
Hello,
For some unknown reason today it gives more lines:
# acpidump -dt | wc -l
acpidump: RSDT entry 2 (sig OEMB) is corrupt
3815
when I did this the other day it was only around 2000 lines;
and there is now an entry for "PS2K" (not for "KBC"):
Device (PS2K)
{
Name (_HID, EisaId ("PNP030B"))
Name (_CID, EisaId ("PNP030B"))
Method (_STA, 0, NotSerialized)
{
ShiftLeft (0x01, 0x0A, Local0)
If (And (IOST, Local0))
{
Return (0x0F
the full file is here: http://www.unixarea.de/acpidump-r21.txt
Thanks for your help
matthias
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e - w http://www.unixarea.de/
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
Hello, Can you put the file "acpidump-r21.txt" on the Internet? When you run `grep "Device" /tmp/acpidump-r21.txt` to get device list, can you find "PS2K" or "KBC" or similar word? Matthias Apitz wrote: > The command `acpidump -dt` in both releases (r21 and r235646) gives > an error: > > # acpidump -dt > /tmp/acpidump-r21.txt > acpidump: RSDT entry 2 (sig OEMB) is corrupt > > the output in r235646 is only some 70 lines and in r21 I do not see > any keyboard related; so I can't answer your question if the > keyboard controller is "PNP0303"; > > Based on r235646 sources, I have checked the SVN-diff between r21 > (where the keyboard is working) and r235646, see attachment > /tmp/atkbdc_isa.c-r21:r235646; and the logic of the kb detection has > changed; I will just give it a try and will revert this SVN change, i.e. > 'svn up -r r21 atkbdc_isa.c > to see if this works... it does not help; > > Thanks > > matthias > -- > Matthias Apitz > t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 > e - w http://www.unixarea.de/ > UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370) > UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
El día Tuesday, July 03, 2012 a las 09:51:37AM +0900, Kaho Toshikazu escribió:
> Hello Matthias Apitz and -current member,
>
> "sys/dev/atkbdc/atkbdc_isa.c" may not have your keyboard controller's ID.
> Run `acpidump -dt` and search your keyboard description.
> Is your keyboard controller "PNP0303" ?
>
> --
> k...@ed.niigata-u.ac.jp
Hello Kaho Toshikazu and all,
The command `acpidump -dt` in both releases (r21 and r235646) gives
an error:
# acpidump -dt > /tmp/acpidump-r21.txt
acpidump: RSDT entry 2 (sig OEMB) is corrupt
the output in r235646 is only some 70 lines and in r21 I do not see
any keyboard related; so I can't answer your question if the
keyboard controller is "PNP0303";
Based on r235646 sources, I have checked the SVN-diff between r21
(where the keyboard is working) and r235646, see attachment
/tmp/atkbdc_isa.c-r21:r235646; and the logic of the kb detection has
changed; I will just give it a try and will revert this SVN change, i.e.
'svn up -r r21 atkbdc_isa.c
to see if this works... it does not help;
Thanks
matthias
--
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e - w http://www.unixarea.de/
UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370)
UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5
Index: atkbdc_isa.c
===
--- atkbdc_isa.c(revision 21)
+++ atkbdc_isa.c(revision 235646)
@@ -49,6 +49,11 @@
static int atkbdc_isa_attach(device_t dev);
static device_tatkbdc_isa_add_child(device_t bus, u_int order, const
char *name,
int unit);
+static struct resource *atkbdc_isa_alloc_resource(device_t dev, device_t child,
+ int type, int *rid, u_long start, u_long end,
+ u_long count, u_int flags);
+static int atkbdc_isa_release_resource(device_t dev, device_t child,
+ int type, int rid, struct resource *r);
static device_method_t atkbdc_isa_methods[] = {
DEVMETHOD(device_probe, atkbdc_isa_probe),
@@ -61,8 +66,8 @@
DEVMETHOD(bus_read_ivar,atkbdc_read_ivar),
DEVMETHOD(bus_write_ivar, atkbdc_write_ivar),
DEVMETHOD(bus_get_resource_list,atkbdc_get_resource_list),
- DEVMETHOD(bus_alloc_resource, bus_generic_rl_alloc_resource),
- DEVMETHOD(bus_release_resource, bus_generic_rl_release_resource),
+ DEVMETHOD(bus_alloc_resource, atkbdc_isa_alloc_resource),
+ DEVMETHOD(bus_release_resource, atkbdc_isa_release_resource),
DEVMETHOD(bus_activate_resource, bus_generic_activate_resource),
DEVMETHOD(bus_deactivate_resource, bus_generic_deactivate_resource),
DEVMETHOD(bus_get_resource, bus_generic_rl_get_resource),
@@ -82,6 +87,7 @@
static struct isa_pnp_id atkbdc_ids[] = {
{ 0x0303d041, "Keyboard controller (i8042)" }, /* PNP0303 */
+ { 0x2003d041, "Keyboard controller (i8042)" }, /* PNP0320 */
{ 0 }
};
@@ -170,8 +176,6 @@
device_verbose(dev);
error = atkbdc_probe_unit(device_get_unit(dev), port0, port1);
- if (error == 0)
- bus_generic_probe(dev);
bus_release_resource(dev, SYS_RES_IOPORT, 0, port0);
bus_release_resource(dev, SYS_RES_IOPORT, 1, port1);
@@ -216,14 +220,25 @@
return ENXIO;
}
+ /*
+* If the device is not created by the PnP BIOS or ACPI, then
+* the hint for the IRQ is on the child atkbd device, not the
+* keyboard controller, so this can fail.
+*/
+ rid = 0;
+ sc->irq = bus_alloc_resource_any(dev, SYS_RES_IRQ, &rid, RF_ACTIVE);
+
error = atkbdc_attach_unit(unit, sc, sc->port0, sc->port1);
if (error) {
bus_release_resource(dev, SYS_RES_IOPORT, 0, sc->port0);
bus_release_resource(dev, SYS_RES_IOPORT, 1, sc->port1);
+ if (sc->irq != NULL)
+ bus_release_resource(dev, SYS_RES_IRQ, 0, sc->irq);
return error;
}
*(atkbdc_softc_t **)device_get_softc(dev) = sc;
+ bus_generic_probe(dev);
bus_generic_attach(dev);
return 0;
@@ -233,9 +248,11 @@
atkbdc_isa_add_child(device_t bus, u_int order, const char *name, int unit)
{
atkbdc_device_t *ivar;
+ atkbdc_softc_t *sc;
device_tchild;
int t;
+ sc = *(atkbdc_softc_t **)device_get_softc(bus);
ivar = malloc(sizeof(struct atkbdc_device), M_ATKBDDEV,
M_NOWAIT | M_ZERO);
if (!ivar)
@@ -251,18 +268,21 @@
ivar->rid = order;
/*
-* If the device is not created by the PnP BIOS or ACPI,
-* refer to device hints for IRQ.
+* If the device is not created by the PnP BIOS or ACPI, refer
+* to device hints for IRQ. We always populate the resource
+* li
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
Hello Matthias Apitz and -current member, "sys/dev/atkbdc/atkbdc_isa.c" may not have your keyboard controller's ID. Run `acpidump -dt` and search your keyboard description. Is your keyboard controller "PNP0303" ? -- k...@ed.niigata-u.ac.jp > El d$(D+c*$(B Sunday, July 01, 2012 a las 06:29:28AM +0700, Erich Dollansky > escribi$(D+Q"k(B > > Hi, > > > and no older versions. I will install the USB booted system to harddisk > > and hope when booted from disk and not from USB the keyboard is working. > > > > I installed the system r235646 to disk and it shows the same problem: no > keyboard; > > if 7.4 still runs but not anything after 8.0, it is most likely what I have > written. Some USB hardware is not supported anymore in 8 and later. > > I would install the old one just to see You will also know wat hwardware is > used there and how it is supported. > > This might be the faster route before starting debugging something which is > not there. > > I said already that it works with a r21 version, CURRENT from > October 2010; so I booted this again and concerning keyboard, here is > the diff: > > r21: > > $ fgrep -i kb /tmp/dmesg-r21.txt > kbd1 at kbdmux0 > atkbdc0: at port 0x60,0x64 on isa0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > > $ ls -l /dev/kb* > lrwxr-xr-x 1 root wheel 6 Jul 1 08:39 /dev/kbd0 -> atkbd0 > lrwxr-xr-x 1 root wheel 7 Jul 1 08:39 /dev/kbd1 -> kbdmux0 > crw--- 1 root wheel0, 17 Jul 1 08:39 /dev/kbdmux0 > > r235646: > > $ fgrep -i kb /tmp/dmesg-r235646.txt > atkbd: the current kbd controller command byte 0065 > atkbd: keyboard ID 0x41ab (2) > sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) > atkbdc0 failed to probe at port 0x60 on isa0 > > $ ls -l /dev/kb* > lrwxr-xr-x 1 root wheel 7 Jul 1 08:39 /dev/kbd1 -> kbdmux0 > crw--- 1 root wheel0, 17 Jul 1 08:39 /dev/kbdmux0 > > the complete /tmp/dmesg-r21.txt is attached, the > /tmp/dmesg-r235646.txt was in some message of this thread; > > So the question is: why the is not > detected anymore in r235646, while it is in r21? > > Thanks > > matthias ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
Hi, On Sunday, July 01, 2012 01:58:49 PM Matthias Apitz wrote: > El día Sunday, July 01, 2012 a las 06:29:28AM +0700, Erich Dollansky escribió: > > > > and no older versions. I will install the USB booted system to harddisk > > > and hope when booted from disk and not from USB the keyboard is working. > > > > > I installed the system r235646 to disk and it shows the same problem: no > keyboard; > ok. > > if 7.4 still runs but not anything after 8.0, it is most likely what I have > > written. Some USB hardware is not supported anymore in 8 and later. > > > > I would install the old one just to see You will also know wat hwardware > > is used there and how it is supported. > > > > This might be the faster route before starting debugging something which is > > not there. > > I said already that it works with a r21 version, CURRENT from > October 2010; so I booted this again and concerning keyboard, here is > the diff: Of course, I have read it but forgot about it then. > > r21: > > atkbdc0: at port 0x60,0x64 on isa0 > > r235646: > > $ fgrep -i kb /tmp/dmesg-r235646.txt > atkbd: the current kbd controller command byte 0065 > atkbd: keyboard ID 0x41ab (2) > sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) > atkbdc0 failed to probe at port 0x60 on isa0 It must be the probing routine then. My keyboard here is at acpi but not on isa0. Is all in the kernel which is needed for isa? It should be, but a check could help. > So the question is: why the is not > detected anymore in r235646, while it is in r21? > Maybe the hints from man will help you: Kernel configuration: options KBD_RESETDELAY=N options KBD_MAXWAIT=N options KBDIO_DEBUG=N device atkbdc Are they still there? /boot/device.hints: hint.atkbdc.0.at="isa" hint.atkbdc.0.port="0x060" I do not know if some defaults have changed. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
On Sunday 01 July 2012 01:29:28 Erich Dollansky wrote: > Hi, > > On Saturday, June 30, 2012 10:11:31 PM Matthias Apitz wrote: > > El día Saturday, June 30, 2012 a las 01:49:58PM +0700, Erich Dollansky escribió: > > > Can you try FreeBSD 7.4 or 8.3? > > > > > > It is sad to say but some times support for older hardware gets cut out > > > for whatever reason. > > > > The IT guy of my company found this laptop in the attic and because > > it has no Wifi, nobody is interested in using it anymore. As I said, > > I could make use of it as a build machine and for this it must run > > CURRENT and no older versions. I will install the USB booted system to > > harddisk and hope when booted from disk and not from USB the keyboard is > > working. > > if 7.4 still runs but not anything after 8.0, it is most likely what I have > written. Some USB hardware is not supported anymore in 8 and later. > > I would install the old one just to see You will also know wat hwardware > is used there and how it is supported. > > This might be the faster route before starting debugging something which is > not there. > > Erich Try to compare pciconf -lv and dmesg. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
El día Sunday, July 01, 2012 a las 06:29:28AM +0700, Erich Dollansky escribió: Hi, > > and no older versions. I will install the USB booted system to harddisk > > and hope when booted from disk and not from USB the keyboard is working. > > I installed the system r235646 to disk and it shows the same problem: no keyboard; > if 7.4 still runs but not anything after 8.0, it is most likely what I have > written. Some USB hardware is not supported anymore in 8 and later. > > I would install the old one just to see You will also know wat hwardware is > used there and how it is supported. > > This might be the faster route before starting debugging something which is > not there. I said already that it works with a r21 version, CURRENT from October 2010; so I booted this again and concerning keyboard, here is the diff: r21: $ fgrep -i kb /tmp/dmesg-r21.txt kbd1 at kbdmux0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: irq 12 on atkbdc0 $ ls -l /dev/kb* lrwxr-xr-x 1 root wheel 6 Jul 1 08:39 /dev/kbd0 -> atkbd0 lrwxr-xr-x 1 root wheel 7 Jul 1 08:39 /dev/kbd1 -> kbdmux0 crw--- 1 root wheel0, 17 Jul 1 08:39 /dev/kbdmux0 r235646: $ fgrep -i kb /tmp/dmesg-r235646.txt atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) atkbdc0 failed to probe at port 0x60 on isa0 $ ls -l /dev/kb* lrwxr-xr-x 1 root wheel 7 Jul 1 08:39 /dev/kbd1 -> kbdmux0 crw--- 1 root wheel0, 17 Jul 1 08:39 /dev/kbdmux0 the complete /tmp/dmesg-r21.txt is attached, the /tmp/dmesg-r235646.txt was in some message of this thread; So the question is: why the is not detected anymore in r235646, while it is in r21? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5 Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-CURRENT #1 r21: Thu Oct 28 10:56:32 CEST 2010 g...@current.sisis.de:/usr/home/guru/myThings/FreeBSD/9-CURRENT/obj/usr/home/guru/myThings/FreeBSD/9-CURRENT/src/sys/GENERIC i386 WARNING: WITNESS option enabled, expect reduced performance. CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2398.34-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Family = f Model = 2 Stepping = 7 Features=0xbfebfbff Features2=0x4400 real memory = 1073741824 (1024 MB) avail memory = 1031737344 (983 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3ff0 (3) failed Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 cpu0: on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xb000-0xb0ff mem 0xd000-0xd7ff,0xffcf-0xffcf irq 16 at device 0.0 on pci1 uhci0: port 0xdf20-0xdf3f irq 16 at device 29.0 on pci0 uhci0: LegSup = 0x2f00 usbus0: on uhci0 uhci1: port 0xdf40-0xdf5f irq 19 at device 29.1 on pci0 uhci1: LegSup = 0x2f00 usbus1: on uhci1 uhci2: port 0xdf80-0xdf9f irq 18 at device 29.2 on pci0 uhci2: LegSup = 0x2f00 usbus2: on uhci2 ehci0: mem 0xffeffc00-0xffef irq 23 at device 29.7 on pci0 usbus3: EHCI version 1.0 usbus3: on ehci0 pcib2: at device 30.0 on pci0 pci2: on pcib2 cbb0: at device 3.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 fwohci0: port 0xcc00-0xcc7f mem 0xffdff800-0xffdf irq 18 at device 10.0 on pci2 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:03:0d:49:75:50:7a:e8 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:03:0d:50:7a:e8 fwe0: Ethernet address: 02:03:0d:50:7a:e8 fwip0: on firewire0 fwip0: Firewire address: 00:03:0d:49:75:50:7a:e8 @ 0xfffe, S400, maxrec 2048 sbp0: on firewire0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x14ac000 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x, SelfID Count=1, CYCLEMASTER mode sis0: port 0xc800-0xc8ff mem 0xffdfe000-0xffdfefff irq 17 at device 12.0 on pci2 sis0: Silicon Revision: DP83816A miibus0: on sis0 nsphyter0: PHY 0 on miibus0 nsphyter0: 10baseT, 10baseT-FDX
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
Hi, On Saturday, June 30, 2012 10:11:31 PM Matthias Apitz wrote: > El día Saturday, June 30, 2012 a las 01:49:58PM +0700, Erich Dollansky > escribió: > > > > > Can you try FreeBSD 7.4 or 8.3? > > > > It is sad to say but some times support for older hardware gets cut out for > > whatever reason. > > The IT guy of my company found this laptop in the attic and because > it has no Wifi, nobody is interested in using it anymore. As I said, > I could make use of it as a build machine and for this it must run CURRENT > and no older versions. I will install the USB booted system to harddisk > and hope when booted from disk and not from USB the keyboard is working. > if 7.4 still runs but not anything after 8.0, it is most likely what I have written. Some USB hardware is not supported anymore in 8 and later. I would install the old one just to see You will also know wat hwardware is used there and how it is supported. This might be the faster route before starting debugging something which is not there. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
El día Saturday, June 30, 2012 a las 01:49:58PM +0700, Erich Dollansky escribió: > > > > I have a boot-able USB key with r235646 which works fine in all my > > > > laptops so far; today I got as a gift an older FS Amilo D 7830 which has > > > > enough resources to use it as new build machine (1 GByte RAM, 80 GByte > > > > disk). I booted it with from the USB key and after the system is up it > > > > does not echo or react on any key-press; before booting the keys are > > > > working, for example in the menu to boot into single user etc. > > > > > > > > What could be the problem? > > > > > > > > I will later configure that the USB booted system brings Ethernet and > > > > SSH up, maybe I can see something when I can login via SSH... > > > > I have just for beeing curios booted an older USB key with r21 > > (from October 2010) and the keyboard just works as it should; > > > I have had a problem like this before. I have had to stick with an older > FreeBSD version on this machine. > > Can you try FreeBSD 7.4 or 8.3? > > It is sad to say but some times support for older hardware gets cut out for > whatever reason. The IT guy of my company found this laptop in the attic and because it has no Wifi, nobody is interested in using it anymore. As I said, I could make use of it as a build machine and for this it must run CURRENT and no older versions. I will install the USB booted system to harddisk and hope when booted from disk and not from USB the keyboard is working. Ofc, I would be willing to help debugging this, for example compiling a kernel with special options and/or debug printfs; but I can't start such a debug path on my own, because I have no clue about where to start. HIH matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
Hi, On Saturday, June 30, 2012 01:25:33 PM Matthias Apitz wrote: > El día Friday, June 29, 2012 a las 04:45:57PM +0200, Hans Petter Selasky > escribió: > > > On Friday 29 June 2012 15:34:23 Matthias Apitz wrote: > > > Hello, > > > > > > I have a boot-able USB key with r235646 which works fine in all my > > > laptops so far; today I got as a gift an older FS Amilo D 7830 which has > > > enough resources to use it as new build machine (1 GByte RAM, 80 GByte > > > disk). I booted it with from the USB key and after the system is up it > > > does not echo or react on any key-press; before booting the keys are > > > working, for example in the menu to boot into single user etc. > > > > > > What could be the problem? > > > > > > I will later configure that the USB booted system brings Ethernet and > > > SSH up, maybe I can see something when I can login via SSH... > > I have just for beeing curios booted an older USB key with r21 > (from October 2010) and the keyboard just works as it should; > I have had a problem like this before. I have had to stick with an older FreeBSD version on this machine. Can you try FreeBSD 7.4 or 8.3? It is sad to say but some times support for older hardware gets cut out for whatever reason. Erich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
El día Friday, June 29, 2012 a las 04:45:57PM +0200, Hans Petter Selasky escribió: > On Friday 29 June 2012 15:34:23 Matthias Apitz wrote: > > Hello, > > > > I have a boot-able USB key with r235646 which works fine in all my > > laptops so far; today I got as a gift an older FS Amilo D 7830 which has > > enough resources to use it as new build machine (1 GByte RAM, 80 GByte > > disk). I booted it with from the USB key and after the system is up it > > does not echo or react on any key-press; before booting the keys are > > working, for example in the menu to boot into single user etc. > > > > What could be the problem? > > > > I will later configure that the USB booted system brings Ethernet and > > SSH up, maybe I can see something when I can login via SSH... I have just for beeing curios booted an older USB key with r21 (from October 2010) and the keyboard just works as it should; a ls -l /dev/kb* shows now: /dev/kbd0 -> atkbd0 /dev/kbd1 -> kbdmux0 /dev/kbdmux0 the first line /dev/kbd0 -> atkbd0 is not shown in r235646; don't know if this has todo with the problem; matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
On Saturday 30 June 2012 06:43:16 Matthias Apitz wrote: > El día Friday, June 29, 2012 a las 04:45:57PM +0200, Hans Petter Selasky escribió: > > On Friday 29 June 2012 15:34:23 Matthias Apitz wrote: > > > Hello, > > > > > > I have a boot-able USB key with r235646 which works fine in all my > > > laptops so far; today I got as a gift an older FS Amilo D 7830 which > > > has enough resources to use it as new build machine (1 GByte RAM, 80 > > > GByte disk). I booted it with from the USB key and after the system > > > is up it does not echo or react on any key-press; before booting the > > > keys are working, for example in the menu to boot into single user > > > etc. > > > > > > What could be the problem? > > > > > > I will later configure that the USB booted system brings Ethernet and > > > SSH up, maybe I can see something when I can login via SSH... > > > > > > matthias > > > > What does dmesg say about USB? > > attached is the dmesg output > > matthias Hi, Can you try to play with USB settings in the BIOS? You can also try to compile a kernel with options USB_DEBUG, and hw.usb.uhub.debug=15. I don't see any errors in the dmesg. Maybe there are some magick bits that needs to be tweaked. Also try to put an external high speed hub in between. --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
El día Friday, June 29, 2012 a las 04:45:57PM +0200, Hans Petter Selasky escribió: > On Friday 29 June 2012 15:34:23 Matthias Apitz wrote: > > Hello, > > > > I have a boot-able USB key with r235646 which works fine in all my > > laptops so far; today I got as a gift an older FS Amilo D 7830 which has > > enough resources to use it as new build machine (1 GByte RAM, 80 GByte > > disk). I booted it with from the USB key and after the system is up it > > does not echo or react on any key-press; before booting the keys are > > working, for example in the menu to boot into single user etc. > > > > What could be the problem? > > > > I will later configure that the USB booted system brings Ethernet and > > SSH up, maybe I can see something when I can login via SSH... > > > > matthias > > What does dmesg say about USB? > attached is the dmesg output matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ UNIX since V7 on PDP-11 | UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2 | FreeBSD since 2.2.5 Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #0 r235646: Sat May 19 15:52:36 CEST 2012 g...@aurora.sisis.de:/usr/obj/usr/src/sys/GENERIC i386 WARNING: WITNESS option enabled, expect reduced performance. CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2398.35-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf27 Family = f Model = 2 Stepping = 7 Features=0xbfebfbff Features2=0x4400 real memory = 1073741824 (1024 MB) avail memory = 1027141632 (979 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 ctl: CAM Target Layer loaded acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, 3ff0 (3) failed driver bug: Unable to set devclass (class: acpi_sysresource devname: (unknown)) driver bug: Unable to set devclass (class: acpi_timer devname: (unknown)) cpu0: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 acpi_ec0: port 0x62,0x66 on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: on hostb0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xb000-0xb0ff mem 0xd000-0xd7ff,0xffcf-0xffcf irq 16 at device 0.0 on pci1 uhci0: port 0xdf20-0xdf3f irq 16 at device 29.0 on pci0 uhci0: LegSup = 0x2f00 usbus0 on uhci0 uhci1: port 0xdf40-0xdf5f irq 19 at device 29.1 on pci0 uhci1: LegSup = 0x2f00 usbus1 on uhci1 uhci2: port 0xdf80-0xdf9f irq 18 at device 29.2 on pci0 uhci2: LegSup = 0x2f00 usbus2 on uhci2 ehci0: mem 0xffeffc00-0xffef irq 23 at device 29.7 on pci0 usbus3: EHCI version 1.0 usbus3 on ehci0 pcib2: at device 30.0 on pci0 pci2: on pcib2 cbb0: at device 3.0 on pci2 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 fwohci0: port 0xcc00-0xcc7f mem 0xffdff800-0xffdf irq 18 at device 10.0 on pci2 fwohci0: OHCI version 1.10 (ROM=1) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:03:0d:49:75:50:7a:e8 fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x29b8000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:03:0d:50:7a:e8 fwe0: Ethernet address: 02:03:0d:50:7a:e8 fwip0: on firewire0 fwip0: Firewire address: 00:03:0d:49:75:50:7a:e8 @ 0xfffe, S400, maxrec 2048 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=0x, SelfID Count=1, CYCLEMASTER mode sis0: port 0xc800-0xc8ff mem 0xffdfe000-0xffdfefff irq 17 at device 12.0 on pci2 sis0: Silicon Revision: DP83816A miibus0: on sis0 nsphyter0: PHY 0 on miibus0 nsphyter0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto sis0: Ethernet address: 00:a0:cc:df:75:57 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0 ata0: at channel 0 on atapci0 ata1: at channel 1 on atapci0 pci0: at device 31.3 (no driver attached) pcm0: port 0xe000-0xe0ff,0xe100-0xe13f at device 31.5 on pci0 pcm0: pci0: at device 31.6 (no driver attached) acpi_button0: on acpi0 acpi_button1: on acpi0 acpi_tz0: on acpi0 battery0: on acpi0 acpi_acad0: on acpi0 ppc0: port 0x378-0x37f irq 7 on acpi0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: on ppc0 lpt0: on p
Re: no keyboard after booting r235646 in laptop FS Amilo D 7830
On Friday 29 June 2012 15:34:23 Matthias Apitz wrote: > Hello, > > I have a boot-able USB key with r235646 which works fine in all my > laptops so far; today I got as a gift an older FS Amilo D 7830 which has > enough resources to use it as new build machine (1 GByte RAM, 80 GByte > disk). I booted it with from the USB key and after the system is up it > does not echo or react on any key-press; before booting the keys are > working, for example in the menu to boot into single user etc. > > What could be the problem? > > I will later configure that the USB booted system brings Ethernet and > SSH up, maybe I can see something when I can login via SSH... > > matthias What does dmesg say about USB? --HPS ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
no keyboard after booting r235646 in laptop FS Amilo D 7830
Hello, I have a boot-able USB key with r235646 which works fine in all my laptops so far; today I got as a gift an older FS Amilo D 7830 which has enough resources to use it as new build machine (1 GByte RAM, 80 GByte disk). I booted it with from the USB key and after the system is up it does not echo or react on any key-press; before booting the keys are working, for example in the menu to boot into single user etc. What could be the problem? I will later configure that the USB booted system brings Ethernet and SSH up, maybe I can see something when I can login via SSH... matthias -- Matthias Apitz e - w http://www.unixarea.de/ UNIX since V7 on PDP-11, UNIX on mainframe since ESER 1055 (IBM /370) UNIX on x86 since SVR4.2 UnixWare 2.1.2, FreeBSD since 2.2.5 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
