Gateway MT3707 questions

[Thndr]

I recently got a used laptop and decide to set up a partition for tinycore//linux on it and seem to be having a couple issues//questions

1) Touchpad has tap-to-click that I find annoying. I can't seem to find out how to disable this in XVesa mode.

2) With wireless_tools and wireless2.6.29.1 I can connect to my router, but after being connected for a bit and restart the computer and boot into TinyCore, I cannot connect again.
Yet if I boot into my windows partition, and then restart back into the TC partition, the wireless connects correctly again.
The code i use is:

Code: [Select]

ifconfig wlan0 up
iwconfig wlan0 essid "MYSSID"
udhcpc -b -i wlan0
3) Not really an issue, but in order to get 1280x800 in xvesa, I just need to edit the .xsession file and replace the resolution, correct?

[Juanito]

Touchpad has tap-to-click that I find annoying. I can't seem to find out how to disable this in XVesa mode.

You don't mention what model of touchpad you have, but if it is one of those combo touch pad/pointing sticks, you may be able to edit the first line of .xsession to read mouse0 or mouse1 - on my machine, mouse0=pointing stick, mouse1=touch pad.

Alternatively, you can use full X via the Xorg extension and load the synaptics driver (for synaptics and alps touch pads at least) to control almost every aspect of a touch pads operation.

Not really an issue, but in order to get 1280x800 in xvesa, I just need to edit the .xsession file and replace the resolution, correct?

Almost correct, if you have an intel chipset, you need to load the 915resolution extension first, use a command similar to "sudo 915resolution 50 1280 800" and then edit .xsession.

[Thndr]

Touchpad has tap-to-click that I find annoying. I can't seem to find out how to disable this in XVesa mode.

You don't mention what model of touchpad you have, but if it is one of those combo touch pad/pointing sticks, you may be able to edit the first line of .xsession to read mouse0 or mouse1 - on my machine, mouse0=pointing stick, mouse1=touch pad.

Alternatively, you can use full X via the Xorg extension and load the synaptics driver (for synaptics and alps touch pads at least) to control almost every aspect of a touch pads operation.

Not really an issue, but in order to get 1280x800 in xvesa, I just need to edit the .xsession file and replace the resolution, correct?

Almost correct, if you have an intel chipset, you need to load the 915resolution extension first, use a command similar to "sudo 915resolution 50 1280 800" and then edit .xsession.

Yeah, sorry about the touchpad thing. It's a synaptics touchpad.

I have an ATI chipset for video. as well.

--
More info about the wireless: booting into Ubuntu doesn't seem to reset whatever the wireless needs to reset. I recently tried to do it because it's boot is faster than Windows, but even Ubuntu fails to connect if I boot into it after I can't connect to it in TinyCore
So it's something in the Windows wireless startup that makes it so my computer can connect to the router in linux once again.

The card I believe is a Realtek 8185. Is there any specific comands that i should run and paste the output here for better analysis? Or bootcodes or extensions I should use (other than the 2 standard wireless ones)?

[Juanito]

The card I believe is a Realtek 8185. Is there any specific comands that i should run and paste the output here for better analysis? Or bootcodes or extensions I should use (other than the 2 standard wireless ones)?

You could have a look through the output from "lspci" or "lsusb" (the latter requires the usb-utils extension) to see if you can spot your wireless card details.

[Thndr]

Code: [Select]

00:00.0 Host bridge: ATI Technologies Inc Unknown device 5a31 (rev 01)
00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:04.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:05.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge
00:13.0 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80)
00:13.1 USB Controller: ATI Technologies Inc IXP SB400 USB Host Controller (rev 80)
00:13.2 USB Controller: ATI Technologies Inc IXP SB400 USB2 Host Controller (rev 80)
00:14.0 SMBus: ATI Technologies Inc IXP SB400 SMBus Controller (rev 83)
00:14.1 IDE interface: ATI Technologies Inc IXP SB400 IDE Controller (rev 80)
00:14.2 Audio device: ATI Technologies Inc IXP SB4x0 High Definition Audio Controller (rev 01)
00:14.3 ISA bridge: ATI Technologies Inc IXP SB400 PCI-ISA Bridge (rev 80)
00:14.4 PCI bridge: ATI Technologies Inc IXP SB400 PCI-PCI Bridge (rev 80)
01:05.0 VGA compatible controller: ATI Technologies Inc RC410 [Radeon Xpress 200M]
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8038 PCI-E Fast Ethernet Controller (rev 14)
08:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8185 IEEE 802.11a/b/g Wireless LAN Controller (rev 20)*Is there another way to copy from terminal other than select and middle click?*

Anyway, it says the wireless is 8185, and I know it works at least on the first attempt to connect to the internet because I am using it right now to post from my TinyCore setup.
When I first tested it with success, I would restart about less than a minute later and be able to connect again (although I usually didn't use the internet after testing until the restart)

As some other threads have their results posted

Code: [Select]

tc@box:~$ dmesg | grep rtl
rtl8180 0000:08:09.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
wmaster0 (rtl8180): not using net_device_ops yet
wlan0 (rtl8180): not using net_device_ops yet
phy0: hwaddr 00:c0:a8:df:eb:f2, RTL8185vD + rtl8225


tc@box:~$ lsmod
Module                  Size  Used by
rtl8180                20960  0
mac80211               82100  1 rtl8180
eeprom_93cx6             688  1 rtl8180
cfg80211               21604  2 rtl8180,mac80211
squashfs               11732  0
serio_raw               2240  0
sky2                   28616  0
battery                 5976  0
ac                      1732  0
scsi_wait_scan           260  0
Not sure if those will help you other than it seems to say I'm using rtl8180 module//drivers

[Juanito]

After you reboot your machine - i.e. boot in tinycore and get wireless connection working, reboot to tinycore again - what does "udhcpc -b -i wlan0" show?

[alu]

ndiswrapper + windriver?

[Thndr]

I tried -mouse1 and also editing the resolution to 1280x800x32 but -mouse1 makes it so xvesa does not start at all and it simply ignores 1280x800 resolution and defaults to 1024x768

After you reboot your machine - i.e. boot in tinycore and get wireless connection working, reboot to tinycore again - what does "udhcpc -b -i wlan0" show?

Code: [Select]

Sending discovery...
Sending discovery...
Sending discovery...
No lease. Forking to background

[Juanito]

I don't believe that Xvesa will work at 1280x800 without some equivalent of 915resolution "fooling" the system - basically it puts 1280x800 in place of an unused video mode that is supported by Xvesa.

For the touchpad - does it have an associated pointing stick? If not, disabling it will stop Xvesa from starting. What do you see in /dev/input - mice, mouse0 and?

You may well need the Xorg extension to sort things out.

For the wireless - is it possible that your router has not released the previous ip address/mac when you reboot? I reboot and reconnect all the time without seeing this error with the "wl" driver.

[Thndr]

I'll check the mouse later, on my windows computer atm

For the wireless - is it possible that your router has not released the previous ip address/mac when you reboot? I reboot and reconnect all the time without seeing this error with the "wl" driver.

That is what I've been assuming really. For some odd reason TinyCore doesn't properly release the lease, which makes it so the router won't let the mac address have another one when it requests one. Ubuntu has no problem restarting and being able to connect to the router again and again (although going into ubuntu after Tinycore has connected and restarted makes it not able to connect) and I assume Windows sends out a script which either uses the current lease or something when booting up that makes it able to use it, and it properly releases it when shutting down.

For the router I have a WRT54G with the DD-WRT Firmware on it, but I doubt it is my router's fault. (or if it is, it's odd that TinyCore only causes the issue)

[^thehatsrule^]

I haven't read the dhcp rfc but I would've thought that if the same link device/MAC was requesting an already leased address, the dhcpd would either resend the lease or make a new offer.