Francis SOUYRI | 1 Oct 11:30 2010
Picon

Re: Kernel + Xorg upgrade on Thinstation 2.2.2d

Hi,

If you do not need video performance you can try the vesa driver.

Best regards.

Francis

On 09/30/2010 04:32 PM, Mike Eriksen wrote:
> On Thu, Sep 30, 2010 at 4:19 PM, Marcos Trazzini
®<mstrazzini@...>  wrote:
>> Hi mike!
>>
>>>> I would like to know if someone sucessfully upgraded the Thinstation
>>>> 2.2.2d Kernel and Xorg to quite recent versions, like at least 2.6.31
>>>> (kernel) and 7.4 (Xorg).
>>>
>>> No and that will never happen. You can try out TS 2.3svn with 2.6.31.5
>>> and Xorg 7.3 but that is work in progress.
>>>
>> By "that will never happen" you mean that there should not be possible
>> for me to make the kernel upgrade on 2.2.2d?
>
> Anything is possible but not necessarily feasible. You can't just pick
> any random kernel and expect to find the necessary patches like
> supermount and bootsplash for it. There are a few lucky possibilities.
> However I doubt very much you *need* a new kernel. Most Intel drivers
> i 2.2.2d with hd-audio as an exception (alway was broken). On the
> video front things are worse, you really need Xorg 7.3 or newer with
> those horrible Intel VGAs. But it isn't just to compile xorg by
(Continue reading)

Marcos Trazzini ® | 1 Oct 12:39 2010
Picon

Re: Kernel + Xorg upgrade on Thinstation 2.2.2d

> If you do not need video performance you can try the vesa driver.
>
The problem behind the vesa driver is that it doesn´t support
widescreen resolutions, and every new computer here comes with such
kind of monitor.

--

-- 
Marcos S. Trazzini => mstrazzini <at> gmail.com

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Thinstation-developer mailing list
Thinstation-developer <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/thinstation-developer
Marcos Trazzini ® | 1 Oct 21:06 2010
Picon

Re: Kernel + Xorg upgrade on Thinstation 2.2.2d

> On Thu, Sep 30, 2010 at 3:54 PM, Marcos Trazzini ® <mstrazzini <at> gmail.com> wrote:
>> Hi there.
>>
>> I would like to know if someone sucessfully upgraded the Thinstation
>> 2.2.2d Kernel and Xorg to quite recent versions, like at least 2.6.31
>> (kernel) and 7.4 (Xorg).
>
> No and that will never happen. You can try out TS 2.3svn with 2.6.31.5
> and Xorg 7.3 but that is work in progress.
>
Hey mike, It seems you are right. Using the latest 2.3svn release give
me bigger chances of achieving my compatibility goals.

--

-- 
Marcos S. Trazzini => mstrazzini <at> gmail.com

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Thinstation-developer mailing list
Thinstation-developer <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/thinstation-developer
Marcos Trazzini ® | 1 Oct 21:08 2010
Picon

Re: Kernel + Xorg upgrade on Thinstation 2.2.2d

Sorry, I forgot to include the list while sending the message, so
let´s send it over again.

> It supports it.
>
Yup, it supports, but not the way I need, since I often need to
manually configure it.

See, I´ve some monitors here that doesn´t follow known vesa
resolutions (like 1360x768) and for most part of them I could manually
fix by setting resolutions by hand, but its not feaseable, since I´ve
systems spread all over the country and its too expensive and unviable
to manully configure each one. My goal is to have the same behavior as
if I install a modern Linux distribution on each machine, where the
accelerated Xorg driver takes care of auto-configuring the right
resolution for each system, as actual monitors has good support for
DDC standards. That´s why I´m looking forward to get a newer kernel +
Xorg version.

Anyway, I decided to use latest 2.3svn release available, since at
least it has newer software.

Rgds

--

-- 
Marcos S. Trazzini => mstrazzini <at> gmail.com

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
(Continue reading)

Marcos Trazzini ® | 2 Oct 21:03 2010
Picon

Re: Kernel + Xorg upgrade on Thinstation 2.2.2d

> Even the most modern distro's with the latest versions of the kernel and xorg
> truggle to resolve the the best mode between the video card and monitor. Some
> combo's are more difficult than others. It's not much wonder that MS operating
> systems default to 800x600, as that is the highest resolution that every single
> monitor and card has a default mode for.
>
Hey, unless I was being very lucky within my latest years installing
Linux and Windows, I don´t think that configuring the correct
resolution for a desktop system should be such a battle! I even can´t
remember the last time I had problems configuring video resolutions on
local installations.

For example: The same machines I am talking about here cames with an
Ubuntu 8.04.1 based distro pre-installed, which is actually a quite
old distro. I just need to plug the widescreen monitor and the correct
resolution is automatically configured. Is this impossible when using
Thinstation? Why?

Rgds

--
Marcos S. Trazzini => mstrazzini <at> gmail.com

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Thinstation-developer mailing list
(Continue reading)

Jason Meers | 2 Oct 22:31 2010
Picon

Re: Kernel + Xorg upgrade on Thinstation 2.2.2d

With a recent version of 2.3svn configure the following:

No manual settings for anything, especially colour depth.
Intel cards wont even try to work if you specify 24bit as a valid
colour depth anywhere in your config.
(In the intel world you don't need any of the bits between 16 and 32)

No org6 drivers anywhere
No xorg "tiny" drivers anywhere
No "vga" drivers anywhere
Vesa is OK as a fallback driver but don't expect widescreen
resolutions (though 1600x1200 and 1280x1024 are perfectly possible)

You don't need and z-intel or z-intel-resolution drivers in 23svn
You don't need any i7xx or i8xx drivers either (these are also
provided by xorg7-intel)

In the intel world you usually don't get a splash screen either as
nobody at intel has read the VESA standard published in 1989.

Try it, but don't be fooled into thinking you have a good video card
and some bad software, you have a very bad video card and some good
software.

Ubuntu and others might be happy to add another 50-100Mbs worth of
drivers and xorg extentions to make a crap video card work, but it
makes no sense to add 100Mb work of baggage to a 15Mb operating system
for a non-vesa-compliant video card from a vendor who doesn't care
about standards.

(Continue reading)

TrevorB | 4 Oct 09:45 2010
Picon
Picon

Off the air for a few days!

Oops,

sorry all, I was unintentionally off the air for a few days (I thought
it was being very quiet... :-)

I'll try and catch up.
--

-- 
TrevorB
+=====================
Developer
http://thinstation.org
+=====================

------------------------------------------------------------------------------
Virtualization is moving to the mainstream and overtaking non-virtualized
environment for deploying applications. Does it make network security 
easier or more difficult to achieve? Read this whitepaper to separate the 
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
TrevorB | 4 Oct 09:55 2010
Picon
Picon

Re: Kernel + Xorg upgrade on Thinstation 2.2.2d

On Sat, 2010-10-02 at 16:03 -0300, Marcos Trazzini ® wrote:
> > Even the most modern distro's with the latest versions of the kernel and xorg
> > truggle to resolve the the best mode between the video card and monitor. Some
> > combo's are more difficult than others. It's not much wonder that MS operating
> > systems default to 800x600, as that is the highest resolution that every single
> > monitor and card has a default mode for.
> >
> Hey, unless I was being very lucky within my latest years installing
> Linux and Windows, I don´t think that configuring the correct
> resolution for a desktop system should be such a battle! I even can´t
> remember the last time I had problems configuring video resolutions on
> local installations.
> 
> For example: The same machines I am talking about here cames with an
> Ubuntu 8.04.1 based distro pre-installed, which is actually a quite
> old distro. I just need to plug the widescreen monitor and the correct
> resolution is automatically configured. Is this impossible when using
> Thinstation? Why?

It is called THINstation....

It ONLY loads what is necessary, so tries to remove all of the crap.

What is the smallest Ubuntu install you have?

But, I am surprised that if you included ALL of the XOrg 7.3 drivers, it
didn't autoconfigure.

What does your /var/log/Xorg.0.log say?
> 
(Continue reading)

TrevorB | 4 Oct 11:14 2010
Picon
Picon

Re: list of modules in 23svn - kernel 2.6.31.5

That's what the LiveCD does, but without the telling you what is loaded.

I have looked at the 'About' bit, but never finished.
As per a previous post by Jason, he is using the hwdetect package to do
just that.

Trevor B

On Thu, 2010-09-30 at 14:44 -0700, Don Cupp wrote:
> Mmmm. Just thinkin out loud here, but what if we take a completely
> different approach.
>  
> How about making a profiler build of thinstation. It would contain
> basic wired networking, X but no clients, and ALL kernel modules and
> ALL firmwares and ALL X drivers. It would never actually launch into
> X, but only do the configuration and then it would build a platform
> package with all the kernel drivers that actually loaded plus firmware
> files that were requested and the xorg driver that was chosen by the
> configurator and offer to push via tftp to your devstation.
>  
> We could really thin out the build.conf with something like that,
> without having to make a bunch of metapackages, or maybe just turn
> user submitted versions of these into metapackages.
>  
> What do you all think.
> 
> --- On Thu, 9/30/10, Jason Meers <jason.meers.energi@...> wrote:
> 
>         
>         From: Jason Meers <jason.meers.energi@...>
(Continue reading)

Marcos Amorim | 4 Oct 12:30 2010
Picon

Re: list of modules in 23svn - kernel 2.6.31.5

Hi All, 


You need to upgrade the java plugin to 1.6.20 or higher, to work with FF 3.6 or higher, more information is here: http://www.oracle.com/technetwork/java/javase/manual-plugin-install-linux-136395.html

Regards, 


Marcos Amorim



2010/9/30 Mike Eriksen <thinstation.mike-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Thu, Sep 30, 2010 at 9:30 PM, Jason Meers
> I'll tidy up my current live cd and send a copy to you and trevor next week.
>
> My current version is based on 222d, as I don't know which version of
> firefox works properly on 23svn.

FF-4beta works nicely in both 2.2.2d and 2.3svn. I intend to make it
default in the upcoming 2.2.2e.

> Can you give me any advice on a working combination of firefox, kiosk
> and 2.3 kernel?
> I'm stuck at the moment getting any version of firefox except 4beta to
> work on 2.3svn

FF-4beta is nice IMHO. Fat, though, but that's any FF since 2.0. No
kiosk yest for FF-4 but that will arrive, I'm sure.

Mike

> Jason_Meers
>
>
>
> On 30 September 2010 19:43, Mike Eriksen <thinstation.mike-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>> Looks nice. Should go into the LiveCD.
>>
>>
>> On Thu, Sep 30, 2010 at 6:33 PM, Jason Meers
>> <jason.meers.energi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>> On 30 September 2010 17:18, Jason Meers <jason.meers.energi-Re5JQEeQqe8@public.gmane.orgm> wrote:
>>>> I think meta packages are a possible solution, but haven't even begun
>>>> to look at how you would do it.
>>>>
>>>> meta-hp-thinclinet
>>>> meta-wyse-thinclinet
>>>> meta-dell-gx1xx
>>>> meta-dell-gx2xx
>>>> meta-intel-atom2xx
>>>> meta-via-epia
>>>> meta-nvidia-nforce4
>>>>
>>>> Jason_Meers
>>>>
>>>>
>>>>
>>>>
>>>> On 30 September 2010 16:25, Mike Eriksen <thinstation.mike <at> gmail.com> wrote:
>>>>> On Thu, Sep 30, 2010 at 3:03 PM, Jason Meers
>>>>> <jason.meers.energi-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>>>>>> Just for info:
>>>>>> list of modules in 23svn - kernel 2.6.31.5 - 30th September 2010
>>>>>>
>>>>>> Jason_Meers
>>>>> [CUT]
>>>>>
>>>>> That's nothing short of horrible and there is no way we can maintain
>>>>> the current layout of build.conf. 107 wired NICs... We have to do
>>>>> something like:
>>>>>
>>>>> #!!!Ethernet 10-100 Mbit Modules
>>>>> # Select among these:
>>>>> # 3c501 3c503 3c505 3c507 3c509 3c515 3c59x 8139cp 8139too 82596 8390 8390p
>>>>> # ac3200 acenic amd8111e at1700 b44 bnx2 bnx2x bsd_comp cassini cnic
>>>>> cs89x0 depca
>>>>> # dl2k dnet e100 e2100 eepro eexpress epic100 eth16i ethoc ewrk3
>>>>> fealnx forcedeth
>>>>> # hamachi hp-plus hp hp100 ipg jme ks8842 lance lp486e mdio natsemi ne ne2k-pci
>>>>> # ni5010 ni52 ni65 niu ns83820 pcnet32 ppp_async ppp_deflate ppp_generic
>>>>> # ppp_synctty qla3xxx r6040 r8101 r8168 r8169 s2io sc92031 seeq8005
>>>>> sis190 sis900
>>>>> # skge sky2 slhc smc-ultra smc9194 smsc9420 starfire sundance sungem sungem_phy
>>>>> # sunhme tehuti tg3 tlan tun typhoon via-rhine via-velocity vmxnet vmxnet3 wd
>>>>> # znet atl1 atl2 be2net cxgb cxgb3 e1000 e1000e enic igb igbvf ixgb ixgbe
>>>>> # mlx4_core mlx4_en myri10ge netxen_nic
>>>>> #
>>>>> #Sample configuration: (multiple drivers are allowed, but only include
>>>>> what you really need)
>>>>> #module r8168
>>>>> #module via-rhine
>>>>>
>>>>> But that's not without problems itself. I foresee a mail storm like
>>>>> "Which module for my Dell?"
>>>>>
>>>>> Mike
>>>>> --
>>>>> Operator of the Danish TS-O-Matic.
>>>>> http://thinstation.org
>>>>> - a light, full featured linux based thin client OS
>>>>>
>>>>
>>>
>>> Hi Mike
>>>
>>> Regarding the meta-package idea...This is how I currently do hardware detection.
>>>
>>> Jason_Meers
>>>
>>>
>>>
>>>
>>>
>>> Here is some of the "glue" I use in my custom HW-Detect CD, and below
>>> is the output that is saves to a bootable usb stick.
>>> It is a quick way of building a hardware database, and also shows
>>> which modules a device will sucessfully load.
>>>
>>> It needs to be built inside an image with LSHW, LSUSB and LSPCI (and
>>> FIREFOX if you want to see the results on screen)
>>> For safety it checks for the existence of a folder called \hwdetect on
>>> any usb sticks it finds (so that it doesn't acidentally trash
>>> non-standard partitions)
>>>
>>>
>>>
>>> WARNING: THIS ISNT PRETTY BUT IT WORKS : WARNING
>>>
>>>
>>> udevsend
>>>        echo "DEVICE INFO" >> /tmp/hardware.txt
>>>        echo " " >> /tmp/hardware.txt
>>>        echo "    SYSTEM" >> /tmp/hardware.txt
>>>        lshw -c system | grep -e product -e vendor -e version -e description
>>> -e serial >> /tmp/hardware.txt
>>>        echo " " >> /tmp/hardware.txt
>>>        echo "       PROCESSOR" >> /tmp/hardware.txt
>>>        lshw -c processor | grep -e product -e vendor >> /tmp/hardware.txt
>>>        echo " " >> /tmp/hardware.txt
>>>        echo "       GRAPHICS" >> /tmp/hardware.txt
>>>        lshw -c display | grep -e product -e vendor >> /tmp/hardware.txt
>>>        echo " " >> /tmp/hardware.txt
>>>        echo "       NETWORK" >> /tmp/hardware.txt
>>>        lshw -c network | grep -e product -e vendor -e serial -e capacity >>
>>> /tmp/hardware.txt
>>>        echo " " >> /tmp/hardware.txt
>>>        echo "       AUDIO" >> /tmp/hardware.txt
>>>        lshw -c multimedia | grep -e product -e vendor >> /tmp/hardware.txt
>>>        echo " " >> /tmp/hardware.txt
>>>        echo " " >> /tmp/hardware.txt
>>>        echo " " >> /tmp/hardware.txt
>>>
>>>
>>>        echo "MODULE INFO" >> /tmp/hardware.txt
>>>        lspci -k | grep modules >> /tmp/hardware.txt
>>>        echo " " >> /tmp/hardware.txt
>>>
>>>        echo "BUS INFO" >> /tmp/hardware.txt
>>>        lshw -short >> /tmp/hardware.txt
>>>        echo " " >> /tmp/hardware.txt
>>>
>>>
>>>
>>>
>>>
>>>        lshw -html >> /tmp/hardware.html
>>>        cp /tmp/hardware.txt /tmp/$CLIENT_NAME.txt
>>>        cp /tmp/hardware.html /tmp/$CLIENT_NAME.html
>>>
>>> if [ -e /mnt/usbdevice/sda1/hwdetect ] ; then
>>>        echo "found sda1/hwdetect" >> /tmp/power-saving.txt
>>>        cp /tmp/hardware.txt /mnt/usbdevice/sda1/hwdetect/$CLIENT_NAME.txt
>>>        cp /tmp/hardware.html /mnt/usbdevice/sda1/hwdetect/$CLIENT_NAME.html
>>> fi
>>>
>>> if [ -e /mnt/usbdevice/sdb1/hwdetect ] ; then
>>>        echo "found sdb1/hwdetect" >> /tmp/power-saving.txt
>>>        cp /tmp/hardware.txt /mnt/usbdevice/sdb1/hwdetect/$CLIENT_NAME.txt
>>>        cp /tmp/hardware.html /mnt/usbdevice/sdb1/hwdetect/$CLIENT_NAME.html
>>> fi
>>>
>>> if [ -e /mnt/usbdevice/sdc1/hwdetect ] ; then
>>>        echo "found sdc1/hwdetect" >> /tmp/power-saving.txt
>>>        cp /tmp/hardware.txt /mnt/usbdevice/sdc1/hwdetect/$CLIENT_NAME.txt
>>>        cp /tmp/hardware.html /mnt/usbdevice/sdc1/hwdetect/$CLIENT_NAME.html
>>> fi
>>>
>>> if [ -e /mnt/usbdevice/sda2/hwdetect ] ; then
>>>        echo "found sda2/hwdetect" >> /tmp/power-saving.txt
>>>        cp /tmp/hardware.txt /mnt/usbdevice/sda2/hwdetect/$CLIENT_NAME.txt
>>>        cp /tmp/hardware.html /mnt/usbdevice/sda2/hwdetect/$CLIENT_NAME.html
>>> fi
>>>
>>> if [ -e /mnt/usbdevice/sdb2/hwdetect ] ; then
>>>        echo "found sdb2/hwdetect" >> /tmp/power-saving.txt
>>>        cp /tmp/hardware.txt /mnt/usbdevice/sdb2/hwdetect/$CLIENT_NAME.txt
>>>        cp /tmp/hardware.html /mnt/usbdevice/sdb2/hwdetect/$CLIENT_NAME.html
>>> fi
>>>
>>> if [ -e /mnt/usbdevice/sdc2/hwdetect ] ; then
>>>        echo "found sdc2/hwdetect" >> /tmp/power-saving.txt
>>>        cp /tmp/hardware.txt /mnt/usbdevice/sdc2/hwdetect/$CLIENT_NAME.txt
>>>        cp /tmp/hardware.html /mnt/usbdevice/sdc2/hwdetect/$CLIENT_NAME.html
>>> fi
>>>
>>>        sync
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> OUTPUT FOLLOWS
>>> --------------------------------------------------------------------------------------------------------
>>>
>>> HP T5530
>>>
>>>    SYSTEM
>>>    description: Desktop Computer
>>>    product: hp t5000 series
>>>    vendor: Hewlett-Packard
>>>    serial: CNV71601CL
>>>
>>>       PROCESSOR
>>>       product: VIA Esther processor  800MHz
>>>       vendor: CentaurHauls
>>>
>>>       GRAPHICS
>>>       product: CN700/P4M800 Pro/P4M800 CE/VN800 [S3 UniChrome Pro]
>>>       vendor: VIA Technologies, Inc.
>>>
>>>       NETWORK
>>>       product: VT6102 [Rhine-II]
>>>       vendor: VIA Technologies, Inc.
>>>       serial: 00:1a:4b:bd:79:d3
>>>       capacity: 100MB/s
>>>
>>>       AUDIO
>>>       product: VT8233/A/8235/8237 AC97 Audio Controller
>>>       vendor: VIA Technologies, Inc.
>>>
>>>
>>>
>>> MODULE INFO
>>>        Kernel modules: via-agp
>>>        Kernel modules: via-agp
>>>        Kernel modules: uhci-hcd
>>>        Kernel modules: uhci-hcd
>>>        Kernel modules: uhci-hcd
>>>        Kernel modules: uhci-hcd
>>>        Kernel modules: ehci-hcd
>>>        Kernel modules: snd-via82xx
>>>        Kernel modules: via-rhine
>>>
>>> BUS INFO
>>> H/W path        Device     Class       Description
>>> ==================================================
>>>                           system      hp t5000 series
>>> /0                         bus         0A6Ch
>>> /0/0                       memory      128KiB BIOS
>>> /0/4                       processor   VIA Esther processor  800MHz
>>> /0/4/5                     memory      128KiB L1 cache
>>> /0/4/6                     memory      64KiB L2 cache
>>> /0/19                      memory      System Memory
>>> /0/19/0                    memory      128MiB Row of chips DDR
>>> /0/1d                      memory      Flash Memory
>>> /0/1d/0                    memory      512KiB Chip FLASH Non-volatile
>>> 33 MHz (30.3 ns)
>>> /0/1                       memory
>>> /0/2                       memory
>>> /0/100                     bridge      CN700/VN800/P4M800CE/Pro Host Bridge
>>> /0/100/1                   bridge      VT8237/VX700 PCI Bridge
>>> /0/100/1/0                 display     CN700/P4M800 Pro/P4M800
>>> CE/VN800 [S3 UniChrome Pro]
>>> /0/100/f                   storage
>>> VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE
>>> /0/100/f/0      ide0       bus         IDE Channel 0
>>> /0/100/f/0/0    /dev/hda   disk        64MB 64MB ATA Flash Disk
>>> /0/100/f/0/0/1  /dev/hda1  volume      61MiB Windows FAT volume
>>> /0/100/10                  bus         VT82xxxxx UHCI USB 1.1 Controller
>>> /0/100/10.1                bus         VT82xxxxx UHCI USB 1.1 Controller
>>> /0/100/10.2                bus         VT82xxxxx UHCI USB 1.1 Controller
>>> /0/100/10.3                bus         VT82xxxxx UHCI USB 1.1 Controller
>>> /0/100/10.4                bus         USB 2.0
>>> /0/100/11                  bridge      VT8237 ISA bridge
>>> [KT600/K8T800/K8T890 South]
>>> /0/100/11.5                multimedia  VT8233/A/8235/8237 AC97 Audio Controller
>>> /0/100/12       eth0       network     VT6102 [Rhine-II]
>>> /0/101                     bridge      CN700/VN800/P4M800CE/Pro Host Bridge
>>> /0/102                     bridge      CN700/VN800/P4M800CE/Pro Host Bridge
>>> /0/103                     bridge      PT890 Host Bridge
>>> /0/104                     bridge      CN700/VN800/P4M800CE/Pro Host Bridge
>>> /0/105                     bridge      CN700/VN800/P4M800CE/Pro Host Bridge
>>> /1              scsi0      storage
>>>
>>> --------------------------------------------------------------------------------------------------------
>>>
>>> DEVICE INFO
>>>
>>>    SYSTEM
>>>    description: Desktop Computer
>>>    product: VT8623-8235
>>>    vendor: VIA Technologies, Inc.
>>>
>>>       PROCESSOR
>>>       product: VIA Samuel 2
>>>       vendor: CentaurHauls
>>>
>>>       GRAPHICS
>>>       product: VT8623 [Apollo CLE266] integrated CastleRock graphics
>>>       vendor: VIA Technologies, Inc.
>>>
>>>       NETWORK
>>>       product: VT6105/VT6106S [Rhine-III]
>>>       vendor: VIA Technologies, Inc.
>>>       serial: 00:40:63:e2:0c:a4
>>>       capacity: 100MB/s
>>>       product: VT6102 [Rhine-II]
>>>       vendor: VIA Technologies, Inc.
>>>       serial: 00:40:63:e2:0c:2c
>>>       capacity: 100MB/s
>>>
>>>       AUDIO
>>>       product: VT8233/A/8235/8237 AC97 Audio Controller
>>>       vendor: VIA Technologies, Inc.
>>>
>>>
>>>
>>> MODULE INFO
>>>        Kernel modules: via-agp
>>>        Kernel modules: via-rhine
>>>        Kernel modules: uhci-hcd
>>>        Kernel modules: uhci-hcd
>>>        Kernel modules: uhci-hcd
>>>        Kernel modules: ehci-hcd
>>>        Kernel modules: snd-via82xx
>>>        Kernel modules: via-rhine
>>>
>>> BUS INFO
>>> H/W path     Device  Class       Description
>>> ============================================
>>>                     system      VT8623-8235
>>> /0                   bus         EPIA-PD
>>> /0/0                 memory      128KiB BIOS
>>> /0/4                 processor   VIA Samuel 2
>>> /0/4/7               memory      64KiB L1 cache
>>> /0/4/8               memory      64KiB L1 cache
>>> /0/14                memory      191MiB System Memory
>>> /0/14/0              memory      DIMM [empty]
>>> /0/100               bridge      VT8623 [Apollo CLE266]
>>> /0/100/1             bridge      VT8633 [Apollo Pro266 AGP]
>>> /0/100/1/0           display     VT8623 [Apollo CLE266] integrated
>>> CastleRock graphics
>>> /0/100/f     eth0    network     VT6105/VT6106S [Rhine-III]
>>> /0/100/10            bus         VT82xxxxx UHCI USB 1.1 Controller
>>> /0/100/10.1          bus         VT82xxxxx UHCI USB 1.1 Controller
>>> /0/100/10.2          bus         VT82xxxxx UHCI USB 1.1 Controller
>>> /0/100/10.3          bus         USB 2.0
>>> /0/100/11            bridge      VT8235 ISA Bridge
>>> /0/100/11.1          storage     VT82C586A/B/VT82C686/A/B/VT823x/A/C
>>> PIPC Bus Master IDE
>>> /0/100/11.5          multimedia  VT8233/A/8235/8237 AC97 Audio Controller
>>> /0/100/12    eth1    network     VT6102 [Rhine-II]
>>> /1           scsi0   storage
>>>
>>
>>
>>
>> --
>> Operator of the Danish TS-O-Matic.
>> http://thinstation.org
>> - a light, full featured linux based thin client OS
>>
>



--
Operator of the Danish TS-O-Matic.
http://thinstation.org
- a light, full featured linux based thin client OS

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Thinstation-developer mailing list
Thinstation-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/thinstation-developer

------------------------------------------------------------------------------
Virtualization is moving to the mainstream and overtaking non-virtualized
environment for deploying applications. Does it make network security 
easier or more difficult to achieve? Read this whitepaper to separate the 
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
_______________________________________________
Thinstation-developer mailing list
Thinstation-developer@...
https://lists.sourceforge.net/lists/listinfo/thinstation-developer

Gmane