Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Emachines M6807 Laptop
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3, 4 ... 11, 12, 13  Next  
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware
View previous topic :: View next topic  
Author Message
ajv
n00b
n00b


Joined: 16 Nov 2003
Posts: 23
Location: U.S.A.

PostPosted: Thu Feb 19, 2004 10:48 pm    Post subject: Reply with quote

To get the ethernet card working you have to pass "-noapic pci=nacpi" to the kernel at boot ( I think that is right... I am not at my computer right now. If it is wrong I will correct it when I get home. ). Then just modprobe via-rhine.

As for the wireless card, I tried the ndiswrapper and the linuxant driverloader and neither worked. So, I ordered a new wireless card, which should be here tomorrow. I will post back and let you know how it goes. I don't know how bad you need wireless networking, but the card I got ( mini-pci, atheros chipset ) cost $99 USD. For me it was worth it though so I can get on the vpn at my school.

ajv
Back to top
View user's profile Send private message
Spoony
Tux's lil' helper
Tux's lil' helper


Joined: 18 Feb 2004
Posts: 99
Location: Washington DC

PostPosted: Fri Feb 20, 2004 1:52 am    Post subject: Reply with quote

hmm...I really would have liked to use the power management features.

I'm still trying to get ndiswrapper...gives me an error on wrapper.o....oh well. I decided to take the leap....went to 2.6.2...runs fast. Earliest I've ever jumped kernels before ;-)

I'm still gonna bang at the wireless card, I'll let everyone know if I get anywhere.
_________________
Regards,
Mike Sponsler
msponsler at gmail.com
Back to top
View user's profile Send private message
gmh
n00b
n00b


Joined: 23 May 2003
Posts: 40

PostPosted: Sat Feb 21, 2004 3:06 am    Post subject: Wireless Reply with quote

Anyone got wireless up and running and if so what soloution did u use thanks
Back to top
View user's profile Send private message
jeffk
l33t
l33t


Joined: 13 Sep 2003
Posts: 641

PostPosted: Sat Feb 21, 2004 8:14 pm    Post subject: Reply with quote

Can I trouble the users in this thread to collectively compile a list of what is known to work on the eMachines 6805/6807 laptop, and what is expected to work with pending updates of various software packages? I've got one here getting prepared to install gentoo, and would like to make a final hassle checklist in case I need to bail and get something a bit simpler, since this will be a work machine from day one. Just chime in with the facts for each section that you have first-hand experience with, if you would. Thanks.

Platform: Is the general consensus that you need to set the platform to x86/~86 when installing? What do you give up in terms of hardware compatibility with this specific machine if you run as AMD-64 platform?


Kernel: Most early success stories seem to use 2.4, with aforementioned x86 platform. Is that the only way to go right now, or is 2.6.3 an option?


ACPI: I don't have any interest in battery life until a trip a full month from now. I do however want to avoid the mistakes I made with my Toshiba 5105, which is perhaps dying early because I had to run it flat-out with no ACPI (RH9) for at least 3,500 hours in the past 12 months. Poor thing must have cooked itself. Do power-saving ACPI measures work today with the 6807, either in 2.4 or 2.6 kernels? What about LCD brighness dimming?


Graphics: This is really a question about bundled XFree vs. ATI Binary drivers. I would opt for non-accelerated, but not dog-slow X graphics if it meant I could stay on AMD-64 and kernel 2.6, and have good ACPI screen blanking from the start. Is ATI just as paranoid as Nvidia about releasing open-source drivers. What are the choices I have here? If using 2.4 kernels and x86 platform, are the ATI kernel drivers fully accelerated and operational today? If I use AMD-64,2.6.3, can I use Xfree drivers with good results, even if they lack accleration?


Networking: I need wired ethernet to work right away, so how is the support for the via-rhine card? Can it be used with 2.4 and 2.6 kernels? When I see that passing the kernel options "-noapic pci=nacpi" is required, is that disabling ACPI? Will that get better with newer kernels, or is it going to be a permanent thing?


Wireless: I'm not in any hurry for wireless functionality, by the end of march would be nice, but not necessary even then. Spoony's putting in a whole different minipci wireless card, I don't think I'd take that drastic measure. Isn't broadcom's wireless 54g MaxPerformance a widely deployed chip? I would have thought linux support would be out for it by now. I noticed that you have to Fn-F2 to turn on the wireless radio.


Display Parameters: If you have a working XF86Config that has the right values for the display refresh rates and so on, I'd like to get a look at that. I think LCDs kind of ignore this, but it probably helps X stability to have the right refresh rates, and that information is usually not in the average owners manual.


Install Stage 1 From LiveCD: What specific Stage-1 LiveCD should I use? I will need wired ethernet to emerge the packages, other than that, I can wait for full hardware support until the install is done. This really becomes important if the answers above lead me to use the AMD-64 platform and 2.6.3 kernels, which I'm hoping to do.


Thanks in advance for the help, everyone!
Back to top
View user's profile Send private message
jeffk
l33t
l33t


Joined: 13 Sep 2003
Posts: 641

PostPosted: Sun Feb 22, 2004 12:36 am    Post subject: Reply with quote

I have some details to report. I found a very recent livecd:
Gentoo AMD-64 rc2 20040219 and booted with that.

The first attempt seemed to avoid the keyboard lockups, but it only gets to step 5a2:
Code:
gentoo-nofb nofb noapic
STEP 4: determining root devices
STEP 5: finishing up
STEP 5a: filling tmpfs filesystem
STEP 5a2: filling filesystem
(stops here)

The next attempt has a strange characteristic. Obviously the USB-only keyboard has some oddity that is giving the livecd problems. If you do nothing, it will hang. If, however, you artfully mash on the keys slowly, 4 of the 5 times I tried it, I was able to get it to keep booting through the keyboard error. At the end of that, though, it still gets hung on hotplugging, so don't get your hopes up. Still, its something for the people working on the LiveCD-AMD64 to look at, maybe they can help us out.

Code:
gentoo-nofb noapic
(boot messages)
atkbd.c: unkwon key released (translated set 0, code 0x41 on isa0060/serio).
atkbd.c: Use 'setkeycodes 41 <keycode>' to make it known.
(repeats, interspersed with services starting)
remounting root filesystem read/write
setting hostname to livecd
mounting local filesystems
mounting usb device filesystme (usbfs)
activating possibly more swap
updating initab
caching service dependencies
setting system clock to hardware clock (UTC)
configuring kernel parameters
updating environment
cleaning /var/lock, /var/run
cleaing /tmp direcotry
bringing lo up
initializing random number generator
INIT: entering runlevel: 3
starting metalog
hardware detection started
processor 0 is Mobile AMD athlon(tm) 64 Processor 3000+ 1804MHz, 1024kb Cache
Autoconfiguring devices ...  Done.
Not loading APM buis support
mouse is generic ps/2 wheel mouseat /dev/psaux
starting USB and PCI hotplugging
(stops here)
Back to top
View user's profile Send private message
scottymace
n00b
n00b


Joined: 15 Feb 2004
Posts: 29

PostPosted: Sun Feb 22, 2004 3:23 am    Post subject: Reply with quote

jeffk,
Get a usb keyboard and plug it in to he laptop. that should stop the oddball lockups, and let you get the install done. Compile UHCI usb into the kernel to stop the problem from recurring. (This is what I had to do with the 2.6.3 kernel)

As for the pcmcia/hotplug issue, try noapic pci=noacpi There is an issue with IRQ steering. if push comes to shove, acpi=off should take care of it as well. This is a case of another botched BIOS

Hope this helps....

Scotty
Back to top
View user's profile Send private message
jeffk
l33t
l33t


Joined: 13 Sep 2003
Posts: 641

PostPosted: Sun Feb 22, 2004 8:02 pm    Post subject: Reply with quote

Quote:
This is a case of another botched BIOS


I agree, there seems to be a law of proportionality at work. The cooler the laptop hardware components, the greater the chance that the integrator uses bogus bios shortcuts or equally bogus one-off windows drivers to cobble everything together, so that it runs XP out of the box and cares about little else. The components in the 6805/7 are all nice, individually.

I got a Microsoft Natural Keyboard Elite, with a USB adapter. I would have preferred something simpler, but this was the only USB keyboard under $40 available locally. At any rate booting that same AMD-64 rc2 livecd has more problems than that:

Code:
gentoo-nofb nofb noacpi noapic pci=noapic
(various boot messages, usb keyboard stops working after entering boot command)
scanning for ohci1394...module /lib/modules/2.6.2-gentoo-r1-up/kernel/drivers/ieee1394.ko loaded
Detected ohci1394 hardware
Scanning for sbp2...
(stops here)


I think that under the circumstances, I'm not quite ready to hassle with this machine under linux right now. A newer LiveCD may help the install, but at the end of the tunnel is an unworkable 64-bit ATI driver situation. I'm going try to get a few more months out of my Toshiba instead.

Looking forward to the next wave of Athlon64 machines. When they release a good one that plays well with linux, I'll be buying.
Back to top
View user's profile Send private message
Spoony
Tux's lil' helper
Tux's lil' helper


Joined: 18 Feb 2004
Posts: 99
Location: Washington DC

PostPosted: Wed Feb 25, 2004 7:13 pm    Post subject: Reply with quote

As far as things working with the laptop:

I had the 2.6.2 kernel boot....i didn't get sound...but I think thats because my kernel *refused* to load any modules.

And yes, you MUST turn acpi off :evil: when you want to use the wired ethernet card. HOWEVER, did anyone bother to try the drivers that came with the laptop? In your windows partition (if you still have it), there is a drivers directory, where it lists the drivers for all of the hardware. The network driver does have a LINUX folder that contains drivers. The read me doesn't mention anything about using acpi...in fact here is the readme:
-------------------------------------------------------------------------------
**
**
** VIA Rhine Family Fast Ethernet Adapter
**
** Linux Driver
**
** v4.24 Jan. 2003
**
**


Introduction:
=============

The instructions listed below are for linux driver installation. You must
compile the source code to generate rhinefet.o and use insmod command to
insert rhinefet.o as module.


Contents of the Subdirectory:
=============================

linux.txt This file.
rhine_main.c The linux core driver source code file
rhine_proc.c The /proc support driver source file
rhine_vmns.c The vmns driver support source file
rhine_wol.c The Wake on Lan support source file
vmns_drv.c The vmns driver support source file
rhine_wol.h The Wake on Lan support header file
rhine_vmns.h The vmns driver support header file
rhine_proc.h The /proc support driver header file
rhine_cfg.h The driver constants header file
rhine.h The linux core driver header file
kcompat.h The linux core driver header file
Makefile Makefile for generating driver object file

Kernel Supported
================
This driver support linux kernel version 2.2.x and 2.4.x now.

Installation
============
Please enter the following commands at the UNIX prompt. Remember, UNIX is
case sensitive.

1) Create a temporary directory:
mkdir /temp

2) Change to the temporary directory:
cd /temp

2) Copy driver (rhinefet.tgz) from DOS disk, (mcopy below is one tool in
mtools, if you didn't install mtools, you can type
'mount -t msdos /dev/fd0 /mnt' and use 'cp /mnt/rhinefet.tgz /temp'
command to copy the driver to the temporary directory):
mcopy a:rhinefet.tgz .

3) untar the archive file:

tar xzvf rhinefet.tgz
cd rhinefet

4) Compile the driver source files and it will generate rhinefet.o, and
copy it to correct driver installation path (The installation directory
is different in different kernel versions. In 2.4.x kernel, the path is
/lib/modules/KERNEL_VERSION/kernel/drivers/net/, and in 2.2.x kernel,
the path is /lib/modules/KERNEL_VERSION/net/, the KERNEL_VERSION (see
above) means the kernel version of your Linux distribution. If you don't
know your kernel version , please run 'uname -r' command in command
line. The kernel version will look like '2.2.16', '2.4.2-2smp' etc.) :
make install

5) Check configuration file (/etc/modules.conf or /etc/conf.modules,it
depend on your Linux distribution) for loading kernel modules. Make sure
there is the following content in the configuration file, where # is
interface number (eg: alias eth0 rhinefet):
alias eth# rhinefet

6) Reboot now:
shutdown -r now

7) Install your driver module (If the driver module is in the wrong place,
an error message will appear, and say that can't find the driver
module):
insmod rhinefet

8) Use ifconfig command to assign the IP address, where # is network
interface number:
ifconfig eth# <IP>

9) Check the interface works:
ping <remote_host_IP>


Uninstallation
==============
Please enter the following commands to uninstall your driver:
make uninstall

Note
====
1) Make sure the link file /usr/src/linux (or /usr/src/linux-2.4) is linked
to correctly kernel sources directory (eg: if you run 'uname -r', it
appears "2.4.2-2", then the link file must be linked to
/usr/src/linux-2.4.2 directory, or you will fail in compiling),
and make sure there are kernel header files in /usr/src/linux/include
directory (or /usr/src/linux-2.4/include), we need kernel header files
in compling.

2) If you can't install driver in SUSE Linux using insmod or modprobe
commands, and error messages appear (see below), please run 'uname -r'
in command line. And make sure the result of 'uname -r' (eg: 2.4.2-4GB)
is the same with the definition of UTS_RELEASE in
/usr/src/linux/include/linux/version.h. If not, please modify the
definition of UTS_RELEASE in /usr/src/linux/include/linux/version.h.

rhinefet.o: kernel-module version mismatch
rhinefet.o was compiled for kernel version 2.4.2
while this kernel is version 2.4.2-4GB.

3) Make sure that your kernel is built with network, fast_ethernet
and module support. Otherwise, you have to rebuild your kernel (see
below).
1. Go to /usr/src/linux (or /usr/src/linux-2.4) directory:
cd /usr/src/linux
2: Run 'make menuconfig' or 'make config' in text mode, or 'make
xconfig' in graphic mode.
3: Mark the options list above.
4: Exit and rebuild your kernel:
make dep;make clean;make bzImage
The file 'bzImage' will be at /usr/src/linux/arch/i386/boot/bzImage
5: Modify /etc/lilo.conf.(this file specifies where kernel image is)
6: Run 'lilo'
7: Reboot, and select the correct kernel image to boot your system.

4) You can use the utility (like netconfig, linuxconf) in your Linux
distribution to set your network parameters(like ip,gateway). These
parameters will be used at boot time. The following is the demonstration
to show how to use linuxconf (it's a utitlity in RedHat Linux 6.x) set
the network paramters.
1. Run linuxconf:
linuxconf
2. Enter setting in the Config/Networking/Client tasks/Basic host information/
and fill out the following information. Where 'xxx' is the IP address
what you have.
IP address: xxx.xxx.xxx.xxx
Netmask: 255.255.255.xxx
Net device: eth0
Kernel module: rhinefet

5) If you can't install driver at boot time.
If you can install your driver using insmod command, but you can't
install it at boot time, please check whether the driver is in the
correct directory (eg: /lib/modules/2.2.XXX/net/), and check the
/lib/modules/2.2.XXX/modules.dep file, it must include the following
line:
/lib/modules/2.2.XXX/net/rhinefet.o:

You can insert this line using depmod command or insert it manually.
Also, you must consult your Linux distribution installation guide
and learn how to set the IP address of your network interface and
up it at boot time.

6) If you can't compile this driver, and parse error messages appear,
please make sure your source code text format is right. You must convert
your source code text format from MS-DOS to UNIX, as show below (see
Solution 1 and 2).
Make sure the files in floppy disk are not rhinefet.tgz file. They must
be the source code text files (5 files), rhinefet.tgz is not a text file
, so it can't be converted.

Solution1:
If you use mcopy command to copy your driver from floppy disk to
linux, you can type:
mcopy -t a:\* .
then it will convert the format for you.

Solution2:
If you use mount command to mount floppy disk to linux, you can
type:
mount -t vfat -o conv=t /dev/fd0 /mnt/floppy
then, when you copy files from /mnt/floppy, these files format will
be right.

Module Parameter:
=================
The following parameters can be set when we install the driver module. You can add this parameters when
you execute 'insmod' or 'modprobe' command to install the driver (as below).
insmod rhinefet.o parameter=value1,value2,value3,...
For example, if you have 3 NIC cards, and you want to set the speed_duplex paramter value of them .
You can type the following command to set it.
insmod rhinefet.o speed_duplex=1,2,3
Then, the parameter value of first card will be 1 (100Mbps half duplex mode), the second card will
be 2 (100Mbps full duplex mode), and the third card will be 3 (10Mbps half duplex mode).
Remember, our driver only support 8 cards parameter setting.

1) speed_duplex
speed_duplex[] is used for setting the speed and duplex mode of NIC.
Value:
0: indicate autonegotiation for both speed and duplex mode (Default).
1: indicate 100Mbps half duplex mode
2: indicate 100Mbps full duplex mode
3: indicate 10Mbps half duplex mode
4: indicate 10Mbps full duplex mode

2) enable_tagging
enable_tagging[] is used for enabling VLAN ID setting and enabling
priority transmit.
Value:
0: disable VID setting and priority transmit (Default).
1: enable VID setting and priority transmit.

3) VID_setting
VID_setting[] is used for setting the VLAN ID of NIC.
Value:
0: default VID.
1-4094: other VIDs.

4) csum_offload
csum_offload[] is used for setting the checksum offload ability of NIC.
Value:
0: disable csum_offload (Default).
1: enable checksum offload. (We only support RX checksum offload now)

5) txcsum_offload (For management adapter only)
csum_offload[] is used for setting the checksum offload ability of NIC.
Value:
0: disable (default)
1: enable


6) flow_control
flow_control[] is used for setting the flow control ability of NIC.
Value:
1: hardware deafult (Default). Use Hardware default value in ANAR.
2: disable PAUSE in ANAR.
3: enable PAUSE in ANAR.


7) IP_byte_align
IP_byte_align[] is used for IP header DWORD byte aligned (For IPVS environment).
(In some enviroment, the IP header should be DWORD byte aligned,or the packet
will be droped when we receive it. (eg: IPVS))
Value:
0: indicate the IP header won't be DWORD byte aligned (Default).
1: indicate the IP header will be DWORD byte aligned.


8) tx_thresh
tx_thresh[] is used for controlling the transmit fifo threshold.
Value:
0: indicate the txfifo threshold is 128 bytes (Default).
1: indicate the txfifo threshold is 256 bytes.
2: indicate the txfifo threshold is 512 bytes.
3: indicate the txfifo threshold is 1024 bytes.
4: indicate that we use store and forward

9) rx_thresh
rx_thresh[] is used for controlling the receive fifo threshold.
Value:
0: indicate the rxfifo threshold is 64 bytes (Default).
1: indicate the rxfifo threshold is 32 bytes.
2: indicate the rxfifo threshold is 128 bytes.
3: indicate the rxfifo threshold is 256 bytes.
4: indicate the rxfifo threshold is 512 bytes.
5: indicate the rxfifo threshold is 768 bytes.
6: indicate the rxfifo threshold is 1024 bytes.
7: indicate that we use store and forward

10) DMA_length
DMA_length[] is used for controlling the DMA length.
Value:
0: 8 DWORDs
1: 16 DWORDs (Deafult)
2: 32 DWORDs
3: 64 DWORDs
4: 128 DWORDs
5: 256 DWORDs
6: SF(flush till emply)
7: SF(flush till emply)

11) ValPktLen
ValPktLen[] is used for controlling driver to receive or drop
the frame with invalid layer 2 length.
Value:
0: Receive frame with invalid layer 2 length.
1: Drop frame with invalid layer 2 length.

12) wol_opts
wol_opts[] is used for controlling wake on lan behavior of NIC.
0: Wake up if recevied a magic packet. (Default)
1: Wake up if link status is on/off.
2: Wake up if recevied an arp packet.
4: Wake up if recevied any unicast packet.
Those value can be sumed up to support more than one option.
------------------------------------------------------------------------
end readme.

The Modem...not sure, not sure if i really care either.

The video works, isn't slow. Was using Xfree 4.3.99...seemed to have the best speed/quality in my opion. Not sure about ATI's binary drivers.

If your using X86_64 DON'T USE REISER FS!!! My superblock died last night, and when I went to rebuild the tree it creamed my partition. Just use ext3 if going 64-bit

The wireless ethernet card is a Broadcom 94306, which is supported in NDIS wrapper ndiswrapper.sourceforge.net Going through the ndiswrapper mailing lists, I see alot of people got this wireless card to work in other laptops using the ndiswrapper 0.3 driver (current is 0.4). I've come across a few sites claiming to have gotten it to work...so I have hope. I haven't gotten it to work yet (see my unable to load modules).

I'm sure the card reader will work...just haven't tried.

Tap-on-click mouse pad just worked for me...didn't do any thing special. Well...it just worked in 2.4.25...didn't work in 2.6.2. Sooo....not sure on this one.

USB mass storage does work...was using a USB flash memory thinger.
Just remember to mount it as vfat...

When I did have ACPI I didn't play with any of the power saving modes or the PowerNow! modes for the K8 CPU.

Any one else want to share thier experiences so far?

So far thats been my experience.
_________________
Regards,
Mike Sponsler
msponsler at gmail.com
Back to top
View user's profile Send private message
scottymace
n00b
n00b


Joined: 15 Feb 2004
Posts: 29

PostPosted: Thu Feb 26, 2004 4:09 pm    Post subject: Reply with quote

Spoony:
I'm using the 1.4 athlon-xp stage3 install, and the 2.6.3 kernel. The via-rhine works perfectly. I have pci=noacpi and psmouse.proto=imps as kernel parameters.

I used the config file at http://www.muru.com/linux/amd64/ as a base for my kernel, and added some drivers for various USB items I have, or may get. I am compiling all my packages as x86 athlon-xp, but I did compile my kernel as an amd64. Everything seems to be working perfectly, but powernow-k8 will not load. I'm hoping the ACPI dev guys can come up with a workaround.
(Perhaps we should start a petition to get eMachines to fix their BIOS)

I own the linuxant driver, but haven't installed it yet. Also still running in VESA mode with xfree 4.3.0, using the XF86Config file from the same guy.
Xrander doesn't seem to be working, although it's loaded.

The onboard SD and CF readers work, CD burner works, although there is the cdrdao issue with ATAPI.

I posted a link earlier in this thread for the modem driver, so that's working.

I'm still in the process of getting various packages installed. I'll post more as I make new discoveries.

Scott
Back to top
View user's profile Send private message
thither
n00b
n00b


Joined: 04 Feb 2004
Posts: 32

PostPosted: Thu Feb 26, 2004 6:54 pm    Post subject: Reply with quote

Just as a heads-up: Brad has said on the amd64 mailing list that the next livecd will have an "emachines" kernel for this laptop - thanks Brad!

I've not yet tried it, but this might be the location of the new livecd:

http://dev.gentoo.org/~brad_mssw/2004.0/livecd/
Back to top
View user's profile Send private message
Silhouette
n00b
n00b


Joined: 23 Aug 2002
Posts: 46

PostPosted: Thu Feb 26, 2004 7:54 pm    Post subject: Reply with quote

yep, it's on the mini-cd so i expect to rest too. /isolinux/emachines & /isolinux/emachines.igz and
Code:
isolinux.cfg
...
label emachines
   kernel emachines
   append initrd.emachines.igz root = /dev/ram0 init=/linuxrc loptype=zisofs pci=noapci no apci chroot vga=0x317 splash=silent
...


great, now all i have to do is wait for my new latop to arrive. :D
Back to top
View user's profile Send private message
Insanity5902
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1228
Location: Fort Worth, Texas

PostPosted: Thu Feb 26, 2004 8:47 pm    Post subject: Reply with quote

As anyone tried this yet. I am looking at getting a laptop and the only thing preventing me from getting this one is the fact the wireless won't work!
Back to top
View user's profile Send private message
thither
n00b
n00b


Joined: 04 Feb 2004
Posts: 32

PostPosted: Fri Feb 27, 2004 10:44 pm    Post subject: Reply with quote

Insanity5902 wrote:
the only thing preventing me from getting this one is the fact the wireless won't work!


Well, I've had no luck on getting the wireless to work and I've been trying to for a while now.

The latest thing I've tried is to hack on ndiswrapper a little bit. The trick to getting it to compile and link properly is to remove div3.o and longlong.h from the makefile (their presence there is mysterious to me - they've been copied out of glibc for some reason, but they're 32-bit specific and so won't compile). I have things working to the point where I have successfully loaded the broadcom .sys driver with ndiswrapper -i.

However when I modprobe ndiswrapper it loads successfully (dmesg reports "ndiswrapper version 0.4+CVS loaded") but then doesn't seem to set up any interfaces whatsoever - instead it just sits there, silently taking up RAM. I'm wondering if the "hardware switch" needs to be enabled somehow - I've never seen the little wireless LED go on under Linux.

Anyone else got info on getting the wireless up and running?
Back to top
View user's profile Send private message
Insanity5902
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1228
Location: Fort Worth, Texas

PostPosted: Fri Feb 27, 2004 10:47 pm    Post subject: Reply with quote

Other then that how is the laptop?
Back to top
View user's profile Send private message
bswrchrd
n00b
n00b


Joined: 27 Jan 2004
Posts: 16
Location: Nashville

PostPosted: Sat Feb 28, 2004 1:34 am    Post subject: Reply with quote

Have you tried the Fn+F2 key combo? I got mine (M6805) today, and while I waiting for the live cd to d/l, I booted it into WXP Home, the wireless card wouldn't come on until I press the key combo.
Back to top
View user's profile Send private message
blaksaga
Guru
Guru


Joined: 19 May 2003
Posts: 461
Location: Omaha, NE, USA

PostPosted: Sat Feb 28, 2004 4:44 am    Post subject: Reply with quote

I would not trust an emachine if God himself floated down from heaven and set it in my arms. :lol:
Back to top
View user's profile Send private message
Insanity5902
Veteran
Veteran


Joined: 23 Jan 2004
Posts: 1228
Location: Fort Worth, Texas

PostPosted: Sat Feb 28, 2004 7:56 am    Post subject: Reply with quote

yeah but the price is so actrative and there are only so many manufactuers of laptop parts.
Back to top
View user's profile Send private message
isnogood
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jul 2003
Posts: 96

PostPosted: Sat Feb 28, 2004 4:05 pm    Post subject: Reply with quote

blaksaga wrote:
I would not trust an emachine if God himself floated down from heaven and set it in my arms. :lol:


Got any specifics to back this up?
Back to top
View user's profile Send private message
Spoony
Tux's lil' helper
Tux's lil' helper


Joined: 18 Feb 2004
Posts: 99
Location: Washington DC

PostPosted: Sat Feb 28, 2004 5:41 pm    Post subject: Reply with quote

Emachines isn't as bad as it used to be. The Emachines company that sucked so badly actually went out of business some time ago. Gateway purchased the rights to emachines. So all emachines are produced by gateway. If you notice, gateway is pulling away from producing low-end computers. See here: http://www.techweb.com/wire/story/TWB20040130S0001

So if you buy an emachines, your basically buying a gateway....they are all produced on the same assembly line...just stamped with emachines instead of gateway.


Scottymace....you are using an athlon-xp stage 3....If you compiled your kernel (2.6.3) in 64 bit....you would have *had* to compile gcc as 64 bit...you can't have a 32 bit compiler compile a kernel as 64 bit.

But my point with the Via-rhine in my last post, was that it doesn't say anything about needed to disable acpi. I was able to get my laptop to get acpi working (well...kinda). But had to disable it to get the kernel's via-rhine driver to work.

Can you install the one included with the laptop and leave acpi on?
_________________
Regards,
Mike Sponsler
msponsler at gmail.com
Back to top
View user's profile Send private message
bswrchrd
n00b
n00b


Joined: 27 Jan 2004
Posts: 16
Location: Nashville

PostPosted: Sun Feb 29, 2004 7:02 pm    Post subject: Reply with quote

EDIT: Maybe I should RTFF. Page one tells me what I wanted to know about the 1280x800 resolution.

I used the XF86Config from muru, but I can't seem to get my display to come up (no screens found). I am going to keep working on this one (somehow I think it has something to do with something really really easy). Also, the only screen sizes in muru's XF86Config are for non-widescreen resolutions, has any gotten the 1280x800 resolution to work correctly? Am I missing something so simple that Jessica Simpson would know it?
Back to top
View user's profile Send private message
sneakerski
Apprentice
Apprentice


Joined: 14 Oct 2003
Posts: 168

PostPosted: Mon Mar 01, 2004 5:52 pm    Post subject: Reply with quote

i was just reviewing the latest news for amd64, and apparently there is a emachines kernel image on the latest livecd...any body tried it?

http://www.gentoo.org/proj/en/base/amd64/index.xml?part=2&chap=3#doc_chap1

it also appears that amd64.gentoo.org is replacing brad's tech notes page.
_________________
Athlon 64 X2 @ 2ghz on an Asus nForce 4 w/ 1gig
Radeon X850 using OSS Radeon drivers
Back to top
View user's profile Send private message
isnogood
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jul 2003
Posts: 96

PostPosted: Mon Mar 01, 2004 10:40 pm    Post subject: Reply with quote

The kernel image from the link a couple of posts ago works fine.
According to a reply to my ati-sucks post there is a list of amd64 distros with ati support at http://www.ati.com/developer/altoschart.pdf
All I can find there is a bunch of links to mandrake and the likes and I ain't going to d/l mandrake without my broadband line just to find out that they use the vesa driver.Anybody tried this yet?
Back to top
View user's profile Send private message
roddog
n00b
n00b


Joined: 02 Mar 2004
Posts: 2

PostPosted: Tue Mar 02, 2004 8:24 pm    Post subject: Video out Reply with quote

I understand that some people are having success with this machine and the amd64 kernel. I am considering picking one of these babies up but I would like to know if anyone has been able to get external vga to work on it. For work, I have to give presentations and such. 2D is fine.

thanks
Back to top
View user's profile Send private message
isnogood
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jul 2003
Posts: 96

PostPosted: Tue Mar 02, 2004 8:58 pm    Post subject: Reply with quote

Well - basically I think along the lines of it getting back to the store.It will work but even with apic and acpi disabled and a 32 bit environment mine is screwing up ocassionally because of it and freezes up completely.I am in the process of trying to get things like that ironed out but don't have much hope there.
It is a nice machine but I don't see it running reliable with Linux right now.
Anyways - just get one and if you don't like it dump it within 14 days.
Back to top
View user's profile Send private message
isnogood
Tux's lil' helper
Tux's lil' helper


Joined: 09 Jul 2003
Posts: 96

PostPosted: Wed Mar 03, 2004 11:59 am    Post subject: Reply with quote

Anybody tried this yet?
http://www.shopping.hp.com/webapp/shopping/computer_store/computer_series_detail.do?tab_switch=true&tab=specs
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Kernel & Hardware All times are GMT
Goto page Previous  1, 2, 3, 4 ... 11, 12, 13  Next
Page 3 of 13

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum