Hey guys. I have been wanting to find an unbranded, generic netbook that we could maybe gain full hardware support for, which we could maybe bundle and sell to people similar to the iMica and AresOne. I have been testing this netbook with Aros for a while now, and while everything runs fine, the video, sound and network cards are of course not supported yet. Through VESA, I'm able to use the native resolution of 1024x576 (I ordered a 1024x600 model but they sent me this!), but it would be great if I could go online with it and hear sound like I can on my borrowed Acer Aspire 3610.

The reason for choosing this netbook over a branded one is that the specifications are practically the same, but this one costs half (or less) as much as branded netbooks, and I think it looks better too. It also means we can badge it ourselves and make it feel more official, if it's chosen as our first official Aros netbook candidate.

I'm aware of a few different models of unbranded netbooks, all available in bulk (as this one is), so it's possible others are available with different chipsets but the same case design and similar pricing. I know for sure there's definitely a model that looks exactly the same as mine but with a 1024x600 screen instead of this 576 one.

Anyway, if anyone is interested and maybe knows more about hardware compatibility than me, please jump in. Here's the output from PCITool:


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Bridge Host-PCI
Vendor name: Intel Corporation
Product name: Mobile 945GME Express Memory Controller Hub
Subsystem: Intel Corporation : 0x27ac
VendorID: 0x8086
ProductID: 0x27ac
RevisionID: 0x0003
Class: 0x06
Subclass: 0x00
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: N/A
Status: IO: no, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar0: Memory at 0xfea80000 (size 0x80000)
RangeList_1: Bar1: I/O at 0xdc80 (size 0x8)
RangeList_2: Bar2: Prefetchable Memory at 0xd0000000 (size 0x10000000)
RangeList_3: Bar3: Memory at 0xfea40000 (size 0x40000)
RangeList_4: Prefetchable ranges memory from fff10000 to 00010000
RangeList_5: IO ranges from e000 to e000


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Video PC Compatible VGA
Vendor name: Intel Corporation
Product name: Mobile 945GME Express Integrated Graphics Controller
Subsystem: Intel Corporation : 0x27ae
VendorID: 0x8086
ProductID: 0x27ae
RevisionID: 0x0003
Class: 0x03
Subclass: 0x00
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: 10 (A)
Status: IO: yes, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar0: Memory at 0xfea80000 (size 0x80000)
RangeList_1: Bar1: I/O at 0xdc80 (size 0x8)
RangeList_2: Bar2: Prefetchable Memory at 0xd0000000 (size 0x10000000)
RangeList_3: Bar3: Memory at 0xfea40000 (size 0x40000)
RangeList_4: È
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Video Other
Vendor name: Intel Corporation
Product name: Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller
Subsystem: Intel Corporation : 0x27ae
VendorID: 0x8086
ProductID: 0x27a6
RevisionID: 0x0003
Class: 0x03
Subclass: 0x80
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: N/A
Status: IO: yes, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar0: Memory at 0xfe980000 (size 0x80000)
RangeList_1: È
RangeList_2: È
RangeList_3: È
RangeList_4: È
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Multimedia
Vendor name: Intel Corporation
Product name: 82801G (ICH7 Family) High Definition Audio Controller
Subsystem:
VendorID: 0x8086
ProductID: 0x27d8
RevisionID: 0x0002
Class: 0x04
Subclass: 0x03
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: 10 (A)
Status: IO: no, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar0: Memory at 0xfea38000 (size 0x4000)
RangeList_1: È
RangeList_2: È
RangeList_3: È
RangeList_4: È
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Bridge PCI-PCI Standard
Vendor name: Intel Corporation
Product name: 82801G (ICH7 Family) PCI Express Port 1
Subsystem:
VendorID: 0x8086
ProductID: 0x27d0
RevisionID: 0x0002
Class: 0x06
Subclass: 0x04
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: 10 (A)
Status: IO: yes, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bridge handles bus 1 (ISA enabled, VGA notenabled)
RangeList_1: Bridge handles bus 1 (ISA enabled, VGA notenabled)
RangeList_2: Bridge handles bus 1 (ISA enabled, VGA notenabled)
RangeList_3: Memory ranges from feb00000 to feb00000
RangeList_4: Prefetchable ranges memory from fff10000 to 00010000
RangeList_5: IO ranges from e000 to e000


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Serial USB UHCI
Vendor name: Intel Corporation
Product name: 82801G (ICH7 Family) USB UHCI Controller #1
Subsystem: Intel Corporation : 0x27c8
VendorID: 0x8086
ProductID: 0x27c8
RevisionID: 0x0002
Class: 0x0c
Subclass: 0x03
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: 11 (A)
Status: IO: yes, MEM: no, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar4: I/O at 0xdc00 (size 0x20)
RangeList_1: Bar4: I/O at 0xdc00 (size 0x20)
RangeList_2: Bar4: I/O at 0xdc00 (size 0x20)
RangeList_3: Bar4: I/O at 0xdc00 (size 0x20)
RangeList_4: Bar4: I/O at 0xdc00 (size 0x20)
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Serial USB UHCI
Vendor name: Intel Corporation
Product name: 82801G (ICH7 Family) USB UHCI Controller #2
Subsystem: Intel Corporation : 0x27c9
VendorID: 0x8086
ProductID: 0x27c9
RevisionID: 0x0002
Class: 0x0c
Subclass: 0x03
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: 5 (B)
Status: IO: yes, MEM: no, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar4: I/O at 0xd880 (size 0x20)
RangeList_1: Bar4: I/O at 0xd880 (size 0x20)
RangeList_2: Bar4: I/O at 0xd880 (size 0x20)
RangeList_3: Bar4: I/O at 0xd880 (size 0x20)
RangeList_4: Bar4: I/O at 0xd880 (size 0x20)
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Serial USB UHCI
Vendor name: Intel Corporation
Product name: 82801G (ICH7 Family) USB UHCI Controller #3
Subsystem: Intel Corporation : 0x27ca
VendorID: 0x8086
ProductID: 0x27ca
RevisionID: 0x0002
Class: 0x0c
Subclass: 0x03
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: 3 (C)
Status: IO: yes, MEM: no, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar4: I/O at 0xd800 (size 0x20)
RangeList_1: Bar4: I/O at 0xd800 (size 0x20)
RangeList_2: Bar4: I/O at 0xd800 (size 0x20)
RangeList_3: Bar4: I/O at 0xd800 (size 0x20)
RangeList_4: Bar4: I/O at 0xd800 (size 0x20)
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Serial USB UHCI
Vendor name: Intel Corporation
Product name: 82801G (ICH7 Family) USB UHCI Controller #4
Subsystem: Intel Corporation : 0x27cb
VendorID: 0x8086
ProductID: 0x27cb
RevisionID: 0x0002
Class: 0x0c
Subclass: 0x03
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: 10 (D)
Status: IO: yes, MEM: no, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar4: I/O at 0xd480 (size 0x20)
RangeList_1: Bar4: I/O at 0xd480 (size 0x20)
RangeList_2: Bar4: I/O at 0xd480 (size 0x20)
RangeList_3: Bar4: I/O at 0xd480 (size 0x20)
RangeList_4: Bar4: I/O at 0xd480 (size 0x20)
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Serial USB
Vendor name: Intel Corporation
Product name: 82801G (ICH7 Family) USB2 EHCI Controller
Subsystem: Intel Corporation : 0x27cc
VendorID: 0x8086
ProductID: 0x27cc
RevisionID: 0x0002
Class: 0x0c
Subclass: 0x03
Interface: 0x20
ROM Base: N/A
ROM Size: N/A
IRQ: 11 (A)
Status: IO: no, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar0: Memory at 0xfea37c00 (size 0x400)
RangeList_1: È
RangeList_2: È
RangeList_3: È
RangeList_4: È
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Bridge PCI-PCI Subtractive
Vendor name: Intel Corporation
Product name: 82801 Mobile PCI Bridge
Subsystem:
VendorID: 0x8086
ProductID: 0x2448
RevisionID: 0x00e2
Class: 0x06
Subclass: 0x04
Interface: 0x01
ROM Base: N/A
ROM Size: N/A
IRQ: N/A
Status: IO: no, MEM: no, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bridge handles bus 2 (ISA enabled, VGA notenabled)
RangeList_1: Bridge handles bus 2 (ISA enabled, VGA notenabled)
RangeList_2: Bridge handles bus 2 (ISA enabled, VGA notenabled)
RangeList_3: Memory ranges from fff00000 to 00000000
RangeList_4: Prefetchable ranges memory from fff10000 to 00010000
RangeList_5: IO ranges from f000 to 0000


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Bridge PCI-ISA
Vendor name: Intel Corporation
Product name: 82801GBM (ICH7-M) LPC Interface Bridge
Subsystem: Intel Corporation : 0x27b9
VendorID: 0x8086
ProductID: 0x27b9
RevisionID: 0x0002
Class: 0x06
Subclass: 0x01
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: N/A
Status: IO: yes, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: È
RangeList_1: È
RangeList_2: È
RangeList_3: È
RangeList_4: È
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Mass storage IDE
Vendor name: Intel Corporation
Product name: 82801GBM/GHM (ICH7 Family) SATA IDE Controller
Subsystem: Intel Corporation : 0x27c4
VendorID: 0x8086
ProductID: 0x27c4
RevisionID: 0x0002
Class: 0x01
Subclass: 0x01
Interface: 0x80
ROM Base: N/A
ROM Size: N/A
IRQ: 0 (B)
Status: IO: yes, MEM: no, Master: yes, PaletteSnoop: no, 66MHz capable: yes
RangeList_0: Bar4: I/O at 0xffa0 (size 0x10)
RangeList_1: Bar4: I/O at 0xffa0 (size 0x10)
RangeList_2: Bar4: I/O at 0xffa0 (size 0x10)
RangeList_3: Bar4: I/O at 0xffa0 (size 0x10)
RangeList_4: Bar4: I/O at 0xffa0 (size 0x10)
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Serial
Vendor name: Intel Corporation
Product name: 82801G (ICH7 Family) SMBus Controller
Subsystem: Intel Corporation : 0x27da
VendorID: 0x8086
ProductID: 0x27da
RevisionID: 0x0002
Class: 0x0c
Subclass: 0x05
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: 5 (B)
Status: IO: yes, MEM: no, Master: no, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar4: I/O at 0x0400 (size 0x20)
RangeList_1: Bar4: I/O at 0x0400 (size 0x20)
RangeList_2: Bar4: I/O at 0x0400 (size 0x20)
RangeList_3: Bar4: I/O at 0x0400 (size 0x20)
RangeList_4: Bar4: I/O at 0x0400 (size 0x20)
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: System Other
Vendor name: JMicron Technologies, Inc.
Product name: SD/MMC Host Controller
Subsystem: JMicron Technologies, Inc. : 0x2382
VendorID: 0x197b
ProductID: 0x2382
RevisionID: 0x0080
Class: 0x08
Subclass: 0x80
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: 7 (B)
Status: IO: yes, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar0: Memory at 0xfebffc00 (size 0x100)
RangeList_1: È
RangeList_2: È
RangeList_3: È
RangeList_4: È
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: System
Vendor name: JMicron Technologies, Inc.
Product name: Standard SD Host Controller
Subsystem: JMicron Technologies, Inc. : 0x2381
VendorID: 0x197b
ProductID: 0x2381
RevisionID: 0x0080
Class: 0x08
Subclass: 0x05
Interface: 0x01
ROM Base: N/A
ROM Size: N/A
IRQ: 7 (B)
Status: IO: yes, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar0: Memory at 0xfebff800 (size 0x100)
RangeList_1: È
RangeList_2: È
RangeList_3: È
RangeList_4: È
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: System Other
Vendor name: JMicron Technologies, Inc.
Product name: MS Host Controller
Subsystem: JMicron Technologies, Inc. : 0x2383
VendorID: 0x197b
ProductID: 0x2383
RevisionID: 0x0080
Class: 0x08
Subclass: 0x80
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: 7 (B)
Status: IO: yes, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar0: Memory at 0xfebff400 (size 0x100)
RangeList_1: È
RangeList_2: È
RangeList_3: È
RangeList_4: È
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: System Other
Vendor name: JMicron Technologies, Inc.
Product name: xD Host Controller
Subsystem: JMicron Technologies, Inc. : 0x2384
VendorID: 0x197b
ProductID: 0x2384
RevisionID: 0x0080
Class: 0x08
Subclass: 0x80
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: 7 (B)
Status: IO: yes, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar0: Memory at 0xfebff000 (size 0x100)
RangeList_1: È
RangeList_2: È
RangeList_3: È
RangeList_4: È
RangeList_5: È


Driver Name: PCINative
Direct bus: yes
Hardware info: IA32 native direct access PCI driver
Description: Network Ethernet
Vendor name: JMicron Technologies, Inc.
Product name: JMC260 PCI Express Fast Ethernet
Subsystem: JMicron Technologies, Inc. : 0x0260
VendorID: 0x197b
ProductID: 0x0260
RevisionID: 0x0002
Class: 0x02
Subclass: 0x00
Interface: 0x00
ROM Base: N/A
ROM Size: N/A
IRQ: 10 (A)
Status: IO: yes, MEM: yes, Master: yes, PaletteSnoop: no, 66MHz capable: no
RangeList_0: Bar0: Memory at 0xfebf4000 (size 0x4000)
RangeList_1: Bar2: I/O at 0xec80 (size 0x80)
RangeList_2: Bar2: I/O at 0xec80 (size 0x80)
RangeList_3: Bar3: I/O at 0xe800 (size 0x100)
RangeList_4: È
RangeList_5: È


:)

Hi i'm preparing my onlineshop. I like your idea very much. The problem about "we" is that "we" have no company...
The only thing i can offer is to take this in my program and would try to get the hardware supported as soon as possible. As told before i will refund Aros-developemnt with at least 25% of my profit + i will use the rest also for Aros related project but with the target to get things working which i can sell too. Its not about profit - its about getting Aros supported with some money. This is not my main business - i don't need the money.

If i sell this netbook too wouldn't you be angry about it? If not i will try it.

Edit: I never heard about the network brand used in this Netbot? Is it working?

@AmigaCammy
I like your idea. Is there a webpage where we can see a picture of the laptop you're describing? PCITool's output is a little verbose, so summarising the hardware specs for three main drivers, we're looking at...

Graphics: Intel Mobile 945GME
Sound: Intel 82801G (ICH7 Family) High Definition Audio
Network: JMicron JMC260 PCI Express Fast Ethernet

Does anyone know if Intel HDA chipsets have an AC97 legacy mode?

I've skimmed the programming docs for Intel HDA, and I didn't see any compatibility mode.

A related question: is Intel HDA compatible with Realtek HDA?

Quote:

Ah, shame. Well, we'll need HDA support at some point anyway, doesn't need to hold back this laptop release.

Quote:

Signs point to yes:
http://en.wikipedia.org/wiki/Intel_High_Definition_Audio
"Like AC'97, HD Audio is a specification that defines the architecture, link frame format, and programming interfaces used by the controller on the PCI bus and by the codec on the other side of the link. Implementations of the host controller are available from at least Intel, NVidia, and AMD.[5] Codecs which can be used with such controllers are available from many companies, including Realtek,[6] Conexant, and Analog Devices."

http://www.hardwaresecrets.com/article/265
"Before HD Audio was released, on-board high quality audio was only available if your motherboard had a separated high quality audio controller – like Envy24 from VIA, for example. With HD Audio technology, the south bridge of the chipset produces high-quality audio itself, without the need of a separated controller chip, what would make the motherboard more expensive. The south bridge only needs an external codec (coder/decoder) chip to make the needed digital/analog and analog/digital conversions. This kind of chip is inexpensive compared to a “full” controller chip. One example of codec compatible with Intel’s HD Audio is C-Media 9880."

http://whitepapers.techrepublic.com.com/abstract.aspx?docid=270442
"Intel High Definition Audio (HD Audio) codecs are flexible hardware devices. They can be configured by system BIOS routines to implement a variety of logical audio devices to support individual systems designs. The BIOS loads the pin configuration registers in an HD Audio codec with default settings that identify the audio devices that the codec implements on the system."

PLease be patient on the ICH7 audio driver.

Hey there Cammy.

I would like to say that I think what you are doing is great - I would love to run Aros on netbook and would purchase one the instant they are available.

Unfortunately, the odd way in which the Aros community supports hardware means that I do not think we will see drivers released within our lifepsns... How old are the bounties on Imica, EEEpc etc?

From the dicussions I have had in another forum, it seems that the majority of Aros users prefer a "quantity over quality" mindset and are happy for dozens of drivers half supporting hardware to be developed, instead of concentrating on a few fully supported pieces of hardware.

In other words, the A1600 you are working on will not be the official netbook for running Aros, but one of many netbooks that "Every man and his dog" thinks should be "half supported".

Having said that, I would love you to prove me wrong and push the A1600 as the FIRST fully supported netbook. If/when that happens, please let me know and I will purchase one immediately to show my support.

I guess you dont understand the concept that people port AROS/write drivers for the hardware THEY want AROS to run on - not because some users want to dictate what should be the "official" supported platform.

If you really want to get "your" chosen hardware supported then put your money where your mouth is and sponsor bounties - otherwise learn to do it yourself like everyone else or save your rant for some other forums.

Lol, you guess wrong then. :)

I fully understand that most open source projects have no direction and consist of a heap of people madly heading in different directions...... and your point?

No users should dictate anything. Resources should be pooled democratically to areas the MAJORITY of users want.

Wow, you so missed the point of my post I am at a loss at how to even begin pointing you in the right direction! :)

.....but here goes... I, have not "chosen" ANY hardware to be supported. This is exactly the point. I am ASKING that the "powers that be" set some hardware guidelines so that WE users can actually purchase some form of fully supported hardware.

... I have NO idea where you thought I was heading! :)

As for ranting, well, I think your post speaks for itself. :)

Quote:

What users want? Devs dont go out of their way to get hardware they dont need just because some people decide they want AROS to run on it - democraticaly chosen or otherwise. FYI most devs go out of their way to try and help support as much hardware as is possible, especially when the people asking are polite about it - though your disrespectfull comments about the work they do in this and other threads makes me wonder why.

Quote:

Im well aware of your point - you somehow think having aros only supported on dedicated/specific hardware (and thereby limit the amount of people who can just download and try it) is preferable to making it usable to as many people as possible on the hardware they already have?


Quote:

The only people who are interested in you buying a fully supported piece of AROS hardware are the people selling you it - So speak to them.

There are no "powers that be" - the people who write drivers do it because they are interested in writing drivers for hardware they have, or because someone has tempted them with a bounty/asked them politely. AROS has very few devs who have any interest in working on drivers, and those that do dedicate a lot of their own limited free time for people like yourself to hang around on forums and critisise for their efforts.

If you "had followed AROS" for as long as you suggest you might understand all this - and that (as people have tried to explain to you already in this and other threads) the only way you will get a completely supported AROS platform is if you do it yourself, or provide some kind of incentive to get devs to write/fix the things you want to see done, eg bounties.

Quote:

*Yawn*