OpenBSD Journal

Developer blog - reyk@: more about EeePC

Contributed by johan on from the donations-really-do-help dept.

In a recent story we highlighted that Reyk Floeter (reyk@) had asked for an Asus EeePC in order to improve support for newer ath(4) chips. Reyk since received two EeePC donations and has been hard at work improving ath(4). While doing so he encountered some issues with these computers, here is his follow up story...

When I fixed support for a number of newer ath(4) variants, I asked for an EeePC donation to work on the currently unsupported wireless chipset that is integrated in most of these mini-laptops. Just about one week later I got two donations - an EeePC 701 and an EeePC 900. And I had more donation offers from other users, I really appreciate your support!

It will need some time to fix the wireless support, but it also helps to work on various other issues that we see on these machines: interrupt routing (with help from kettenis@), camera support (with help from mglocker@), ACPI (with help from marco@) and I also want to improve the lii(4) driver (to be fair, lii was written by the author without documentation since it is a chipset that is now owned by Atheros).

Please read on for the rest of the story...

Both EeePCs require ACPI to work correctly, but for some reason the BIOS still provides APM. ACPI is not enabled by the kernel if APM is detected, so you need to manually disable the apm(4) device to get ACPI on boot. The EeePC 701 can be installed with the normal installation sets, but the EeePC 900 is a little bit trickier; I decided to write a short guide on installing the 900 until we found a way to fix it in the default OpenBSD installer.

  • Create a multi processor (MP) version of bsd.rd on another i386 OpenBSD build machine. The EeePC 900 is a single core machine, but the MP kernel also enables IOAPICs and a slightly different interrupt handling.
    # cd /usr/src/sys/arch/i386/conf
    # sed "s/^apm0.*/apm0 at bios0 disabled/" RAMDISK_CD > RAMDISK_CD.eeepc
    # sed "s/GENERIC/RAMDISK_CD.eeepc/" GENERIC.MP > RAMDISK_CD
    # cd /usr/src/distrib/special/libstubs && \
            make obj && make depend && make all && make install
    # cd /usr/src/distrib/crunch && \
            make obj && make depend && make all && make install
    # cd /usr/src/distrib/i386/ramdisk_cd && \
            make obj && make depend && make all
    
  • Create a bootable USB stick (sd1 in this example):
    # fdisk -i sd1
    # disklabel -E sd1
    > a a                   (use the defaults)
    > w
    > q
    # newfs rsd1a
    # mount /dev/sd1a /mnt
    # cp /usr/mdec/boot /mnt/boot
    # /usr/mdec/installboot -v /mnt/boot /usr/mdec/biosboot sd1
    # cp /usr/src/distrib/i386/ramdisk_cd/obj/bsd.rd /mnt/bsd
    # umount /mnt
    
  • Install the EeePC900: insert the USB stick and press ESC on boot to get the EeePC BIOS boot dialog. Select the USB device and continue... In the OpenBSD installation make sure to select "bsd.mp" as well.
    
    
  • After installation, make sure to boot bsd.mp with apm(4) disabled
    boot> boot bsd.mp -c
    ...
    UKC> disable apm
    UKC> quit
    
  • Store the bsd.mp settings for the next reboots (if you don't want to compile your own modified kernel):
    eeepc900# config -ef /bsd.mp
    > disable apm
    > quit
    eeepc900# echo set image bsd.mp > /etc/boot.conf
    

Here is the dmesg of the EeePC 900:

OpenBSD 4.4 (GENERIC.MP) #839: Wed Aug  6 00:15:05 MDT 2008
    deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Celeron(R) M processor 900MHz ("GenuineIntel" 686-class) 901 MHz
cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,CFLUSH,DS,
ACPI,MMX,FXSR,SSE,SSE2,SS,TM,SBF
real mem  = 1064398848 (1015MB)
avail mem = 1020715008 (973MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 06/10/08, BIOS32 rev. 0 @ 0xf0010, SMBIOS rev.
2.5 @ 0xf06f0 (37 entries)
bios0: vendor American Megatrends Inc. version "0704" date 06/10/2008
bios0: ASUSTeK Computer INC. 900
apm at bios0 function 0x15 not configured
acpi0 at bios0: rev 0
acpi0: tables DSDT FACP APIC OEMB MCFG
acpi0: wakeup devices P0P3(S4) P0P4(S4) P0P5(S4) P0P6(S4) P0P7(S4) MC97(S4) USB1(S3)
 USB2(S3) USB3(S3) USB4(S3) EUSB(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee00000: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 100MHz
ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 20, 24 pins
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 5 (P0P3)
acpiprt2 at acpi0: bus 3 (P0P5)
acpiprt3 at acpi0: bus 1 (P0P6)
acpiec0 at acpi0
acpicpu0 at acpi0
acpicpu0 at acpi0: C3, C2
acpitz0 at acpi0: critical temperature 90 degC
acpibat0 at acpi0: BAT0 model "900" serial   type LION oem "ASUS"
acpiac0 at acpi0: AC unit online
acpiasus0 at acpi0
acpibtn0 at acpi0: LID_
acpibtn1 at acpi0: SLPB
acpibtn2 at acpi0: PWRB
acpivideo at acpi0 not configured
bios0: ROM list: 0xc0000/0xf800!
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82915GM Host" rev 0x04
vga1 at pci0 dev 2 function 0 "Intel 82915GM Video" rev 0x04
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
agp0 at vga1: aperture at 0xd0000000, size 0x10000000
drm at vga1 unsupported
"Intel 82915GM Video" rev 0x04 at pci0 dev 2 function 1 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801FB HD Audio" rev 0x04: apic 1 int 16
(irq 5)
azalia0: codec[s]: Realtek/0x0662
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801FB PCIE" rev 0x04: apic 1 int 16 (irq 5)
pci1 at ppb0 bus 4
ppb1 at pci0 dev 28 function 1 "Intel 82801FB PCIE" rev 0x04: apic 1 int 17 (irq 11)
pci2 at ppb1 bus 3
lii0 at pci2 dev 0 function 0 "Attansic Technology L2" rev 0xa0: apic 1 int 17
(irq 11), address 00:1f:c6:8f:0d:ee
ukphy0 at lii0 phy 1: Generic IEEE 802.3u media interface, rev. 2: OUI 0x001374,
model 0x0002
ppb2 at pci0 dev 28 function 2 "Intel 82801FB PCIE" rev 0x04: apic 1 int 18 (irq 10)
pci3 at ppb2 bus 1
ath0 at pci3 dev 0 function 0 "Atheros AR5424" rev 0x01: apic 1 int 18 (irq 10)
ath0: AR5424 14.2 phy 7.0 rf 0.0, WOR0W, address 00:15:af:a7:3d:55
uhci0 at pci0 dev 29 function 0 "Intel 82801FB USB" rev 0x04: apic 1 int 23 (irq 3)
uhci1 at pci0 dev 29 function 1 "Intel 82801FB USB" rev 0x04: apic 1 int 19 (irq 7)
uhci2 at pci0 dev 29 function 2 "Intel 82801FB USB" rev 0x04: apic 1 int 18 (irq 10)
uhci3 at pci0 dev 29 function 3 "Intel 82801FB USB" rev 0x04: apic 1 int 16 (irq 5)
ehci0 at pci0 dev 29 function 7 "Intel 82801FB USB" rev 0x04: apic 1 int 23 (irq 3)
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BAM Hub-to-PCI" rev 0xd4
pci4 at ppb3 bus 5
ichpcib0 at pci0 dev 31 function 0 "Intel 82801FBM LPC" rev 0x04: PM disabled
pciide0 at pci0 dev 31 function 2 "Intel 82801FBM SATA" rev 0x04: DMA, channel 0
wired to compatibility, channel 1 wired to compatibility
wd0 at pciide0 channel 1 drive 0: 
wd0: 1-sector PIO, LBA, 3847MB, 7880544 sectors
wd1 at pciide0 channel 1 drive 1: 
wd1: 1-sector PIO, LBA, 7695MB, 15761088 sectors
wd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 4
wd1(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 4
ichiic0 at pci0 dev 31 function 3 "Intel 82801FB SMBus" rev 0x04: apic 1 int 19
(irq 0) iic0 at ichiic0
spdmem0 at iic0 addr 0x50: 1GB DDR2 SDRAM non-parity PC2-3200CL5 SO-DIMM
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 "Intel UHCI root hub" rev 1.00/1.00 addr 1
usb4 at uhci3: USB revision 1.0
uhub4 at usb4 "Intel UHCI root hub" rev 1.00/1.00 addr 1
isa0 at ichpcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pmsi0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pmsi0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: 
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
mtrr: Pentium Pro MTRR support
umass0 at uhub0 port 5 configuration 1 interface 0 "ENE UB6225" rev 2.00/1.00 addr 2
umass0: using SCSI over Bulk-Only
scsibus0 at umass0: 2 targets, initiator 0
sd0 at scsibus0 targ 1 lun 0:  SCSI0 0/direct removable
sd0: drive offline
uvideo0 at uhub4 port 2 configuration 1 interface 0 "Chicony Electronics Co., Ltd.
 CNF7129" rev 2.00/15.12 addr 2
video0 at uvideo0
softraid0 at root
root on wd0a swap on wd0b dump on wd0b

This story really goes to show how important donations are, so please, read through want.html and try to find an item you can donate.

(Comments are closed)


Comments
  1. By Karl Sjödahl (dunceor) dunceor@gmail.com on

    Sweet that an developer has gotten the eeepc because it looks like they are very popular which means a lot of people will try and run OpenBSD on them. I plan to buy a 901 soon, any success stories with that one?
    Keep up the good work!

    Comments
    1. By Anonymous Coward (151.136.100.2) on

      "an developer"
      holy moses!

      Comments
      1. By Karl Sjödahl (dunceor) on

        > "an developer"
        > holy moses!

        Holy bill of rights Batman!

      2. By Anonymous Coward (81.30.249.67) on

        Some people are not good in english,because it isn't their native language.

        So please stop this bullshits ;-) If you like this flamewars -> find another OS.

        > "an developer"
        > holy moses!

        Comments
        1. By Anonymous Coward (151.136.100.2) on

          > Some people are not good in english,because it isn't their native language.

          no reason not to improve.
          this whole attitude of "do not tell me i was wrong"
          will lead nowhere...

          Comments
          1. By goodb0fh@gmail.com (71.127.154.43) goodb0fh@gmail.com on

            > > Some people are not good in english,because it isn't their native language.
            >
            > no reason not to improve.
            > this whole attitude of "do not tell me i was wrong"
            > will lead nowhere...

            And this whole nitpicking hairsplitting stuff is what advances civilizations.

      3. By Anonymous Coward (84.245.6.55) on

        > "an developer"
        > holy moses!

        This journal is for openbsd dev news.
        so please keep that in mind.

        you could say he made a spelling error, but not in this way.
        (im also a not native english speaker so i make more errors than native english speakers)

        p.s.

        were here to learn from each other not the make fun of each other.

        Comments
        1. By Anonymous Coward (128.171.90.200) on

          > > "an developer"
          > were here to learn from each other not the make fun of each other.

          What a good point, so Karl, in english english me ol' china, you use 'an' if the letter starting the next word is a vowel, otherwise just use an 'a', c ?

          an orange
          an apple
          a banana
          a pear

          an installation CD
          an OpenBSD installation
          a CD for installing OpenBSD

          an eeepc

          There may be a few corner cases I haven't thought of, but that will do in most situations. Oh and 84.245.6.55, it is "we're here to learn" it is a contraction of 'we' and 'are' and so is separated by an apostrophe ( or 'okina if you da kine brah ! )

          Right, back to the hack !

          Comments
          1. By Anonymous Coward (84.245.6.55) on

            > an eeepc

            Isin't an Eee PC?

            Comments
            1. By Anonymous Coward (128.171.90.200) on

              > > an eeepc
              >
              > Isin't an Eee PC?

              No, it's pronounced eeeeeepucuh

          2. Comments
            1. By Anonymous Coward (219.90.182.70) on

              An holy moses.

              Am I the only one who's always thought that rule made things sound ridiculous and unnatural?

            2. By tedu (74.68.146.146) on

              "The is pronounced with an er sound, as in mother, father, brother, before a noun or an adjective beginning with a consonant or a consonant sound"


              crazy funny talkers!

            3. By Anonymous Coward (128.171.90.200) on

              > > What a good point, so Karl, in english english me ol' china, you use 'an' if the letter starting the next word is a vowel, otherwise just use an 'a', c ?
              >
              > vowel *sound*, me old mucker.

              Ah, that probably is correct, vowels tend to dominate the vowel sounds so it holds for the most part. English english is full of odd pronunciations so it would not surprise me one bit if the corner non vowel cases are just words which sound like they start with a vowel. Cheers ears.

              Comments
              1. By Gimlet (67.108.81.126) on


                > Ah, that probably is correct, vowels tend to dominate the vowel sounds so it holds for the most part. English english is full of odd pronunciations so it would not surprise me one bit if the corner non vowel cases are just words which sound like they start with a vowel. Cheers ears.
                >


                English has an extremely high rate of change, and there are an extremely large number of loan words from other languages. So, many words end up with a spelling from an archaic version. A good example is the word "knight," which used to be pronounced similarly to its German relative, "Knecht."

            4. By Anonymous Coward (84.198.96.249) on

              > vowel *sound*, me old mucker.

              You're correct. Now all that's left is to teach Americans that the "h" is NEVER ignored. It's a hard consonnant. There's no such things as "erbs".

              Comments
              1. By Anonymous Coward (88.23.210.207) on

                > > vowel *sound*, me old mucker.
                >
                > You're correct. Now all that's left is to teach Americans that the "h" is NEVER ignored. It's a hard consonnant. There's no such things as "erbs".
                >
                >

                what about

                "An hour"

                ?

                haha...

              2. By goodb0fh@gmail.com (71.127.154.43) goodb0fh@gmail.com on

                > > vowel *sound*, me old mucker.
                >
                > You're correct. Now all that's left is to teach Americans that the "h" is NEVER ignored. It's a hard consonnant. There's no such things as "erbs".
                >
                No no no, aluminium, teach them that. Otherwise, it's sodum, lithum, caesum, californum and americum.

                Comments
                1. By CODOR (CODOR) on

                  > No no no, aluminium, teach them that. Otherwise, it's sodum, lithum, caesum, californum and americum.

                  And platinium. Don't forget platinium!

                  Comments
                  1. By Miod Vallat (miod) on

                    > > No no no, aluminium, teach them that. Otherwise, it's sodum, lithum, caesum, californum and americum.
                    >
                    > And platinium. Don't forget platinium!

                    But then, what's a bignium???

      4. By Anonymous Coward (85.222.21.198) on

        > "an developer"
        > holy moses!

        Holly shit, an nasty shit
        Sheep on ship, look on loop, it's an very hasty troop
        So pull an bull via git or clit
        Leave an sieve and go to hive!

        http://www.simpsonstrivia.com.ar/simpsons-photos/wallpapers/bumble-bee-man.gif

    2. By Simon Lundström (simmel) on

      > Sweet that an developer has gotten the eeepc because it looks like they are very popular which means a lot of people will try and run OpenBSD on them. I plan to buy a 901 soon, any success stories with that one?
      > Keep up the good work!

      I bought a 901 and I've been trying to get OpenBSD installed on a USB-stick for it, but failed for various reasons.

      The wlan card is supported but not the wired card. One can download Linux drivers from ASUS (http://dlsvr01.asus.com/pub/ASUS/mb/socket775/P5KPL-CM/LinuxDrivers.zip) so OpenBSD devs have something to go on even if specs are better..

      I've successfully booted an 4.2 stick which jj@ had and that works, but I want to install a snapshot.

  2. By minusf (58.91.133.98) on

    hey,

    it's been a long way since this year's january for the eeepc(701) for openbsd...
    it is very usable now, *but* (and hopefully lots of people having it will read
    this thread) here are a couple of issues i am seeing and maybe others
    have ideas how to solve them. actually, it is way more usable with acpi
    (hear hear).

    1. fan. if the fan comes on---basically after running anything like firefox/gimp/etc
    it never stops again. i am not sure if this is bios or OS issue, but sometimes under
    xandros it stops again, or starts later. this is not really a nuissance, it's not that
    loud, purely a battery issue.

    2. acpi quirks. more or less acpi works ok on this one now, the fn keys work except
    the obvious candidates, BUT, sometimes they stop responding. e.g. try lowering
    the screen brightness right logging in in xdm. press it 10, 15x. the fn keys stop
    responding after this.

    3. halting the machine. actually this is not only an eeepc issue, my previous toshiba
    had it too. when i type halt, all the programs stop, so i get to the console. but the
    "syncing disk..." sometimes appears 20-30-40 seconds after this, and "done" never
    comes. a couple of times i even let it turned on overnight, still no "done".
    my limited experiments in ddb showed nothing.

    4. has anyone tried running hotplugd? it locks up the machine after a couple of
    seconds/minutes. syslog is hammered with devices appearing and disappearing.
    (admittedly i havent tried this with more recent snapshots, and i will, i just mention
    it if others see it).

    the halt issue is the one that bothers me the most and i would appreciate any
    advice hunting it down. btw. i am running from sd0, a usb stick, wd0 is still
    the linux.

    Comments
    1. By Anonymous Coward (128.171.90.200) on

      > the halt issue is the one that bothers me the most and i would appreciate any
      > advice hunting it down.

      I had a similar problem on another machine, I know I will get panned for telling you this, but what I did was rebuild my system, though you might get away with just rebuilding the kernel. I don't know why it worked for me, and I am slightly annoyed that it fixed it, but I was rebuilding my system anyway and it happened to work. This was 4.3 base.

      Good luck.

    2. By Anonymous Coward (72.174.27.134) on

      > 1. fan.

      Possibly an ACPI issue...

      > 2. acpi quirks.

      ...which reyk@ has said is on his punchlist for these machines...

      > 3. halting the machine.

      ...which will also probably fix this issue.

      > 4. has anyone tried running hotplugd?

      set ddb.console to 1 in sysctl.conf, re-freeze the machine, and dump into ddb and grab as much info from there as you can before you write up a problem report and file it via sendbug(1).

      Comments
      1. By minusf (220.219.220.118) on

        > ...which reyk@ has said is on his punchlist for these machines...
        >
        > > 3. halting the machine.

        i think this might be acpi independent. it's not the act of halting the
        machine and/or turning it off. the syncing just never finishes. it is
        the same with the apm version.


        > > 4. has anyone tried running hotplugd?
        >
        > set ddb.console to 1 in sysctl.conf, re-freeze the machine, and dump into ddb and grab as much info from there as you can before you write up a problem report and file it via sendbug(1).

        yesterday i tried this again. first it worked flawlessly so i thought i made a fool
        of myself. the only strange thing was a couple of zombie sh processes which
        i think were somehow related to /etc/hotplug/attach. my attach script uses logger(1)
        to show the disklabel of an attached device, and the sd card reader showed up
        right after starting hotplugd, it is emulated as an usb device, but i don't know
        why it shows up as if attached just then, like my mouse it was "attached" at boot
        time. my suspicion is, that this device might send endless attach/detach events
        and that is the reason hotplugd locks up the system. unfortunately there is nothing
        in the logs at all. and sometimes work as i wrote before...

        i will try again, but after the machine locks up, there is no accessible ddb anymore...

        interesting that noone else sees these issues....

    3. By minusf (220.219.220.118) on

      oh and to make the list complete (i am not complaining of course),
      i forgot to add that copying large files (e.g. movie) to sd cards doesn't
      work either. it stops mid-write and hangs. after cancelling the write
      everything is back at "normal".

      Comments
      1. By Anonymous Coward (89.104.120.231) on

        > oh and to make the list complete (i am not complaining of course),
        > i forgot to add that copying large files (e.g. movie) to sd cards doesn't
        > work either. it stops mid-write and hangs. after cancelling the write
        > everything is back at "normal".

        this is likely to be a hardware problem with a card reader chip. the
        problem seems to go away if you make it use usb1.1 (disable ehci for
        example). freebsd dudes also advise to do this.

        Comments
        1. By Anonymous Coward (89.104.120.231) on

          > > oh and to make the list complete (i am not complaining of course),
          > > i forgot to add that copying large files (e.g. movie) to sd cards doesn't
          > > work either. it stops mid-write and hangs. after cancelling the write
          > > everything is back at "normal".
          >
          > this is likely to be a hardware problem with a card reader chip. the
          > problem seems to go away if you make it use usb1.1 (disable ehci for
          > example). freebsd dudes also advise to do this.
          >

          and this might also help with a hotplugd issue.

  3. By Brynet (Brynet) on

    Hi,

    In the above dmesg:
    oapic0 at mainbus0: apid 1 pa 0xfec00000, version 20, 24 pins

    Should probably be:
    ioapic0 at mainbus0: apid 1 pa 0xfec00000, version 20, 24 pins

    Was that some sort of typographical error? or was the dmesg actually managed at boot?

    Regardless, reyk@ is awesome.. great work, the people who donated, as well.. :)

  4. By Anonymous Coward (60.53.20.129) on

    Is it possible to use OpenBSD in Sony PS3?

    Comments
    1. By Brynet (Brynet) on

      > Is it possible to use OpenBSD in Sony PS3?

      All 3rd party OS's for the PS3 run inside some sort of hypervisor, severely limiting access to the hardware.

      Q1) Is it possible?
      A1) Yes..

      Q2) Should the person who ports it be congratulated?
      A2) Probably not..

      Comments
      1. By Brynet (Brynet) on

        > > Is it possible to use OpenBSD in Sony PS3?
        >
        > All 3rd party OS's for the PS3 run inside some sort of hypervisor, severely limiting access to the hardware.
        >
        > Q1) Is it possible?
        > A1) Yes..
        >
        > Q2) Should the person who ports it be congratulated?
        > A2) Probably not..

        Looks like their was the start of a NetBSD port, I don't know.. guess it might be somewhat useful, developers are still limited with what they can do though.

  5. By Anonymous Coward (66.42.183.218) on

    Thanks to reyk for his work with the Eee PC, and other OpenBSD work generally.

    I'd really hope that OpenBSD developers get what they want with supporting these new small computers.
    I'm holding out for possibly an Asus Eee PC 904, although Dell and Lenovo are coming out with E and S series computers soon.

    Small computers could be revolutionary and a major hit like cell phone were. Hopefully this would lead to more people buying OpenBSD CDs and donations.
    My point again is simple, I'm pleading to those with money and business, who might be reading this blog or read this comment somehow, to donate what OpenBSD wants in this area.

    Small quality computers running OpenBSD, priceless and critical to productivity. What everybody should have.

    Peace.

    Comments
    1. By GRH (66.223.252.146) on

      I'd also like to thank Reyk for his work. I've been running -current on my 701 for a while and generally it works great. Getting the wireless working would be the icing on the cake.

      One odd thing with the current lii driver is that appears as though the link detection doesn't work unless the cable is connected when the EEE boots.

      As for the halt issue, the sync is working fine for me, but I'm still letting the kernel boot with APM enabled, so ACPI is out. Relevant? I dunno.


  6. By Tobias Weingartner (129.128.184.101) weingart@tepid.org on

    I've updated the cpuid.c file some (posted/asked for tests on tech@ a while ago). If there are any people with brand new CPU's out there (Nano/etc), that can compile/run this, I'd appreciate an email with
    the output.

    http://www.tepid.org/~weingart/cpuid.c

    A simple 'make cpuid && ./cpuid' should work on both i386 and amd64.

    -Toby.

  7. By packeteer (150.101.122.57) on

    I've just got myself an old 7" eeePC. Unfortunately 4.5 doesn't seem to like the ethernet nic (lii).

    Complains about having "no carrier".

    Gonna try a 4.6 snapshot...

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]