login
Search
This is a multi-part message in MIME format.
--------------060607070709070301020503
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printableHi,
If anyone's interested, here's dmesg and pciconf for Asus' EEE PC.
Apparently everything works except the network and the wireless cards.--------------060607070709070301020503
Content-Type: text/plain;
name="eee-pciconf.txt"
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename="eee-pciconf.txt"aG9zdGIwQHBjaTA6MDowOgljbGFzcz0weDA2MDAwMCBjYXJkPTB4ODJkOTEwNDMgY2hpcD0w
eDI1OTA4MDg2IHJldj0weDA0IGhkcj0weDAwCiAgICBjbGFzcyAgICA9IGJyaWRnZQogICAg
c3ViY2xhc3MgPSBIT1NULVBDSQphZ3AwQHBjaTA6MjowOgljbGFzcz0weDAzMDAwMCBjYXJk
PTB4ODJkOTEwNDMgY2hpcD0weDI1OTI4MDg2IHJldj0weDA0IGhkcj0weDAwCiAgICBjbGFz
cyAgICA9IGRpc3BsYXkKICAgIHN1YmNsYXNzID0gVkdBCm5vbmUwQHBjaTA6MjoxOgljbGFz
cz0weDAzODAwMCBjYXJkPTB4ODJkOTEwNDMgY2hpcD0weDI3OTI4MDg2IHJldj0weDA0IGhk
cj0weDAwCiAgICBjbGFzcyAgICA9IGRpc3BsYXkKbm9uZTFAcGNpMDoyNzowOgljbGFzcz0w
eDA0MDMwMCBjYXJkPTB4ODJhMTEwNDMgY2hpcD0weDI2Njg4MDg2IHJldj0weDA0IGhkcj0w
eDAwCiAgICBjbGFzcyAgICA9IG11bHRpbWVkaWEKcGNpYjFAcGNpMDoyODowOgljbGFzcz0w
eDA2MDQwMCBjYXJkPTB4MDAwMDAwNDAgY2hpcD0weDI2NjA4MDg2IHJldj0weDA0IGhkcj0w
eDAxCiAgICBjbGFzcyAgICA9IGJyaWRnZQogICAgc3ViY2xhc3MgPSBQQ0ktUENJCnBjaWIy
QHBjaTA6Mjg6MToJY2xhc3M9MHgwNjA0MDAgY2FyZD0weDAwMDAwMDQwIGNoaXA9MHgyNjYy
ODA4NiByZXY9MHgwNCBoZHI9MHgwMQogICAgY2xhc3MgICAgPSBicmlkZ2UKICAgIHN1YmNs
YXNzID0gUENJLVBDSQpwY2liM0BwY2kwOjI4OjI6CWNsYXNzPTB4MDYwNDAwIGNhcmQ9MHgw
MDAwMDA0MCBjaGlwPTB4MjY2NDgwODYgcmV2PTB4MDQgaGRyPTB4MDEKICAgIGNsYXNzICAg
ID0gYnJpZGdlCiAgICBzdWJjbGFzcyA9IFBDSS1QQ0kKdWhjaTBAcGNpMDoyOTowOgljbGFz
cz0weDBjMDMwMCBjYXJkPTB4ODJkODEwNDMgY2hpcD0weDI2NTg4MDg2IHJldj0weDA0IGhk
cj0weDAwCiAgICBjbGFzcyAgICA9IHNlcmlhbCBidXMKICAgIHN1YmNsYXNzID0gVVNCCnVo
Y2kxQHBjaTA6Mjk6MToJY2xhc3M9MHgwYzAzMDAgY2FyZD0weDgyZDgxMDQzIGNoaXA9MHgy
NjU5ODA4NiByZXY9MHgwNCBoZHI9MHgwMAogICAgY2xhc3MgICAgPSBzZXJpYWwgYnVzCiAg
ICBzdWJjbGFzcyA9IFVTQgp1aGNpMkBwY2kwOjI5OjI6CWNsYXNzPTB4M...
One of the guys I know is running FreeBSD on the Eee, and has written
up the following information for anyone who is interested in doing
what he did:http://nighthack.org/wiki/EeeBSD
This includes tips on how to get the wireless working, and sound,
and some oddities with how X11 works.--
Garance Alistair Drosehn = drosehn@rpi.edu
Senior Systems Programmer or gad@FreeBSD.org
Rensselaer Polytechnic Institute; Troy, NY; USA
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Well, I searched the wiki and I found no contact email, so I'm posting
here hoping that you can contact him.Perhaps he wants to use the Xorg intel driver instead of i815? This
way he probably doesn't need 915resolution anymore (if the LCD reports
the correct size, the intel driver will use it).Regards.
--
Rui Paulo_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Over this past weekend, he updated his web page based on your comments,
and feedback from a few other people. It looks like there's a fair
number of people who are interested in running FreeBSD (or one of the
other BSD's) on the ASUS Eee.--
Garance Alistair Drosehn = drosehn@rpi.edu
Senior Systems Programmer or gad@FreeBSD.org
Rensselaer Polytechnic Institute; Troy, NY; USA
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Cool, thanks :-)
--
Rui Paulo_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
=2E.. the intended meaning was "everything I expected to work". The video=
camera obviously doesn't work, but I think audio should, if it's AC97.
Do you know what network chip it uses?
-Kip
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
One of my friends has an Eee with freebsd working on it. I believe
he had to do some work to get the network card running, but he has
it working okay now. I'll see if he's following this mailing list.--
Garance Alistair Drosehn = gad@gilead.netel.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Dang did he keep a record of what he did? Will he share? Which FreeBSD
version? Does it support the touchpad? Please shackle him to a
terminal for answers to these and other pressing questions
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
On Wed, Jan 02, 2008 at 04:51:14PM -0500, Garance A Drosihn wrote:
> At 1:12 PM -0800 1/2/08, Kip Macy wrote:
> >Do you know what network chip it uses?
> >
> > -Kip
>
> One of my friends has an Eee with freebsd working on it. I believe
> he had to do some work to get the network card running, but he has
> it working okay now. I'll see if he's following this mailing list.
>I'm also interesting in Atheros(Attansic) PHY. One user reported
nfe(4) stability issues on CURRENT and I noticed the PHY was made by
Atheros.
http://lists.freebsd.org/pipermail/freebsd-current/2007-December/081560....I even wrote a simple PHY driver for it but I need more information
for the PHY hardware. You can get a latest atphy(4) at the following
URL. The PHY driver doesn't take care of fast ethernet PHY so it
needs more work.(Note, I don't have any Attansic hardwares so it's
guess work and it may not even work at all.)
http://people.freebsd.org/~yongari/atphy.diff--
Regards,
Pyun YongHyeon
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Not exactly, but apparently it's very well supported under Linux and
Windows since Google doesn't find anything useful on the topic.I found this in the Linux drivers' source code:
* Copyright(c) 2007 Atheros Corporation. All rights reserved.
* Copyright(c) 2006 xiong huang <xiong.huang@atheros.com>
*
* Derived from Intel e1000 driver
* Copyright(c) 1999 - 2005 Intel Corporation. All rights reserved.The Linux driver is here:
http://support.asus.com/download/download.aspx?SLanguage=3Den-us&model=3D=
Eee%20PC%204G(701)&type=3Dmap&mapindex=3D8
(atl2_1.0.40.4-4.tar.gz)I don't have the device anymore but will probably have it in a few weeks.=
On Wed, Jan 02, 2008 at 10:26:06PM +0100, Ivan Voras wrote:
> Kip Macy wrote:
> > Do you know what network chip it uses?
>
> Not exactly, but apparently it's very well supported under Linux and
> Windows since Google doesn't find anything useful on the topic.
>
> I found this in the Linux drivers' source code:
>
> * Copyright(c) 2007 Atheros Corporation. All rights reserved.
> * Copyright(c) 2006 xiong huang <xiong.huang@atheros.com>
> *
> * Derived from Intel e1000 driver
> * Copyright(c) 1999 - 2005 Intel Corporation. All rights reserved.
>
> The Linux driver is here:
>
> http://support.asus.com/download/download.aspx?SLanguage=en-us&model=Eee%20PC%204G(701)&type=map&mapindex=8
> (atl2_1.0.40.4-4.tar.gz)
>
> I don't have the device anymore but will probably have it in a few weeks.
>AFAIK kevlo@(Kevin Lo) is working on Attansic L1. Not sure his driver
also supports fast ethernet version(Attansic F2). I don't know current
status of the driver but it seems that he has a working driver.
Btw, you can also use a NDIS mini port driver until native driver hits
tree.--
Regards,
Pyun YongHyeon
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Yes, I worked on Attansic L1 driver which was based on Linux atl1
driver.
I sent my patch to Alex Lukin four months ago:http://unix.derkeiler.com/Mailing-Lists/FreeBSD/hackers/2007-09/msg00081...
Don't know whether he is still working on it or not. If not, I'll finish
it :-)Kevin
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Hello,
I have tried the ndis. The loadable kernel build sucessfully using the
lan/attansic/ris/winxp_32/l251x86.sys/inf file from the DVD.The module kernel build successfully and give :
ndis0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
ether 00:1e:8c:bc:9f:7a
media: Ethernet autoselect
status: no carrierThe /var/log/messages say :
Feb 7 15:32:16 eeehpc kernel: no match for KeBugCheckEx
Feb 7 15:32:16 eeehpc kernel: no match for KeTickCount
Feb 7 15:32:16 eeehpc kernel: no match for RtlUpcaseUnicodeString
Feb 7 15:32:16 eeehpc kernel: ndis0: <Atheros L2 Fast Ethernet 10/100
Base-T Controller> mem 0xfbfc0000-0xfbffffff irq 17 at device 0.0 on
pci3
Feb 7 15:32:16 eeehpc kernel: ndis0: [ITHREAD]
Feb 7 15:32:16 eeehpc kernel: ndis0: NDIS API version: 5.1
Feb 7 15:32:17 eeehpc kernel: ndis0: using obsoleted if_watchdog interface
Feb 7 15:32:17 eeehpc kernel: ndis0: Ethernet address: 00:1e:8c:bc:9f:7aCould you post your patch, I'm interessted to give a try !
The most annoying think is the Fn+F5 (switch from lcd to the VGA port)
which doesn't work. It's the only reason I don't swith from xandros to
FreeBSD on my machine (I actually use a bootable usb key for my
trials). Any idea to debug this problem ?--
HPC
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
The chip is an Atheros (formerly Attansic) L2. Even though it claims to
be derived from the e1000 driver, I believe they just used it as a
reference on writing Linux device drivers; I don't think it's really
related to the e1000 hardware at all.-Ed
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Chuck Ebbert | Why do so many machines need "noapic"? |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Natalie Protasevich | [BUG] New Kernel Bugs |
