Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

FreeBSD vs eMachines M6805 part II

0 views
Skip to first unread message

jed...@fxp.org

unread,
Feb 25, 2004, 11:15:15 AM2/25/04
to

--LZvS9be/3tNcYl/X
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

(crossposting to -amd64 and -mobile, please reply to either as
appropriate. I'm not on -mobile so please include me in replies)

I broke down last week and picked up an AMD Athlon 64-based
eMachines M6805 Laptop. Overall I am quite happy with it.

Under FreeBSD 5.2.1RC1 (i386) everything is supported except
the internal winmodem and internal Broadcom 54g-based wireless
adapter. Supported hardware on the laptop: Athlon 64 3000+,
512M RAM, 60G HD, CDRW/DVD-ROM, USB, Firewire, CF/Memory stick
reader, Rhine II ethernet, 15.5" display with a ATI Radeon 9600
(requires XFree 3.99.xx). Very fast and quite affordable
($1300 after rebates from the local Best Buy).

In order to get the ethernet controller and USB working I had
to disable APIC support (same under Linux). ACPI seems to
work fine under FreeBSD but Linux does not like the PCI
handling and requires 'pci=3Dnoacpi'.

So far I have had no luck getting FreeBSD 5.2.1-RC1 amd64 to
boot on the laptop. The loader loads the kernel and displays
the menu but upon before any messages from the kernel have
shown on the console the machine locks. Same for NetBSD amd64.
Linux amd64 works as well as FreeBSD i386 though.

More info, including dmesg and pciconf info, can be found
at http://www.fxp.org/jedgar/amd64/

Any help on getting FreeBSD amd64 supported would be greatly
appreciated.

--=20
Chris D. Faulhaber - jed...@fxp.org - jed...@FreeBSD.org
--------------------------------------------------------
FreeBSD: The Power To Serve - http://www.FreeBSD.org

--LZvS9be/3tNcYl/X
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
Comment: FreeBSD: The Power To Serve

iD8DBQFAPMmOObaG4P6BelARAj8BAJ9w1yGaXUX9BTB5EP9rTst5jwMDCACffUuD
9dfQ9tOWH9OsBqj6JT/x8CA=
=wvBH
-----END PGP SIGNATURE-----

--LZvS9be/3tNcYl/X--

Sean_...@alum.wofford.org

unread,
Feb 26, 2004, 7:42:29 AM2/26/04
to
Chris, this is very interesting. I've been eyeing this machine
as a posible replacement for my Dell Inspiron 8000 (hate giving
up the 1600x1200 res screen though...)

A few questions.

I looked at your verbose dmesg and wasn't able to tell if your
sound works (there are a bunch of mss_probe messages) and it
looks as though you might be having some issue with the
firewire ethernet mode (sbp messages). Could you clarify?

Also, do the sleep modes work for you?

"project evil" may help you with the wireless chipset.

Sean

_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-mobile
To unsubscribe, send any mail to "freebsd-mobil...@freebsd.org"

jed...@fxp.org

unread,
Feb 26, 2004, 9:56:13 AM2/26/04
to

--3V7upXqbjpZ4EhLz

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 26, 2004 at 06:40:47AM -0600, Sean Welch wrote:
> Chris, this is very interesting. I've been eyeing this machine
> as a posible replacement for my Dell Inspiron 8000 (hate giving
> up the 1600x1200 res screen though...)

>=20

Yeah, the higher resolution is nice.

> A few questions.
>=20


> I looked at your verbose dmesg and wasn't able to tell if your
> sound works (there are a bunch of mss_probe messages) and it
> looks as though you might be having some issue with the
> firewire ethernet mode (sbp messages). Could you clarify?

>=20

The sounds works fine for me, detected as:

pcm0: <VIA VT8235> port 0x1000-0x10ff irq 9 at device 17.5 on pci0

pcm0@pci0:17:5: class=3D0x040100 card=3D0x2032161f chip=3D0x30591106 rev=
=3D0x50 hdr=3D0x00
vendor =3D 'VIA Technologies Inc'
device =3D 'VT8233/33A AC97 Enhanced Audio Controller'
class =3D multimedia
subclass =3D audio

I assume those sbp errors are due to a lack of fireware hardware
on the bus.

> Also, do the sleep modes work for you?

>=20

Dunno, I have not tried yet...

> "project evil" may help you with the wireless chipset.

>=20

Looks promising. I will have to try that.

--=20
Chris D. Faulhaber - jed...@fxp.org - jed...@FreeBSD.org
--------------------------------------------------------
FreeBSD: The Power To Serve - http://www.FreeBSD.org

--3V7upXqbjpZ4EhLz
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
Comment: FreeBSD: The Power To Serve

iD8DBQFAPgiyObaG4P6BelARAqQXAKCB21nq344FRJ203MvBP+GMuGPOPACfejMf
FIVW9mOydsId/ZNmYYN2n/k=
=EK+k
-----END PGP SIGNATURE-----

--3V7upXqbjpZ4EhLz--

jed...@fxp.org

unread,
Feb 26, 2004, 9:56:51 PM2/26/04
to

--tThc/1wpZn/ma/RB

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 26, 2004 at 06:40:47AM -0600, Sean Welch wrote:

> Also, do the sleep modes work for you?

>=20

Not really. Most modes are not supported:

acpi0: Sleep state S1 not supported by BIOS

The laptop appears to suspend ok but does not resume well. It
seems to power back up but the system does not return.

> "project evil" may help you with the wireless chipset.

>=20

Heh, I forgot about Project Evil. Yep, the ndis wrapper works
well. Pure Evil.

ndis0: <Broadcom 54g MaxPerformance 802.11g> mem 0xd0000000-0xd0001fff ir=
q 10 at device 12.0 on pci0
ndis0: NDIS API version: 5.0
ndis0: 802.11 address: 00:90:96:80:6c:d9
ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 36Mbps 48Mbps 54Mbps
ndis0: link up

--=20
Chris D. Faulhaber - jed...@fxp.org - jed...@FreeBSD.org
--------------------------------------------------------
FreeBSD: The Power To Serve - http://www.FreeBSD.org

--tThc/1wpZn/ma/RB
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
Comment: FreeBSD: The Power To Serve

iD8DBQFAPrF0ObaG4P6BelARAiLiAJ91m/EdD7xVMClh04v8rxScGqIdvQCdFDZN
AgiLlujVvAw1jzpzwhxZkZ4=
=lM6i
-----END PGP SIGNATURE-----

--tThc/1wpZn/ma/RB--

Sean_...@alum.wofford.org

unread,
Feb 27, 2004, 6:35:30 PM2/27/04
to
Too bad about the sleep modes. Mine won't resume properly from
s3, but that is a bios issue (I upgraded the graphics card in
my I8K for better performance with DRI).

How is the battery life?

That ndis wrapper is pretty amazing; glad it works for you!

Sean

On Thu, Feb 26, 2004 at 09:54:45PM -0500, Chris Faulhaber wrote:
> On Thu, Feb 26, 2004 at 06:40:47AM -0600, Sean Welch wrote:
> > Also, do the sleep modes work for you?
> >
>

> Not really. Most modes are not supported:
>
> acpi0: Sleep state S1 not supported by BIOS
>
> The laptop appears to suspend ok but does not resume well. It
> seems to power back up but the system does not return.
>
> > "project evil" may help you with the wireless chipset.
> >
>

> Heh, I forgot about Project Evil. Yep, the ndis wrapper works
> well. Pure Evil.
>

> ndis0: <Broadcom 54g MaxPerformance 802.11g> mem 0xd0000000-0xd0001fff irq 10 at device 12.0 on pci0


> ndis0: NDIS API version: 5.0
> ndis0: 802.11 address: 00:90:96:80:6c:d9
> ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
> ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 36Mbps 48Mbps 54Mbps
> ndis0: link up
>
> --

> Chris D. Faulhaber - jed...@fxp.org - jed...@FreeBSD.org
> --------------------------------------------------------
> FreeBSD: The Power To Serve - http://www.FreeBSD.org

b...@spc.org

unread,
Feb 28, 2004, 2:05:33 AM2/28/04
to

--vmttodhTwj0NAgWp

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Feb 26, 2004 at 09:54:45PM -0500, Chris Faulhaber wrote:
> Heh, I forgot about Project Evil. Yep, the ndis wrapper works
> well. Pure Evil.

>=20
> ndis0: <Broadcom 54g MaxPerformance 802.11g> mem 0xd0000000-0xd0001fff =
irq 10 at device 12.0 on pci0

Does anybody have any idea what it would take to make if_ndis(4) support
radiotap (DLT_IEEE802_11_RADIO) ? This would be more Evil.

I don't have an ndis wireless device with which to test/hack at this time.

BMS

--vmttodhTwj0NAgWp
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Comment: ''

iD8DBQFAQD1VueUpAYYNtTsRAqZpAJ9jJL22yhgQ61/xLV3V5DuuaEFREgCfTfal
vzQ8/xIp0Wssf4+eDqlP0P0=
=02pr
-----END PGP SIGNATURE-----

--vmttodhTwj0NAgWp--

wp...@freebsd.org

unread,
Feb 28, 2004, 10:01:06 PM2/28/04
to
> On Thu, Feb 26, 2004 at 09:54:45PM -0500, Chris Faulhaber wrote:
> > Heh, I forgot about Project Evil. Yep, the ndis wrapper works
> > well. Pure Evil.
> >
> > ndis0: <Broadcom 54g MaxPerformance 802.11g> mem 0xd0000000-0xd0001fff irq 10 at device 12.0 on pci0

>
> Does anybody have any idea what it would take to make if_ndis(4) support
> radiotap (DLT_IEEE802_11_RADIO) ? This would be more Evil.
>
> I don't have an ndis wireless device with which to test/hack at this time.
>
> BMS

For the umpity-umpth time: existing Windows NDIS drivers are implemented
using the 802.3 (ethernet) link type. They don't support monitor mode or
raw 802.11 frame formats, so it is not possible to implement radiotap
with them.

Any vendor that claims to let you read/send raw 802.11 frames with
their device has implemented a non-standard interface that falls outside
the NDIS API.

-Bill

--
=============================================================================
-Bill Paul (510) 749-2329 | Senior Engineer, Master of Unix-Fu
wp...@windriver.com | Wind River Systems
=============================================================================
<adamw> you're just BEGGING to face the moose
=============================================================================

0 new messages