View previous topic :: View next topic |
Author |
Message |
racoontje Veteran
Joined: 19 Jul 2004 Posts: 1290
|
Posted: Fri Mar 18, 2005 10:25 pm Post subject: |
|
|
It is availible with both processors. |
|
Back to top |
|
|
cooljoe2003 n00b
Joined: 02 Apr 2004 Posts: 46 Location: Jamestown, NC
|
Posted: Sun Mar 20, 2005 12:24 am Post subject: |
|
|
I wish this was easy, because everything with the wireless looks right, (On a compaq r3000 series ..particularly the R3370us - running 64-bit..naturally). The ndiswrapper module loads, and the drivers install just fine..except for one thing
Code: | bash-2.05b# ndiswrapper -i netbc564.inf
Installing netbc564
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
bash-2.05b# ndiswrapper -l
Installed ndis drivers:
netbc564 driver present, hardware present
|
it does in fact say the hardware is present, and dmesg says its ready to use
Code: |
ndiswrapper version 1.1 loaded (preempt=no,smp=no)
ndiswrapper: driver netbc564 (,10/01/2002,3.70.17.5) loaded
ACPI: PCI interrupt 0000:02:02.0[A] -> GSI 11 (level, low) -> IRQ 11
ndiswrapper: using irq 11
wlan0: ndiswrapper ethernet device 00:90:4b:92:70:1b using driver netbc564, configuration file 14E4:4320:103C:12F4.5.conf
wlan0: encryption modes supported: WEP, WPA with TKIP, WPA with AES/CCMP
|
yet, (for those of you who know what im talking about), I cannot get the light in the front to come on, no light=no network
anyone have any idears?
EDIT:
, I didnt read the title of this thread, i guess everyone does know what the light on the front does _________________ Mount Jones [dot] Net
It has been my experience that there are two kinds of liars in the world:
The ones that say they don't masturbate, and
The ones that say they quit. |
|
Back to top |
|
|
cooljoe2003 n00b
Joined: 02 Apr 2004 Posts: 46 Location: Jamestown, NC
|
Posted: Sun Mar 20, 2005 1:13 am Post subject: |
|
|
ok thats weird, I run my startup script, and ... even tho there is no light...it works..i cant believe it Well, Ill just take it at that, but maybe someone can tell me why the status light does not come on? _________________ Mount Jones [dot] Net
It has been my experience that there are two kinds of liars in the world:
The ones that say they don't masturbate, and
The ones that say they quit. |
|
Back to top |
|
|
DNAspark99 Guru
Joined: 03 Sep 2004 Posts: 321
|
Posted: Sun Mar 20, 2005 9:09 am Post subject: |
|
|
it should blink on/off when traffic is crossing the connection |
|
Back to top |
|
|
racoontje Veteran
Joined: 19 Jul 2004 Posts: 1290
|
Posted: Sun Mar 20, 2005 11:10 am Post subject: |
|
|
One some laptops the LED is controlled through software, ie it is not connected to the wireless hardware as such (as you would see on a PCMCIA ethernet card). |
|
Back to top |
|
|
BlakeJob Tux's lil' helper
Joined: 23 May 2004 Posts: 80
|
Posted: Sun Mar 20, 2005 2:28 pm Post subject: |
|
|
[quote="cooljoe2003"]I wish this was easy, because everything with the wireless looks right, (On a compaq r3000 series ..particularly the R3370us - running 64-bit..naturally). The ndiswrapper module loads, and the drivers install just fine..except for one thing
[code]bash-2.05b# ndiswrapper -i netbc564.inf
Installing netbc564
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
Forcing parameter IBSSGMode|0 to IBSSGMode|2
bash-2.05b# ndiswrapper -l
Installed ndis drivers:
netbc564 driver present, hardware present
[/code]
it does in fact say the hardware is present, and dmesg says its ready to use
[code]
ndiswrapper version 1.1 loaded (preempt=no,smp=no)
ndiswrapper: driver netbc564 (,10/01/2002,3.70.17.5) loaded
ACPI: PCI interrupt 0000:02:02.0[A] -> GSI 11 (level, low) -> IRQ 11
ndiswrapper: using irq 11
wlan0: ndiswrapper ethernet device 00:90:4b:92:70:1b using driver netbc564, configuration file 14E4:4320:103C:12F4.5.conf
wlan0: encryption modes supported: WEP, WPA with TKIP, WPA with AES/CCMP
[/code]
yet, (for those of you who know what im talking about), I cannot get the light in the front to come on, no light=no network
anyone have any idears?
EDIT:
, I didnt read the title of this thread, i guess everyone does know what the light on the front does [/quote]
the light will work when you have traffic. it won't stay on (like in windows) but it will flash when sending/receiving data.
Did you use the NDISWRAPPER WIKKI?
Once you have everythign setup (serached for a router, and picked one, and connected) then just run 'ping yahoo.com'. Let us know if you are getting anywhere. |
|
Back to top |
|
|
dan reid n00b
Joined: 01 Mar 2005 Posts: 12
|
Posted: Sun Mar 20, 2005 3:42 pm Post subject: |
|
|
I just:
modprobe ndiswrapper
ndiswrapper -i net564.inf
iwconfig wlan0 key XXXXXXXXXX "your key here, or not if you don't have WEP ennabled on your router"
dhcpcd wlan0
and there it was "surfing the net"
the blue light only comes on during traffic.....it blinks alot |
|
Back to top |
|
|
cooljoe2003 n00b
Joined: 02 Apr 2004 Posts: 46 Location: Jamestown, NC
|
Posted: Sun Mar 20, 2005 4:51 pm Post subject: |
|
|
Ok thanks guys, it does work no problem, it just is different. I hope you can tell by my post count that I never post unless I REALLY think I have a problem, usually 99% of the time I find what I need to know by searching, but this time I jumped the gun. Thanks for all you guy's help tho, it cleared up alot of things.
And dan, ur right, it does blink a whole lot lol _________________ Mount Jones [dot] Net
It has been my experience that there are two kinds of liars in the world:
The ones that say they don't masturbate, and
The ones that say they quit. |
|
Back to top |
|
|
tamarian n00b
Joined: 02 Feb 2004 Posts: 31 Location: Ottawa, Canada
|
Posted: Sat Mar 26, 2005 9:17 pm Post subject: |
|
|
How did you guys emerge the ndiswrapper ?
I emerged a couple of the versions, and each time I modprobe it, it gives:
FATAL: Error inserting ndiswrapper (/lib/modules/2.6.9-gentoo-r14/misc/ndiswrapper.ko): Operation not permitted |
|
Back to top |
|
|
cooljoe2003 n00b
Joined: 02 Apr 2004 Posts: 46 Location: Jamestown, NC
|
Posted: Sun Mar 27, 2005 2:51 am Post subject: |
|
|
Code: | # emerge ndiswrapper |
as far as it not loading, it could be a number of things...post the output of dmesg
i had the same problem too, and I accidentally found a way..at least it works for me...around it
I already had it listed in /etc/modules.autoload.d/kernel-2.6, so when I restarted the computer it loaded no problem..
like I said..it worked for me _________________ Mount Jones [dot] Net
It has been my experience that there are two kinds of liars in the world:
The ones that say they don't masturbate, and
The ones that say they quit. |
|
Back to top |
|
|
tamarian n00b
Joined: 02 Feb 2004 Posts: 31 Location: Ottawa, Canada
|
Posted: Sun Mar 27, 2005 9:31 pm Post subject: |
|
|
cooljoe2003 wrote: | Code: | # emerge ndiswrapper |
as far as it not loading, it could be a number of things...post the output of dmesg
i had the same problem too, and I accidentally found a way..at least it works for me...around it
I already had it listed in /etc/modules.autoload.d/kernel-2.6, so when I restarted the computer it loaded no problem..
like I said..it worked for me |
O.k., I think the fatal error was due to modprobing before installing the windows drivers.
Here's the dmesg:
Code: | ndiswrapper version 1.1 loaded (preempt=yes,smp=no)
ndiswrapper: driver netbc564 (,10/01/2002,3.70.17.5) loaded
ACPI: PCI interrupt 0000:02:02.0[A] -> GSI 11 (level, low) -> IRQ 11
ndiswrapper: using irq 11
wlan0: ndiswrapper ethernet device 00:90:4b:b7:31:a0 using driver netbc564, configuration file 14E4:4320.5.conf
wlan0: encryption modes supported: WEP, WPA with TKIP, WPA with AES/CCMP |
|
|
Back to top |
|
|
tamarian n00b
Joined: 02 Feb 2004 Posts: 31 Location: Ottawa, Canada
|
Posted: Mon Mar 28, 2005 10:28 pm Post subject: |
|
|
Has anyone managed getting a screen resolution higher than 1280x800 for WSXGA+ 15.4"?
Any attempt at modline with a higher resolution results in either a blank screen, or it switches back to 1024x768, with 1/4 or the screen in black, on the right side.
Here's my xorg.conf:
Code: |
Section "Module"
# Load "GLcore"
Load "synaptics"
Load "bitmap"
Load "dbe"
Load "ddc"
# Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "record"
#Load "speedo"
Load "type1"
Load "vbe"
EndSection
Section "Files"
RgbPath "/usr/lib/X11/rgb"
ModulePath "/usr/X11R6/lib/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Speedo/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
EndSection
Section "ServerFlags"
# Option "AllowNonLocalModInDev"
EndSection
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
EndSection
Section "InputDevice"
Identifier "Alps Touchpad"
Driver "synaptics"
Option "CorePointer"
Option "Device" "/dev/input/event1"
Option "Protocol" "event"
Option "LeftEdge" "60"
Option "RightEdge" "830"
Option "TopEdge" "70"
Option "BottomEdge" "650"
Option "FingerLow" "25"
Option "FingerHigh" "30"
Option "MaxTapTime" "180"
Option "MaxTapMove" "110"
Option "EmulateMidButtonTime" "75"
Option "VertScrollDelta" "50"
Option "HorizScrollDelta" "50"
Option "MinSpeed" "0.2"
Option "MaxSpeed" "0.5"
Option "AccelFactor" "0.01"
Option "EdgeMotionSpeed" "40"
Option "UpDownScrolling" "1"
Option "TouchpadOff" "0"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
Identifier "monitor1"
VendorName "Generic"
ModelName "Flat Panel 1280x800"
Option "DPMS"
#UseModes "16:10"
HorizSync 30-90
VertRefresh 50-75
Option "UseEdidFreqs" "1"
Option "FlatPanelProperties" "Scaling = aspect-scaled"
Modeline "1280x800 at 60" 83.91 1280 1312 1624 1656 800 816 824 841
-hsync -vsync
EndSection
Section "Device"
Identifier "geforce"
#Driver "vesa"
Driver "nvidia"
#Driver "nv"
Option "DPMS"
Option "IgnoreEDID" "1"
Option "NvAgp" "3"
Option "NoLogo" "0"
Option "UseEdidFreqs" "1"
Option "FlatPanelProperties" "Scaling = aspect-scaled"
#VideoRam 65536
# Insert Clocks lines here if appropriate
EndSection
Section "Screen"
Identifier "Screen 1"
Device "geforce"
Monitor "monitor1"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1280x800 at 60"
ViewPort 0 0
EndSubsection
EndSection
Section "ServerLayout"
Identifier "Simple Layout"
Screen "Screen 1"
InputDevice "Generic Keyboard"
InputDevice "Alps Touchpad"
InputDevice "USB Mouse"
EndSection
Section "DRI"
Mode 0666
EndSection
|
The above works fine, but anything higher doesn't.
I'm runnign 2.6.9-gentoo-r14, xorig 6.8.2-r1 and nvidia-kernel and nvidia-glx 1.0.6629-r4
The newer nvidia ebuidls are masked, and when installed anyway, seem to not work with xorg, complainign about the version mismatch with xorg.
The X logfiles show that other modes seem out of range:
Code: |
(II) Setting vga for screen 0.
(**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(--) NVIDIA(0): Linear framebuffer at 0xF0000000
(--) NVIDIA(0): MMIO registers at 0xE2000000
(II) NVIDIA(0): NVIDIA GPU detected as: GeForce4 440 Go 64M
(--) NVIDIA(0): VideoBIOS: 04.17.20.49.25
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(II) NVIDIA(0): Detected AGP rate: 4X
(--) NVIDIA(0): VideoRAM: 65536 kBytes
(II) NVIDIA(0): Connected display device(s): DFP-0
(--) NVIDIA(0): Display device DFP-0: maximum pixel clock at 8 bpp: 350 MHz
(--) NVIDIA(0): Display device DFP-0: maximum pixel clock at 16 bpp: 350 MHz
(--) NVIDIA(0): Display device DFP-0: maximum pixel clock at 32 bpp: 350 MHz
(II) Loading sub module "ddc"
(II) LoadModule: "ddc"
(II) Loading /usr/lib64/modules/libddc.a
(II) Module ddc: vendor="X.Org Foundation"
compiled for 6.8.2, module version = 1.0.0
ABI class: X.Org Video Driver, version 0.7
(WW) NVIDIA(0): The user specified HorizSync "31.500-90.000" has been adjusted
(WW) NVIDIA(0): to "31.500-49.000" (the intersection with EDID-specified
(WW) NVIDIA(0): HorizSync "29.000-49.000")
(II) NVIDIA(0): Monitor0: Using hsync range of 31.50-49.00 kHz
(II) NVIDIA(0): Monitor0: Using vrefresh value of 60.00 Hz
(II) NVIDIA(0): Clock range: 12.00 to 350.00 MHz
(II) NVIDIA(0): Not using mode "1680x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x350" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "320x175" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "640x400" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "320x200" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "720x400" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "360x200" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "640x480" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "320x240" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "640x480" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "320x240" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "640x480" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "320x240" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "800x600" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "400x300" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "800x600" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "400x300" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "800x600" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "400x300" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "400x300" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "512x384" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "512x384" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1152x864" (hsync out of range)
(II) NVIDIA(0): Not using default mode "576x432" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x960" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x960" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x480" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1280x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "640x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1200" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x600" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1792x1344" (hsync out of range)
(II) NVIDIA(0): Not using default mode "896x672" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range)
(II) NVIDIA(0): Not using default mode "928x696" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1856x1392" (hsync out of range)
(II) NVIDIA(0): Not using default mode "928x696" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "832x624" (hsync out of range)
(II) NVIDIA(0): Not using default mode "416x312" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1152x768" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "576x384" (vrefresh out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1400x1050" (hsync out of range)
(II) NVIDIA(0): Not using default mode "700x525" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1600x1024" (hsync out of range)
(II) NVIDIA(0): Not using default mode "800x512" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1920x1440" (hsync out of range)
(II) NVIDIA(0): Not using default mode "960x720" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (hsync out of range)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using default mode "2048x1536" (bad mode clock/interlace/doublescan)
(II) NVIDIA(0): Not using default mode "1024x768" (hsync out of range)
(II) NVIDIA(0): Not using mode "1680x1050" (no mode of this name)
(II) NVIDIA(0): Not using mode "1400x1050" (no mode of this name)
(II) NVIDIA(0): Not using mode "1280x1024" (no mode of this name)
(II) NVIDIA(0): Not using mode "1280x960" (no mode of this name)
(**) NVIDIA(0): Validated modes for display device DFP-0:
(**) NVIDIA(0): Default mode "1024x768": 65.0 MHz, 48.4 kHz, 60.0 Hz
(**) NVIDIA(0): Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz
(**) NVIDIA(0): Default mode "640x480": 25.2 MHz, 31.5 kHz, 60.0 Hz
(**) NVIDIA(0): Default mode "512x384": 32.5 MHz, 48.4 kHz, 60.0 Hz (D)
(**) NVIDIA(0): Default mode "400x300": 20.0 MHz, 37.9 kHz, 60.3 Hz (D)
(**) NVIDIA(0): Default mode "320x240": 12.6 MHz, 31.5 kHz, 60.1 Hz (D)
(II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
(--) NVIDIA(0): Display dimensions: (320, 240) mm
(--) NVIDIA(0): DPI set to (81, 81)
(II) Loading sub module "fb"
(II) LoadModule: "fb"
|
|
|
Back to top |
|
|
fcgreg Apprentice
Joined: 17 May 2003 Posts: 264 Location: California, USA
|
Posted: Tue Apr 19, 2005 7:37 am Post subject: I suggest being very cautious |
|
|
tamarian wrote: | Has anyone managed getting a screen resolution higher than 1280x800 for WSXGA+ 15.4"?
Any attempt at modline with a higher resolution results in either a blank screen, or it switches back to 1024x768, with 1/4 or the screen in black, on the right side.
|
I strongly recommend against attempting this, unless you have extra money to throw around. resolutions above 1280x800 are phsycially NOT SUPPORTED by that display. Attempts to go higher than that may damage something.
This is why it is going black / blank when you attempt to go higher than that -- and why Xorg is warning you that those modes are out of range. They are trying to protect you and them from malfunction. _________________ Greg T. |
|
Back to top |
|
|
hw-tph l33t
Joined: 08 Jan 2004 Posts: 768 Location: Uppsala, Sweden
|
Posted: Tue Apr 26, 2005 8:44 am Post subject: |
|
|
Some of the guys from the Linux-R3000 mailing list (me included) have started a wiki dedicated to Linux on the R3000 series. Most issues are dealt with there (it's a wiki so it's work in progress).
Håkan |
|
Back to top |
|
|
xante Apprentice
Joined: 23 Aug 2004 Posts: 229
|
Posted: Mon May 09, 2005 4:51 pm Post subject: |
|
|
http://www.pcxperience.com/WebGUI/index.pl/laptop/r3140us
This link has helped for lots, but I havent tried the wireless net for it so far.
Anyone know a good link for atapi burning, because for some reason, both on my pc and my R3000 I cant get it atapi or scsi burning to work with any kernel >2.6.8-gentoo-r3
Kind of a downfall, but its been pretty frustrating as is any problem. |
|
Back to top |
|
|
tamarian n00b
Joined: 02 Feb 2004 Posts: 31 Location: Ottawa, Canada
|
Posted: Mon May 09, 2005 5:02 pm Post subject: |
|
|
xante wrote: | Anyone know a good link for atapi burning, because for some reason, both on my pc and my R3000 I cant get it atapi or scsi burning to work with any kernel >2.6.8-gentoo-r3
Kind of a downfall, but its been pretty frustrating as is any problem. |
Have you tried K3B? Post any errors it gives you. It burns fine on my PC and Presario, both running 2.6.11 |
|
Back to top |
|
|
hw-tph l33t
Joined: 08 Jan 2004 Posts: 768 Location: Uppsala, Sweden
|
Posted: Mon May 09, 2005 9:20 pm Post subject: |
|
|
ATAPI burning works well for me on my nx9105 (HP branded R3000). I have an alias called "burn" set up so I can simpy type burn install.iso:
Code: | alias burn='cdrecord -v dev=ATAPI:0,0,0 speed=24 driveropts=burnfree' |
Håkan |
|
Back to top |
|
|
xante Apprentice
Joined: 23 Aug 2004 Posts: 229
|
Posted: Thu May 12, 2005 6:48 pm Post subject: |
|
|
The link I posted above, also states that nvidia drivers will not work with these laptops. It appears that some of you do have them working...Could any of you comment on how you did this?
Edit: K3B did work perfectly on a cdr, and Ill assume it will work just as beautifully on a dvdr. I had heard of k3b before, but on an older system, it would never install. Thank you (as I unmerge xcdroast.) |
|
Back to top |
|
|
fcgreg Apprentice
Joined: 17 May 2003 Posts: 264 Location: California, USA
|
Posted: Thu May 12, 2005 7:05 pm Post subject: Practically all of us do |
|
|
xante wrote: | The link I posted above, also states that nvidia drivers will not work with these laptops. It appears that some of you do have them working...Could any of you comment on how you did this? |
Most of the variants of these laptops come with nVidia cards on-board (until very recently, as I've seen some of the newer models with ATI cards). Therefore, the vast majority of folks here are undoubtedly using the nVidia drivers.
Have you read the rest of this thread? Nothing too special was required to get the nVidia drivers themselves working at all. The bigger issue is usually getting the widescreen working within your X configuration -- this is generally true regardless of which video drivers you're using.
Are you having specific problems of some kind? We'll need more information before being able to help you in any useful way. _________________ Greg T. |
|
Back to top |
|
|
xante Apprentice
Joined: 23 Aug 2004 Posts: 229
|
Posted: Thu May 12, 2005 7:14 pm Post subject: |
|
|
The nvidia drivers seem to install without a scratch, the module loads (and loads on reboot to). When it comes time to startx, I get a black screen. It never gets passed the black screen causing me to forcefull kill X.
Heres my xorg.conf
Ill post any warnings in a second, im running the vesa driver right now which allows me to run 1024x768.
Heres my Xorg.0.log.old when trying to run the nvidia driver.
Code: | Removed to save space |
Last edited by xante on Thu May 12, 2005 10:57 pm; edited 1 time in total |
|
Back to top |
|
|
fcgreg Apprentice
Joined: 17 May 2003 Posts: 264 Location: California, USA
|
Posted: Thu May 12, 2005 8:18 pm Post subject: You need to set a proper mode-line for wide-screen |
|
|
Ah, that makes more sense. Your X/Xorg configuration is having problems with the widescreen resolution you're attempting to use.
You need to add the following lines into your X config:
Code: | Section "Modes"
Identifier "1280x800"
ModeLine "1280x800" 83.5 1280 1344 1480 1680 800 801 804 828
EndSection |
This tells the X server how to deal with the wide-screen resolution properly.
If this doesn't fix the issue by itself, you may also need to add the following line to your appropriate "Monitor" section:
Code: | UseModes "1280x800" |
HTH _________________ Greg T. |
|
Back to top |
|
|
hw-tph l33t
Joined: 08 Jan 2004 Posts: 768 Location: Uppsala, Sweden
|
Posted: Thu May 12, 2005 9:58 pm Post subject: |
|
|
Perhaps the video configuration part of the R3000 Linux wiki would be of help? Most common issues using nvidia on the R3000z series are dealt with there.
Håkan |
|
Back to top |
|
|
xante Apprentice
Joined: 23 Aug 2004 Posts: 229
|
Posted: Thu May 12, 2005 10:55 pm Post subject: |
|
|
hw-tph -> Your right it did help. Just not the way i was expecting. Nvidia drivers are still a no go, they cause the screen to blank to black and not ever move after that. Vesa drivers do not support the 1280x800 mode at all, but on the other hand I tried the nv driver and it works well at 1280x800.
Code: | Section "Modes"
Identifier "1280x800"
#ModeLine "1280x800" 83.5 1280 1344 1480 1680 800 801 804 828
ModeLine "1280x800" 101.92 1280 1312 1696 1728 800 816 825 841
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
Option "DPMS" "true"
UseModes "1280x800"
HorizSync 30-90
VertRefresh 50-75
EndSection
Section "Device"
Identifier "GeForce"
Driver "nv" <- currently working driver, would like to use nvidia driver if possible
VendorName "nVidia Corporation"
BoardName "NV17 [GeForce4 440 Go 64M]"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "GeForce"
Monitor "Monitor0"
DefaultDepth 24
DefaultColorDepth 24
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1280x800" "1024x768" "800x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1280x800" "1024x768" "800x600"
EndSubSection
EndSection
|
Code: | bash-2.05b# emerge -s nvidia
Searching...
[ Results for search key : nvidia ]
[ Applications found : 3 ]
* app-emulation/emul-linux-x86-nvidia
Latest version available: 1.0.6629
Latest version installed: 1.0.6629
Size of downloaded files: 7,595 kB
Homepage: http://www.nvidia.com/
Description: NVIDIA GLX 32-bit compatibility libraries
License: NVIDIA
* media-video/nvidia-glx
Latest version available: 1.0.6629-r5
Latest version installed: 1.0.6629-r1
Size of downloaded files: 16,116 kB
Homepage: http://www.nvidia.com/
Description: NVIDIA X11 driver and GLX libraries
License: NVIDIA
* media-video/nvidia-kernel
Latest version available: 1.0.6629-r4
Latest version installed: 1.0.6629-r4
Size of downloaded files: 16,116 kB
Homepage: http://www.nvidia.com/
Description: Linux kernel module for the NVIDIA X11 driver
License: NVIDIA
bash-2.05b# |
I would upgrade to the nvidia-glx-*-r5 except the x86 emulation drivers are holding it back. I also tried without the emulation part it did the same thing. |
|
Back to top |
|
|
tamarian n00b
Joined: 02 Feb 2004 Posts: 31 Location: Ottawa, Canada
|
Posted: Thu May 12, 2005 11:05 pm Post subject: |
|
|
xante wrote: | I would upgrade to the nvidia-glx-*-r5 except the x86 emulation drivers are holding it back. I also tried without the emulation part it did the same thing. |
Have you tried removing the emulation drivers? If you have no specific need for them, unemerge, then get nvidia-glx as normal. I've posted my xorg.conf a few posts up, and it works fine with nvidia-glx. |
|
Back to top |
|
|
xante Apprentice
Joined: 23 Aug 2004 Posts: 229
|
Posted: Fri May 13, 2005 12:47 am Post subject: |
|
|
I have tried without the emulation, I guess my previous post wasnt so clear on that. But it made no difference. And with your previous post, I even tried copying and pasting yours and it did the same thing. Im clueless over this. Anyone else have any other suggestions...? Ill post any config file or log you ask for if it helps. |
|
Back to top |
|
|
|
|
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
|
|