From colejp at bigpond.com Thu Nov 1 03:41:42 2007 From: colejp at bigpond.com (Jason Cole) Date: Thu, 01 Nov 2007 12:41:42 +0900 Subject: No more sound Message-ID: <47294AF6.7070301@bigpond.com> Hi, In the last couple of months my sound has gone. I have updated Alsa, Kernel, Bios with no avail. My Laptop is a NEC M400 Here is a link to my data: http://pastebin.ca/756324 or ALSA Audio Debug v0.1.0 - Wed Oct 31 21:03:07 WST 2007 http://alsa.opensrc.org/aadebug http://www.gnu.org/licenses/gpl.txt Kernel ---------------------------------------------------- Linux nec 2.6.23.1-10.fc7 #1 SMP Fri Oct 19 15:39:08 EDT 2007 i686 i686 i386 GNU/Linux Loaded Modules -------------------------------------------- snd_intel8x0m 16717 0 snd_usb_audio 74305 0 snd_usb_lib 16961 1 snd_usb_audio snd_rawmidi 21185 1 snd_usb_lib snd_hwdep 10309 1 snd_usb_audio snd_seq_dummy 6725 0 snd_intel8x0 30429 0 snd_ac97_codec 91749 2 snd_intel8x0m,snd_intel8x0 snd_seq_oss 29889 0 snd_seq_midi_event 9665 1 snd_seq_oss snd_seq 44721 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 9933 4 snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 38337 0 snd_mixer_oss 16577 1 snd_pcm_oss snd_pcm 64069 5 snd_intel8x0m,snd_usb_audio,snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_timer 20421 2 snd_seq,snd_pcm snd 43205 13 snd_intel8x0m,snd_usb_audio,snd_rawmidi,snd_hwdep,snd_intel8x0,snd_ac97_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer snd_page_alloc 11209 3 snd_intel8x0m,snd_intel8x0,snd_pcm Modprobe Conf --------------------------------------------- options snd cards_limit=8 alias snd-card-0 snd-intel8x0 options snd-intel8x0 index=0 alias snd-card-7 snd-usb-audio options snd-usb-audio index=7 Proc Asound ----------------------------------------------- Advanced Linux Sound Architecture Driver Version 1.0.14 (Fri Jul 20 09:12:58 2007 UTC). --- no soundcards --- 2: : timer 3: : sequencer Client info cur clients : 3 peak clients : 3 max clients : 192 Client 0 : "System" [Kernel] Port 0 : "Timer" (Rwe-) Port 1 : "Announce" (R-e-) Connecting To: 15:0 Client 14 : "Midi Through" [Kernel] Port 0 : "Midi Through Port-0" (RWe-) Client 15 : "OSS sequencer" [Kernel] Port 0 : "Receiver" (-we-) Connected From: 0:1 Dev Snd --------------------------------------------------- seq timer CPU ------------------------------------------------------- model name : Genuine Intel(R) CPU 2.80GHz cpu MHz : 1596.000 RAM ------------------------------------------------------- MemTotal: 1002448 kB SwapTotal: 983032 kB Hardware -------------------------------------------------- 00:00.0 Host bridge: Intel Corporation 82852/82855 GM/GME/PM/GMV Processor to I/O Controller (rev 02) 00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03) Cheers Jason From fabiotust at gmail.com Mon Nov 5 17:14:12 2007 From: fabiotust at gmail.com (Fabio Tust) Date: Mon, 5 Nov 2007 15:14:12 -0200 Subject: Dell Latitude 131L and Fedora 8 Message-ID: Hello everybody, I have a Dell 131L laptop running Fedora 7 x64, but the wifi don't work. My wifi is a Broadcom and the driver is bcm43xx. I tried various tutorials on de web, using ndiswrapper or fwcutter and winxp drivers, but don't getting sucess. I'm have tested with ubuntu 7.10 and the wifi works fine, but i received a warning like "the driver have a restrict license". I don't like ubuntu, so anyone knows if the F8 is better for wifi cards of laptops? Forgive my mistakes in English, I am Brazilian and my English is not widely used Thank's Fabio Tust -------------- next part -------------- An HTML attachment was scrubbed... URL: From biggles58 at sbcglobal.net Mon Nov 5 20:14:37 2007 From: biggles58 at sbcglobal.net (Al Thompson) Date: Mon, 5 Nov 2007 12:14:37 -0800 (PST) Subject: Dell Latitude 131L and Fedora 8 Message-ID: <604070.29384.qm@web82812.mail.mud.yahoo.com> ----- Original Message ---- From: Fabio Tust To: fedora-laptop-list at redhat.com Sent: Monday, November 5, 2007 12:14:12 PM Subject: Dell Latitude 131L and Fedora 8 >I have a Dell 131L laptop running Fedora 7 x64, but the wifi don't work. My wifi is a Broadcom and >the driver is bcm43xx. I tried various tutorials on de web, using ndiswrapper or fwcutter and winxp >drivers, but don't getting sucess. I'm having the same trouble with Fedora Core 7 on a Compaq laptop with a Broadcom internal wifi. I can actually get as far as being able to configure it using iwconfig, and it will even scan for APs, and give me the results. However, I cannot ping out of it, and the GUI steadfastly refuses to see it. On a whim, I tried a USB wifi device, with the exact same results, so maybe it's not specific to the Broadcom device. If you find an answer, post it here! -------------- next part -------------- An HTML attachment was scrubbed... URL: From cabedogni at gmail.com Mon Nov 5 20:53:43 2007 From: cabedogni at gmail.com (Carlo Alberto Bedogni) Date: Mon, 5 Nov 2007 21:53:43 +0100 Subject: Dell Latitude 131L and Fedora 8 In-Reply-To: <604070.29384.qm@web82812.mail.mud.yahoo.com> References: <604070.29384.qm@web82812.mail.mud.yahoo.com> Message-ID: hi i have F7 and a bcm4306 working very fine , i use fwcutter take a look at this ( but is italian ) http://www.centos-italia.org/index.php/topic,7.0.html On 11/5/07, Al Thompson wrote: > > > > > > > ----- Original Message ---- > From: Fabio Tust > To: fedora-laptop-list at redhat.com > Sent: Monday, November 5, 2007 12:14:12 PM > Subject: Dell Latitude 131L and Fedora 8 > > >I have a Dell 131L laptop running Fedora 7 x64, but the wifi don't work. My > wifi is a Broadcom and >the driver is bcm43xx. I tried various tutorials on > de web, using ndiswrapper or fwcutter and winxp >drivers, but don't getting > sucess. > > > I'm having the same trouble with Fedora Core 7 on a Compaq laptop with a > Broadcom internal wifi. I can actually get as far as being able to > configure it using iwconfig, and it will even scan for APs, and give me the > results. However, I cannot ping out of it, and the GUI steadfastly refuses > to see it. > > On a whim, I tried a USB wifi device, with the exact same results, so maybe > it's not specific to the Broadcom device. > > If you find an answer, post it here! > > > _______________________________________________ > Fedora-laptop-list mailing list > Fedora-laptop-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-laptop-list > > From peterlauri at gmail.com Thu Nov 8 22:07:51 2007 From: peterlauri at gmail.com (Peter Lauri) Date: Fri, 9 Nov 2007 00:07:51 +0200 Subject: T61 monitor Message-ID: <8ab6097c0711081407p3bf09311x93be563717b79230@mail.gmail.com> Hi, I have the Lenovo/IBM T61 with WXGA 14.1 inch screen and Intel Graphics Media Accelerator 945. The max resolution is 1280x800. On my current FC7 installation I cannot get the resolution up to this value. Maximum is 1024x768 :( Any hints of how I can fix this? /Peter From jos at xos.nl Thu Nov 8 22:15:19 2007 From: jos at xos.nl (Jos Vos) Date: Thu, 8 Nov 2007 23:15:19 +0100 Subject: T61 monitor In-Reply-To: <8ab6097c0711081407p3bf09311x93be563717b79230@mail.gmail.com> References: <8ab6097c0711081407p3bf09311x93be563717b79230@mail.gmail.com> Message-ID: <20071108221519.GA24187@jasmine.xos.nl> On Fri, Nov 09, 2007 at 12:07:51AM +0200, Peter Lauri wrote: > I have the Lenovo/IBM T61 with WXGA 14.1 inch screen and Intel > Graphics Media Accelerator 945. The max resolution is 1280x800. On my > current FC7 installation I cannot get the resolution up to this value. > Maximum is 1024x768 :( Any hints of how I can fix this? Change your Monitor and Device sections as follows (the 2 Monitor sections are needed!): Section "Monitor" Identifier "Monitor0" ModelName "LCD Panel 1280x800" HorizSync 31.5 - 90.0 VertRefresh 59.9 - 60.1 Option "dpms" EndSection Section "Monitor" Identifier "Monitor1" Option "Ignore" "true" EndSection Section "Device" Identifier "Videocard0" Driver "intel" Option "monitor-VGA" "Monitor0" Option "monitor-TV" "Monitor1" Option "DRI" "false" EndSection The "DRI" setting is needed as otherwise some apps (like Google Earth) make X go crazy, but if you only do simple things, you may eanable it. -- -- Jos Vos -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 From peterlauri at gmail.com Fri Nov 9 04:55:15 2007 From: peterlauri at gmail.com (Peter Lauri) Date: Fri, 9 Nov 2007 06:55:15 +0200 Subject: T61 monitor In-Reply-To: <20071108221519.GA24187@jasmine.xos.nl> References: <8ab6097c0711081407p3bf09311x93be563717b79230@mail.gmail.com> <20071108221519.GA24187@jasmine.xos.nl> Message-ID: <8ab6097c0711082055y6e556989pdcf6b99e7cee32bd@mail.gmail.com> Hi, I did change the things you said. However, as before (as I forgot to mention) is that the system-config-display cannot be opened. This is my xorg.conf content for the moment. And after that is the log for Xorg. I am a very novice in this area, sorry for that :( But I'd really like to use Fedora on my laptop. Section "ServerLayout" Identifier "single head configuration" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Synaptics" "CorePointer" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Synaptics" Driver "synaptics" Option "Device" "/dev/input/mice" Option "Protocol" "auto-dev" Option "Emulate3Buttons" "yes" EndSection Section "Monitor" Identifier "Monitor0" ModelName "LCD Panel 1280x800" HorizSync 31.5 - 90.0 VertRefresh 59.9 - 60.1 Option "dpms" EndSection Section "Monitor" Identifier "Monitor1" Option "Ignore" "true" EndSection Section "Device" Identifier "Videocard0" Driver "intel" Option "monitor-VGA" "Monitor0" Option "monitor-TV" "Monitor1" Option "DRI" "false" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection This is the /var/log/Xorg.0.log: (II) intel(0): Output VGA disconnected (II) intel(0): EDID for output VGA (II) intel(0): Output LVDS connected (II) intel(0): I2C device "LVDSDDC_C:ddc2" registered at address 0xA0. (II) intel(0): I2C device "LVDSDDC_C:ddc2" removed. (II) intel(0): EDID for output LVDS (II) intel(0): Manufacturer: LEN Model: 4031 Serial#: 0 (II) intel(0): Year: 2007 Week: 0 (II) intel(0): EDID Version: 1.3 (II) intel(0): Digital Display Input (II) intel(0): Max H-Image Size [cm]: horiz.: 30 vert.: 19 (II) intel(0): Gamma: 2.20 (II) intel(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display (II) intel(0): First detailed timing is preferred mode (II) intel(0): redX: 0.569 redY: 0.332 greenX: 0.312 greenY: 0.544 (II) intel(0): blueX: 0.149 blueY: 0.132 whiteX: 0.313 whiteY: 0.329 (II) intel(0): Supported VESA Video Modes: (II) intel(0): 640x480 at 60Hz (II) intel(0): 800x600 at 60Hz (II) intel(0): 1024x768 at 60Hz (II) intel(0): Manufacturer's mask: 0 (II) intel(0): Supported additional Video Mode: (II) intel(0): clock: 76.8 MHz Image Size: 303 x 190 mm (II) intel(0): h_active: 1280 h_sync: 1332 h_sync_end 1396 h_blank_end 1568 h_border: 0 (II) intel(0): v_active: 800 v_sync: 803 v_sync_end 806 v_blanking: 816 v_border: 0 (II) intel(0): Supported additional Video Mode: (II) intel(0): clock: 64.0 MHz Image Size: 303 x 190 mm (II) intel(0): h_active: 1280 h_sync: 1332 h_sync_end 1396 h_blank_end 1568 h_border: 0 (II) intel(0): v_active: 800 v_sync: 803 v_sync_end 806 v_blanking: 816 v_border: 0 (II) intel(0): LTN141W1-L05 (II) intel(0): EDID (in hex): (II) intel(0): 00ffffffffffff0030ae314000000000 (II) intel(0): 00110103801e1378eacd7591554f8b26 (II) intel(0): 21505421080001010101010101010101 (II) intel(0): 010101010101fd1d0020512010303440 (II) intel(0): 33002fbe10000019fe18002051201030 (II) intel(0): 344033002fbe100000190000000f0081 (II) intel(0): 0a32810a281201004ca35731000000fe (II) intel(0): 004c544e31343157312d4c30350a0022 (II) intel(0): Printing DDC gathered Modelines: (II) intel(0): Modeline "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (II) intel(0): Modeline "640x480" 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (II) intel(0): Modeline "1024x768" 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (II) intel(0): Modeline "1280x800" 76.77 1280 1332 1396 1568 800 803 806 816 -hsync -vsync (II) intel(0): Modeline "1280x800" 63.98 1280 1332 1396 1568 800 803 806 816 -hsync -vsync (II) intel(0): EDID vendor "LEN", prod id 16433 (II) intel(0): Not using default mode "640x350" (vrefresh out of range) (II) intel(0): Not using default mode "640x400" (vrefresh out of range) (II) intel(0): Not using default mode "720x400" (vrefresh out of range) (II) intel(0): Not using default mode "640x480" (vrefresh out of range) (II) intel(0): Not using default mode "640x480" (vrefresh out of range) (II) intel(0): Not using default mode "640x480" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "800x600" (vrefresh out of range) (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) (II) intel(0): Not using default mode "1024x768" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (vrefresh out of range) (II) intel(0): Not using default mode "1280x960" (hsync out of range) (II) intel(0): Not using default mode "1280x960" (vrefresh out of range) (II) intel(0): Not using default mode "1280x1024" (hsync out of range) (II) intel(0): Not using default mode "1280x1024" (vrefresh out of range) (II) intel(0): Not using default mode "1280x1024" (vrefresh out of range) (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size) (II) intel(0): Not using default mode "1600x1200" (width too large for virtual size) (II) intel(0): Not using default mode "1792x1344" (height too large for virtual size) (II) intel(0): Not using default mode "1792x1344" (height too large for virtual size) (II) intel(0): Not using default mode "1856x1392" (height too large for virtual size) (II) intel(0): Not using default mode "1856x1392" (height too large for virtual size) (II) intel(0): Not using default mode "1920x1440" (height too large for virtual size) (II) intel(0): Not using default mode "1920x1440" (height too large for virtual size) (II) intel(0): Not using default mode "832x624" (vrefresh out of range) (II) intel(0): Not using default mode "1152x768" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (exceeds panel dimensions) (II) intel(0): Not using default mode "1152x864" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (vrefresh out of range) (II) intel(0): Not using default mode "1152x864" (vrefresh out of range) (II) intel(0): Not using default mode "1280x720" (vrefresh out of range) (II) intel(0): Not using default mode "1280x720" (vrefresh out of range) (II) intel(0): Not using default mode "1280x720" (vrefresh out of range) (II) intel(0): Not using default mode "1280x800" (vrefresh out of range) (II) intel(0): Not using default mode "1280x800" (vrefresh out of range) (II) intel(0): Not using default mode "1280x800" (vrefresh out of range) (II) intel(0): Not using default mode "1280x768" (vrefresh out of range) (II) intel(0): Not using default mode "1280x768" (vrefresh out of range) (II) intel(0): Not using default mode "1280x768" (vrefresh out of range) (II) intel(0): Not using default mode "1360x768" (width too large for virtual size) (II) intel(0): Not using default mode "1360x768" (width too large for virtual size) (II) intel(0): Not using default mode "1400x1050" (width too large for virtual size) (II) intel(0): Not using default mode "1400x1050" (width too large for virtual size) (II) intel(0): Not using default mode "1400x1050" (width too large for virtual size) (II) intel(0): Not using default mode "1400x1050" (width too large for virtual size) (II) intel(0): Not using default mode "1400x1050" (width too large for virtual size) (II) intel(0): Not using default mode "1400x1050" (width too large for virtual size) (II) intel(0): Not using default mode "1440x900" (width too large for virtual size) (II) intel(0): Not using default mode "1600x1024" (width too large for virtual size) (II) intel(0): Not using default mode "1680x1050" (width too large for virtual size) (II) intel(0): Not using default mode "1680x1050" (width too large for virtual size) (II) intel(0): Not using default mode "1680x1050" (width too large for virtual size) (II) intel(0): Not using default mode "1680x1050" (width too large for virtual size) (II) intel(0): Not using default mode "1680x1050" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1080" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1080" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1080" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1080" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1080" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1200" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1200" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1200" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1200" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1200" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1200" (width too large for virtual size) (II) intel(0): Not using default mode "1920x1440" (height too large for virtual size) (II) intel(0): Not using default mode "2048x1536" (height too large for virtual size) (II) intel(0): Not using default mode "2048x1536" (height too large for virtual size) (II) intel(0): Not using default mode "2048x1536" (height too large for virtual size) (II) intel(0): Not using default mode "2560x1600" (height too large for virtual size) (II) intel(0): Printing probed modes for output LVDS (II) intel(0): Modeline "1280x800"x60.0 76.77 1280 1332 1396 1568 800 803 806 816 -hsync -vsync (49.0 kHz) (II) intel(0): Modeline "1280x800"x60.0 83.46 1280 1344 1480 1680 800 801 804 828 -hsync +vsync (49.7 kHz) (II) intel(0): Modeline "1280x800"x50.0 63.98 1280 1332 1396 1568 800 803 806 816 -hsync -vsync (40.8 kHz) (II) intel(0): Modeline "1280x768"x60.0 80.14 1280 1344 1480 1680 768 769 772 795 -hsync +vsync (47.7 kHz) (II) intel(0): Modeline "1280x720"x60.0 74.48 1280 1336 1472 1664 720 721 724 746 -hsync +vsync (44.8 kHz) (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz) (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz) (II) intel(0): Output TMDS-1 disconnected (II) intel(0): EDID for output TMDS-1 On Nov 9, 2007 12:15 AM, Jos Vos wrote: > > On Fri, Nov 09, 2007 at 12:07:51AM +0200, Peter Lauri wrote: > > > I have the Lenovo/IBM T61 with WXGA 14.1 inch screen and Intel > > Graphics Media Accelerator 945. The max resolution is 1280x800. On my > > current FC7 installation I cannot get the resolution up to this value. > > Maximum is 1024x768 :( Any hints of how I can fix this? > > Change your Monitor and Device sections as follows (the 2 Monitor > sections are needed!): > > Section "Monitor" > Identifier "Monitor0" > ModelName "LCD Panel 1280x800" > HorizSync 31.5 - 90.0 > VertRefresh 59.9 - 60.1 > Option "dpms" > EndSection > > Section "Monitor" > Identifier "Monitor1" > Option "Ignore" "true" > EndSection > > Section "Device" > Identifier "Videocard0" > Driver "intel" > Option "monitor-VGA" "Monitor0" > Option "monitor-TV" "Monitor1" > Option "DRI" "false" > EndSection > > The "DRI" setting is needed as otherwise some apps (like Google Earth) > make X go crazy, but if you only do simple things, you may eanable it. > > -- > -- Jos Vos > -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 > -- Amsterdam, The Netherlands | Fax: +31 20 6948204 > From jos at xos.nl Fri Nov 9 13:42:35 2007 From: jos at xos.nl (Jos Vos) Date: Fri, 9 Nov 2007 14:42:35 +0100 Subject: T61 monitor In-Reply-To: <8ab6097c0711082055y6e556989pdcf6b99e7cee32bd@mail.gmail.com> References: <8ab6097c0711081407p3bf09311x93be563717b79230@mail.gmail.com> <20071108221519.GA24187@jasmine.xos.nl> <8ab6097c0711082055y6e556989pdcf6b99e7cee32bd@mail.gmail.com> Message-ID: <20071109134235.GD30977@jasmine.xos.nl> On Fri, Nov 09, 2007 at 06:55:15AM +0200, Peter Lauri wrote: > Hi, I did change the things you said. However, as before (as I forgot > to mention) is that the system-config-display cannot be opened. This > is my xorg.conf content for the moment. And after that is the log for > Xorg. I am a very novice in this area, sorry for that :( But I'd > really like to use Fedora on my laptop. Your config is really exactly the same (except for a few spaces) as what we use here. To be 100% sure about typos etc., I'll send you a copy of our xorg.conf in private mail (please try that, just in case...), as well as our (long) Xorg.0.log file. Did you also restart the laptop after making the changes? I'm not sure if this is needed (normally it's not), because of that special issue of the TV-output. You shouldn't need to run system-config-display (that only works if X is already running), with this xorg.conf it "just should work". Let me know if you get it working, or otherwise send the output of "lspci -v", as Lenovo might have changed some hardware. B.t.w., sound on the T61 is still not working, we hope for F8 (not tried yet), as this is said to be solved in newer versions of ALSA. -- -- Jos Vos -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 From peterlauri at gmail.com Fri Nov 9 19:15:45 2007 From: peterlauri at gmail.com (Peter Lauri) Date: Fri, 9 Nov 2007 21:15:45 +0200 Subject: T61 architecture Message-ID: <8ab6097c0711091115n11efdd0dr688a565ce5b43614@mail.gmail.com> Hi, I am a bit confused. Some sites on internet I found refer to a x86_64 installation and others to a i386 installation. Can both be done? What is recommended in that case? I have just noticed that the x86_64 arch is less supported by other software? /Peter From jos at xos.nl Fri Nov 9 19:41:59 2007 From: jos at xos.nl (Jos Vos) Date: Fri, 9 Nov 2007 20:41:59 +0100 Subject: T61 architecture In-Reply-To: <8ab6097c0711091115n11efdd0dr688a565ce5b43614@mail.gmail.com> References: <8ab6097c0711091115n11efdd0dr688a565ce5b43614@mail.gmail.com> Message-ID: <20071109194159.GA2426@jasmine.xos.nl> On Fri, Nov 09, 2007 at 09:15:45PM +0200, Peter Lauri wrote: > I am a bit confused. Some sites on internet I found refer to a x86_64 > installation and others to a i386 installation. Can both be done? What > is recommended in that case? I have just noticed that the x86_64 arch > is less supported by other software? You can do both. The x86_64 install will also install several packages (mainly libraries) in both 32- and 64-bit, so that you can run third-party 32-bit apps without problems. There is one important thing to consider: some third-party (proprietary) plugins for Firefox (like flashplayer and Acrobat reader) are only available in 32-bit mode and for these you need to run 32-bit Firefox. So, when running Firefox you also pull in several 32-bit libraries and thus have usually 2 active copies of these libraries in memory. -- -- Jos Vos -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 From biggles58 at sbcglobal.net Fri Nov 9 20:23:25 2007 From: biggles58 at sbcglobal.net (Al Thompson) Date: Fri, 9 Nov 2007 12:23:25 -0800 (PST) Subject: FC 8 Message-ID: <977967.96648.qm@web82805.mail.mud.yahoo.com> I see that Core 8 is out, or will be very shortly. I have Core7 installed, and up-to-date. My question is this: If I continue to update my FC7 installation, is there any advantage to installing FC8? What would the differences be, if any? -------------- next part -------------- An HTML attachment was scrubbed... URL: From sundaram at fedoraproject.org Fri Nov 9 20:54:41 2007 From: sundaram at fedoraproject.org (Rahul Sundaram) Date: Sat, 10 Nov 2007 02:24:41 +0530 Subject: FC 8 In-Reply-To: <977967.96648.qm@web82805.mail.mud.yahoo.com> References: <977967.96648.qm@web82805.mail.mud.yahoo.com> Message-ID: <4734C911.9050902@fedoraproject.org> Al Thompson wrote: > > I see that Core 8 is out, or will be very shortly. I have Core7 > installed, and up-to-date. My question is this: If I continue to > update my FC7 installation, is there any advantage to installing FC8? > What would the differences be, if any? There are a number of features too intrusive to introduce as updates and that list is quite long for Fedora 8 (no more "core" in the name since Core and Extras repository was merged in the previous release). http://fedoraproject.org/wiki/Releases/8/ReleaseSummary Rahul From peterlauri at gmail.com Fri Nov 9 21:15:24 2007 From: peterlauri at gmail.com (Peter Lauri) Date: Fri, 9 Nov 2007 23:15:24 +0200 Subject: T61 architecture In-Reply-To: <20071109194159.GA2426@jasmine.xos.nl> References: <8ab6097c0711091115n11efdd0dr688a565ce5b43614@mail.gmail.com> <20071109194159.GA2426@jasmine.xos.nl> Message-ID: <8ab6097c0711091315j59472309s547f20aec06ca019@mail.gmail.com> But what would the benefit of installing x86_64 be? Pros vs cons? /Peter On Nov 9, 2007 9:41 PM, Jos Vos wrote: > > On Fri, Nov 09, 2007 at 09:15:45PM +0200, Peter Lauri wrote: > > > I am a bit confused. Some sites on internet I found refer to a x86_64 > > installation and others to a i386 installation. Can both be done? What > > is recommended in that case? I have just noticed that the x86_64 arch > > is less supported by other software? > > You can do both. > > The x86_64 install will also install several packages (mainly libraries) > in both 32- and 64-bit, so that you can run third-party 32-bit apps > without problems. > > There is one important thing to consider: some third-party (proprietary) > plugins for Firefox (like flashplayer and Acrobat reader) are only > available in 32-bit mode and for these you need to run 32-bit Firefox. > So, when running Firefox you also pull in several 32-bit libraries and > thus have usually 2 active copies of these libraries in memory. > > -- > -- Jos Vos > -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 > -- Amsterdam, The Netherlands | Fax: +31 20 6948204 > From zaitcev at redhat.com Fri Nov 9 21:58:07 2007 From: zaitcev at redhat.com (Pete Zaitcev) Date: Fri, 9 Nov 2007 13:58:07 -0800 Subject: T61 architecture In-Reply-To: <8ab6097c0711091315j59472309s547f20aec06ca019@mail.gmail.com> References: <8ab6097c0711091115n11efdd0dr688a565ce5b43614@mail.gmail.com> <20071109194159.GA2426@jasmine.xos.nl> <8ab6097c0711091315j59472309s547f20aec06ca019@mail.gmail.com> Message-ID: <20071109135807.f7010d79.zaitcev@redhat.com> On Fri, 9 Nov 2007 23:15:24 +0200, "Peter Lauri" wrote: > But what would the benefit of installing x86_64 be? Pros vs cons? x86_64 is marginally faster despite the bigger cache footprint because it adds registers, so if you do something like biochemistry or mathlab on your lappy, it helps. It's more about the number of registers than their size. Also, at some loads with some peripherals, eliminating highmem gives a boost. Not only there's no copying, but also the single-zone VM in Linux performs much better than dual-zone for many loads. You can see it when using an external USB disk. So that's the rule of thumb. On a plain office box with less than 960MB there's probably no sense in it. -- Pete From tiagomatos at gmail.com Fri Nov 9 22:47:07 2007 From: tiagomatos at gmail.com (Rui Tiago Matos) Date: Fri, 9 Nov 2007 22:47:07 +0000 Subject: T61 architecture In-Reply-To: <20071109194159.GA2426@jasmine.xos.nl> References: <8ab6097c0711091115n11efdd0dr688a565ce5b43614@mail.gmail.com> <20071109194159.GA2426@jasmine.xos.nl> Message-ID: On 11/9/07, Jos Vos wrote: > There is one important thing to consider: some third-party (proprietary) > plugins for Firefox (like flashplayer and Acrobat reader) are only > available in 32-bit mode and for these you need to run 32-bit Firefox. > So, when running Firefox you also pull in several 32-bit libraries and > thus have usually 2 active copies of these libraries in memory. nspluginwrapper allows you to run these plugins (at least flash) with a 64 bit browser. Plus, it has the added benefit that the plugin will run outside the browser process, thus, if it crashes it shouldn't take the browser with it. Actually I don't know why isn't nspluginwrapper used even on the x86 fedora, AFAICS there are only benefits on its use. Rui From aweterings at gmail.com Tue Nov 13 20:00:15 2007 From: aweterings at gmail.com (Arno Weterings) Date: Tue, 13 Nov 2007 21:00:15 +0100 Subject: Problem with Fedora core 8 installer Message-ID: <000901c8262f$d70497e0$850dc7a0$@com> Hello, When I run the Fedora core 8 installer my laptop hangs with the "running /sbin/loader", I've left my laptop on for over an hour but still nothing is happened. Please help Gr Arno -------------- next part -------------- An HTML attachment was scrubbed... URL: From mauricio at projetofedora.org Tue Nov 13 20:02:09 2007 From: mauricio at projetofedora.org (Mauricio Pretto) Date: Tue, 13 Nov 2007 18:02:09 -0200 Subject: Problem with Fedora core 8 installer In-Reply-To: <000901c8262f$d70497e0$850dc7a0$@com> References: <000901c8262f$d70497e0$850dc7a0$@com> Message-ID: <473A02C1.8080407@projetofedora.org> Set acpi=off at the installer boot Pretto http://fedoraproject.org/wiki/MauricioPretto Arno Weterings wrote: > Hello, > > > > When I run the Fedora core 8 installer my laptop hangs with the ?running > /sbin/loader?, I?ve left my laptop on for over an hour but still nothing > is happened. Please help > > > > Gr Arno > > > ------------------------------------------------------------------------ > > _______________________________________________ > Fedora-laptop-list mailing list > Fedora-laptop-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-laptop-list From mauricio at projetofedora.org Tue Nov 13 21:30:11 2007 From: mauricio at projetofedora.org (Mauricio Pretto) Date: Tue, 13 Nov 2007 19:30:11 -0200 Subject: T61 monitor In-Reply-To: <20071109134235.GD30977@jasmine.xos.nl> References: <8ab6097c0711081407p3bf09311x93be563717b79230@mail.gmail.com> <20071108221519.GA24187@jasmine.xos.nl> <8ab6097c0711082055y6e556989pdcf6b99e7cee32bd@mail.gmail.com> <20071109134235.GD30977@jasmine.xos.nl> Message-ID: <473A1763.3090709@projetofedora.org> Make sure you have 915resolution installed and configured, im quite sure that will solve your problems. Regards Pretto http://fedoraproject.org/wiki/MauricioPretto Jos Vos wrote: > On Fri, Nov 09, 2007 at 06:55:15AM +0200, Peter Lauri wrote: > >> Hi, I did change the things you said. However, as before (as I forgot >> to mention) is that the system-config-display cannot be opened. This >> is my xorg.conf content for the moment. And after that is the log for >> Xorg. I am a very novice in this area, sorry for that :( But I'd >> really like to use Fedora on my laptop. > > Your config is really exactly the same (except for a few spaces) as what > we use here. To be 100% sure about typos etc., I'll send you a copy of > our xorg.conf in private mail (please try that, just in case...), as > well as our (long) Xorg.0.log file. > > Did you also restart the laptop after making the changes? I'm not sure > if this is needed (normally it's not), because of that special issue > of the TV-output. > > You shouldn't need to run system-config-display (that only works if > X is already running), with this xorg.conf it "just should work". > > Let me know if you get it working, or otherwise send the output of > "lspci -v", as Lenovo might have changed some hardware. > > B.t.w., sound on the T61 is still not working, we hope for F8 (not > tried yet), as this is said to be solved in newer versions of ALSA. > From jos at xos.nl Tue Nov 13 21:35:44 2007 From: jos at xos.nl (Jos Vos) Date: Tue, 13 Nov 2007 22:35:44 +0100 Subject: T61 monitor In-Reply-To: <473A1763.3090709@projetofedora.org> References: <8ab6097c0711081407p3bf09311x93be563717b79230@mail.gmail.com> <20071108221519.GA24187@jasmine.xos.nl> <8ab6097c0711082055y6e556989pdcf6b99e7cee32bd@mail.gmail.com> <20071109134235.GD30977@jasmine.xos.nl> <473A1763.3090709@projetofedora.org> Message-ID: <20071113213544.GA16869@jasmine.xos.nl> On Tue, Nov 13, 2007 at 07:30:11PM -0200, Mauricio Pretto wrote: > Make sure you have 915resolution installed and configured, im quite sure > that will solve your problems. I don't think so. I never needed 915resolution on the T61. The standard resolution is 1280x800 and (thus?) the video chip seems to know about this. -- -- Jos Vos -- X/OS Experts in Open Systems BV | Phone: +31 20 6938364 -- Amsterdam, The Netherlands | Fax: +31 20 6948204 From aweterings at gmail.com Wed Nov 14 08:02:24 2007 From: aweterings at gmail.com (Arno Weterings) Date: Wed, 14 Nov 2007 09:02:24 +0100 Subject: FW: Problem with Fedora core 8 installer Message-ID: <002101c82694$b70dcf50$25296df0$@com> Hello, The option you gave me worked very well, my next problem is with the installer, when I run the installdisk check it says the dvd is good, I run the installer, selecting partitions, software etc, and then the installer start installing. After the formatting stuff the installer come with the can't find package error. The only options are retry and reboot. How can this happen while my install-disc is correct. Please help Gr Arno Van: Mohd Zeeshan [mailto:zeehere at gmail.com] Verzonden: Wednesday, November 14, 2007 3:15 AM Aan: Arno Weterings Onderwerp: Re: Problem with Fedora core 8 installer When you get the first menu to install/upgrade fedora, press TAB and append these lines to the existing line floppy.allowed_mask=0 clocksource=acpi_pm Also if you have many extra non-standard software installed on your last Fedora 7, that yum will not find on its standard repositories, then also it will hang on resolving dependencies at later stage. Therefore before upgrading, remove all extras. I have faced all these issues myself. Thanks. Zee. On Nov 14, 2007 1:30 AM, Arno Weterings wrote: Hello, When I run the Fedora core 8 installer my laptop hangs with the "running /sbin/loader", I've left my laptop on for over an hour but still nothing is happened. Please help Gr Arno _______________________________________________ Fedora-laptop-list mailing list Fedora-laptop-list at redhat.com http://www.redhat.com/mailman/listinfo/fedora-laptop-list -- ::Zeeshan:: -------------- next part -------------- An HTML attachment was scrubbed... URL: From katzj at redhat.com Wed Nov 14 13:39:31 2007 From: katzj at redhat.com (Jeremy Katz) Date: Wed, 14 Nov 2007 08:39:31 -0500 Subject: T61 monitor In-Reply-To: <473A1763.3090709@projetofedora.org> References: <8ab6097c0711081407p3bf09311x93be563717b79230@mail.gmail.com> <20071108221519.GA24187@jasmine.xos.nl> <8ab6097c0711082055y6e556989pdcf6b99e7cee32bd@mail.gmail.com> <20071109134235.GD30977@jasmine.xos.nl> <473A1763.3090709@projetofedora.org> Message-ID: <1195047571.17950.44.camel@localhost.localdomain> On Tue, 2007-11-13 at 19:30 -0200, Mauricio Pretto wrote: > Make sure you have 915resolution installed and configured, im quite sure > that will solve your problems. 915resolution shouldn't be used any more now that we configure things to use the intel driver rather than i810. The intel driver supports native modesetting and thus avoids the need for 915resolution. In fact, given that we're switching to only including the intel driver in Fedora 9, it's probably time to drop 915resolution too Jeremy From mansour77 at yahoo.com Wed Nov 14 15:14:57 2007 From: mansour77 at yahoo.com (Mansour) Date: Wed, 14 Nov 2007 11:14:57 -0400 Subject: Problem with Fedora core 8 installer In-Reply-To: <473A02C1.8080407@projetofedora.org> References: <000901c8262f$d70497e0$850dc7a0$@com> <473A02C1.8080407@projetofedora.org> Message-ID: <473B10F1.7000509@yahoo.com> I tried it and it worked. Thank you. Mauricio Pretto wrote: > Set acpi=off at the installer boot > > Pretto > http://fedoraproject.org/wiki/MauricioPretto > > > > Arno Weterings wrote: > >> Hello, >> >> >> >> When I run the Fedora core 8 installer my laptop hangs with the ?running >> /sbin/loader?, I?ve left my laptop on for over an hour but still nothing >> is happened. Please help >> >> >> >> Gr Arno >> >> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Fedora-laptop-list mailing list >> Fedora-laptop-list at redhat.com >> http://www.redhat.com/mailman/listinfo/fedora-laptop-list >> > > _______________________________________________ > Fedora-laptop-list mailing list > Fedora-laptop-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-laptop-list > > From mauricio at projetofedora.org Wed Nov 14 17:48:03 2007 From: mauricio at projetofedora.org (Mauricio Pretto) Date: Wed, 14 Nov 2007 15:48:03 -0200 Subject: T61 monitor In-Reply-To: <1195047571.17950.44.camel@localhost.localdomain> References: <8ab6097c0711081407p3bf09311x93be563717b79230@mail.gmail.com> <20071108221519.GA24187@jasmine.xos.nl> <8ab6097c0711082055y6e556989pdcf6b99e7cee32bd@mail.gmail.com> <20071109134235.GD30977@jasmine.xos.nl> <473A1763.3090709@projetofedora.org> <1195047571.17950.44.camel@localhost.localdomain> Message-ID: <473B34D3.1090600@projetofedora.org> He is using F7 Pretto http://fedoraproject.org/wiki/MauricioPretto Jeremy Katz wrote: > On Tue, 2007-11-13 at 19:30 -0200, Mauricio Pretto wrote: >> Make sure you have 915resolution installed and configured, im quite sure >> that will solve your problems. > > 915resolution shouldn't be used any more now that we configure things to > use the intel driver rather than i810. The intel driver supports native > modesetting and thus avoids the need for 915resolution. > > In fact, given that we're switching to only including the intel driver > in Fedora 9, it's probably time to drop 915resolution too > > Jeremy > > _______________________________________________ > Fedora-laptop-list mailing list > Fedora-laptop-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-laptop-list From thilinamb at gmail.com Tue Nov 20 09:57:49 2007 From: thilinamb at gmail.com (Thilina Buddhika) Date: Tue, 20 Nov 2007 15:27:49 +0530 Subject: support for ati VGA and broadcom wireless cards Message-ID: <930503ab0711200157n5d5deed9jeacbe09e9d8884f3@mail.gmail.com> Hi, I am using a DELL INSPIRON 6400, with ati radeon x1300 graphics card. I found it difficult to install other linux based OSs due to this VGA. Will i be able to install fedora 8 in my laptop, without any difficulty. Also it has a broadcom wireless card. does fedora 8 supports this ? thanks and regards, buddhika From dhhb2304 at quicknet.nl Tue Nov 20 10:05:49 2007 From: dhhb2304 at quicknet.nl (dhhb2304) Date: Tue, 20 Nov 2007 11:05:49 +0100 Subject: ASUS M6000: dual head & upgrade to fedora 8 Message-ID: <4742B17D.10607@quicknet.nl> An HTML attachment was scrubbed... URL: From mauricio at projetofedora.org Tue Nov 20 10:06:52 2007 From: mauricio at projetofedora.org (Mauricio Pretto) Date: Tue, 20 Nov 2007 08:06:52 -0200 Subject: support for ati VGA and broadcom wireless cards In-Reply-To: <930503ab0711200157n5d5deed9jeacbe09e9d8884f3@mail.gmail.com> References: <930503ab0711200157n5d5deed9jeacbe09e9d8884f3@mail.gmail.com> Message-ID: <4742B1BC.1070303@projetofedora.org> Thilina Buddhika wrote: > Hi, > I am using a DELL INSPIRON 6400, with ati radeon x1300 graphics card. > I found it difficult to install other linux based OSs due to this VGA. > Will i be able to install fedora 8 in my laptop, without any > difficulty. > > Also it has a broadcom wireless card. does fedora 8 supports this ? > > > thanks and regards, > buddhika > > _______________________________________________ > Fedora-laptop-list mailing list > Fedora-laptop-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-laptop-list The video should work out the box, and you can use the livna drivers for 3d. The broadcom i'm not sure but i think you will need some extra hacking. -- Pretto http://fedoraproject.org/wiki/MauricioPretto From dhhb2304 at quicknet.nl Thu Nov 22 08:45:01 2007 From: dhhb2304 at quicknet.nl (dhhb2304) Date: Thu, 22 Nov 2007 09:45:01 +0100 Subject: ASUS M6000: dual head & upgrade to fedora 8 Message-ID: <4745418D.6040609@quicknet.nl> Since my message earlier was sent in HTML-format, I repeat it here as text: (sorry for the inconvenience) I have an Asus M6000 laptop that gives me two problems: *1. *when attaching a separate monitor to the VGA-slot on the back, I get a copy of the picture I see on the laptop screen (as it should!). Then, as root I enter into monitor management (sorry, my F7 is in Dutch, so the correct term is probably different in English) and activate dual head, giving the screen size and resolution of the external monitor. after OK, I get the order to restart X for the change to take effect. After having done this by logging out and again logging in, the laptop screen remains black and only the external monitor shows a picture. After restarting the laptop without the external monitor all is back as it used to be. The video card in this laptop is a ATI Technologies RV350 [Mobility Radeon 9600 M10] Has anybody an idea how to use the external monitor in order to enable an extended desktop? I have tried to see whether I could change /etc/X/xorg.conf but did not find a way to do this. I hoped fedora 8 would solve this problem, but see below: 2. I have downloaded fedora 8, burned this on a disk and used the disk to install on a desktop. No problem. I took the same disk to my Asus (dual boot with Windows XP) and started up from the disk and chose the option "upgrade an existing system". the system began collecting installed packages end thereafter checking dependencies. about 40% through this the system hangs completely (no mouse action either) and only using the on/off button of the laptop gives any result. B. From lists at hambrecht.org Thu Nov 22 11:44:05 2007 From: lists at hambrecht.org (Kai-Thorsten Hambrecht) Date: Thu, 22 Nov 2007 12:44:05 +0100 Subject: ASUS M6000: dual head & upgrade to fedora 8 In-Reply-To: <4745418D.6040609@quicknet.nl> References: <4745418D.6040609@quicknet.nl> Message-ID: <47456B85.10000@hambrecht.org> Hello, > 2. I have downloaded fedora 8, burned this on a disk and used the disk > to install on a desktop. No problem. I took the same disk to my Asus > (dual boot with Windows XP) and started up from the disk and chose the > option "upgrade an existing system". the system began collecting > installed packages end thereafter checking dependencies. about 40% > through this the system hangs completely (no mouse action either) and > only using the on/off button of the laptop gives any result. maybe you should see Redhat Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=372011 but in F8 there is also an issue with dual-head on ATI cards. See: https://bugzilla.redhat.com/show_bug.cgi?id=374901 Kai. From dhhb2304 at quicknet.nl Thu Nov 22 13:01:12 2007 From: dhhb2304 at quicknet.nl (dhhb2304) Date: Thu, 22 Nov 2007 14:01:12 +0100 Subject: ASUS M6000: dual head & upgrade to fedora 8 In-Reply-To: <47456B85.10000@hambrecht.org> References: <4745418D.6040609@quicknet.nl> <47456B85.10000@hambrecht.org> Message-ID: <47457D98.3070103@quicknet.nl> Kai-Thorsten Hambrecht schreef: > Hello, > >> 2. I have downloaded fedora 8, burned this on a disk and used the disk >> to install on a desktop. No problem. I took the same disk to my Asus >> (dual boot with Windows XP) and started up from the disk and chose the >> option "upgrade an existing system". the system began collecting >> installed packages end thereafter checking dependencies. about 40% >> through this the system hangs completely (no mouse action either) and >> only using the on/off button of the laptop gives any result. > > maybe you should see Redhat Bugzilla: > https://bugzilla.redhat.com/show_bug.cgi?id=372011 > > but in F8 there is also an issue with dual-head on ATI cards. See: > https://bugzilla.redhat.com/show_bug.cgi?id=374901 > > Kai. > > > > Thanks. After reading through the items posted for bug 372011 (=upgrade to F8), I decided to stick with F7 and wait for a new iso-image (or F9...). Especially since the dual-head problem seems as yet unresolved, also in F8. B. From amar.hs at gmail.com Thu Nov 22 13:08:31 2007 From: amar.hs at gmail.com (Amar) Date: Thu, 22 Nov 2007 18:38:31 +0530 Subject: driver for TP Link WN610G Message-ID: Hi, Need help with driver for TP Link WN610G wireless network card amar -------------- next part -------------- An HTML attachment was scrubbed... URL: From fedora at shmuelhome.mine.nu Thu Nov 22 22:26:32 2007 From: fedora at shmuelhome.mine.nu (shmuel siegel) Date: Fri, 23 Nov 2007 00:26:32 +0200 Subject: support for ati VGA and broadcom wireless cards In-Reply-To: <930503ab0711200157n5d5deed9jeacbe09e9d8884f3@mail.gmail.com> References: <930503ab0711200157n5d5deed9jeacbe09e9d8884f3@mail.gmail.com> Message-ID: <47460218.1060105@shmuelhome.mine.nu> Thilina Buddhika wrote: > Hi, > I am using a DELL INSPIRON 6400, with ati radeon x1300 graphics card. > I found it difficult to install other linux based OSs due to this VGA. > Will i be able to install fedora 8 in my laptop, without any > difficulty. > > Also it has a broadcom wireless card. does fedora 8 supports this ? > > > thanks and regards, > buddhika > I have a lattitue d620. For fedora 6 and 7 I couldn't get it to work on my encrypted wireless but fedora 8 worked. It is not, however straightforward since fedora is not allowed to ship the drivers for the broadcom wireless. You will have to retrieve the drivers, use fwcutter and set it up yourself. It would be nice if fedora supplied a script that magically did all of the work after you retrieved the drivers. Sorry, I can't help with the graphics card. From mauricio at projetofedora.org Fri Nov 23 06:58:11 2007 From: mauricio at projetofedora.org (Mauricio Pretto) Date: Fri, 23 Nov 2007 07:58:11 +0100 Subject: driver for TP Link WN610G In-Reply-To: References: Message-ID: <47467A03.3050406@projetofedora.org> Amar wrote: > Hi, > Need help with > driver for TP Link WN610G wireless network card > amar > > > ------------------------------------------------------------------------ > > _______________________________________________ > Fedora-laptop-list mailing list > Fedora-laptop-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-laptop-list Can you supply us with more information? What seems to be your problem? -- Pretto http://fedoraproject.org/wiki/MauricioPretto From amar.hs at gmail.com Fri Nov 23 08:23:55 2007 From: amar.hs at gmail.com (Amar) Date: Fri, 23 Nov 2007 13:53:55 +0530 Subject: driver for TP Link WN610G In-Reply-To: <47467A03.3050406@projetofedora.org> References: <47467A03.3050406@projetofedora.org> Message-ID: Hi, The Wireselss network card is not detected by Fedora. I was useing TP Link WN610G wireless network card with my laptop with windows. Checked up TPlink website but they have given driver only for Windows. Best regards, amar On 23/11/2007, Mauricio Pretto wrote: > > Amar wrote: > > Hi, > > Need help with > > driver for TP Link WN610G wireless network card > > amar > > > > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Fedora-laptop-list mailing list > > Fedora-laptop-list at redhat.com > > http://www.redhat.com/mailman/listinfo/fedora-laptop-list > > Can you supply us with more information? > What seems to be your problem? > > -- > Pretto > http://fedoraproject.org/wiki/MauricioPretto > > _______________________________________________ > Fedora-laptop-list mailing list > Fedora-laptop-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-laptop-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From smartkenny at gmail.com Fri Nov 23 22:15:55 2007 From: smartkenny at gmail.com (smartkenny) Date: Fri, 23 Nov 2007 14:15:55 -0800 Subject: Suspend succeed, wake up lost screen Message-ID: <4747511B.5090909@gmail.com> Hi, all Fedora 8 on my Acer Aspire 1681 has problem to suspend/wake up. Actually, it suspend successfully, but when wake up, the screen is completely black. The keyboard works still, because the caps lock LED works. I can ssh remote login from other machine, and get the attached dmesg output. I am using 915resolution+i810 drv to support my 1280x800 resolution. I did try intel drv which actually is the default when install Fedora 8, but the problem is when wake up, the screen is also complete black, plus the keyboard doesn't respond. Any suggestion? I hope the dmesg output can help the developers to improve the suspending. Thank. Kenny -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: fail.txt URL: From jfsnutter at yahoo.com Sat Nov 24 04:29:46 2007 From: jfsnutter at yahoo.com (Joseph F. Shea) Date: Fri, 23 Nov 2007 20:29:46 -0800 (PST) Subject: hpdv9500 Message-ID: <927654.76865.qm@web39510.mail.mud.yahoo.com> I tried loading Ubuntu 7.10 on to an HP dv9500 laptop (AMD Turion 64 x2 TL-58 1.9Ghz), but could not configure Nvidia card or Broadcom wireless card. (Saw some suggestions for fixing the NVidia card, but need wireless connection to do it). Will Fedora 8 load on this machine without a lot of tweaking? From tiagomatos at gmail.com Sat Nov 24 11:30:46 2007 From: tiagomatos at gmail.com (Rui Tiago Matos) Date: Sat, 24 Nov 2007 11:30:46 +0000 Subject: hpdv9500 In-Reply-To: <927654.76865.qm@web39510.mail.mud.yahoo.com> References: <927654.76865.qm@web39510.mail.mud.yahoo.com> Message-ID: On 24/11/2007, Joseph F. Shea wrote: > I tried loading Ubuntu 7.10 on to an HP dv9500 laptop (AMD Turion 64 x2 TL-58 1.9Ghz), but could not configure Nvidia card or Broadcom wireless card. (Saw some suggestions for fixing the NVidia card, but need wireless connection to do it). Will Fedora 8 load on this machine without a lot of tweaking? The nvidia card I know that it will only work with the nv driver out of the box, i.e. so so 2D performance and no 3D, if you want better performance and don't mind using a proprietary driver, check the vendor's website. The broadcom I don't know and you don't provide model numbers so it would be harder to find. Your best bet: get yourself a live CD[1]. If it doesn't work, file bugs[2]. It's not so hard to do this by yourself. Rui [1] http://fedoraproject.org/get-fedora [2] https://bugzilla.redhat.com/enter_bug.cgi?format=guided From willhs at siu.edu Tue Nov 27 06:51:12 2007 From: willhs at siu.edu (willhs at siu.edu) Date: Tue, 27 Nov 2007 00:51:12 -0600 Subject: Wireless Broadcom BCM93411MCG wlan mini-pci Message-ID: <1196146272-27751.00013.00255-smmsdV2.1.6@saluki-mailhub.siu.edu> I have a compaq presario c500 running fedora core 8 (with automatic updates already installed) with a "Broadcom Corparation BCM93411MCG wlan mini-pci" card. It shows up in network configuration under hardware as an ethernet card and not a wireless connection. I tried to delete it as an ethernet and set it up as a wireless, yet "Broadcom Corparation BCM93411MCG wlan mini-pci" does not show up under "select wireless device" or "adapter type". Yet when I add it as an ethernet connection it shows up under "adapter type" or "select ethernet connection" yet if I install it, it has a status of 'ok', yet does not function or activate. Drivers? Any ideas? From miatared at gmail.com Tue Nov 27 18:02:46 2007 From: miatared at gmail.com (MiataRed) Date: Tue, 27 Nov 2007 13:02:46 -0500 Subject: Help in installing Fedora 8 Message-ID: <000001c8311f$b798f0e0$26cad2a0$@com> I hope someone can give some ideas. I have a Toshiba Port?g? 3500 laptop. (P3 1.3GHz, 1 GB of RAM) It is a Tablet PC and has been running XP Pro Tablet Ed. I have been trying to install Fedora for many months already and am not giving up I have successfully installed Fedora 8 on many other PCs and laptops, but this one is a real challenge to me. It is a non-standard PC: no built-in CD-ROM, it uses a proprietary PCMCIA model from Targus made for this model, and special drivers are needed to run it, DOS drivers do exist, but no Linux drivers. I only use it to re-install Windows XP as the Toshiba recovery CDs need it. I do not care for the Tablet PC specific functions, as I use it as a standard laptop. I also have a standard external USB 2.0 CD/DVD-RW, however it will not boot from this ? but I do have an external FDD and it will boot from this. If I try to boot the Fedora DVD, using the PCMCIA CD-ROM it will get started, but then Anaconda will not recognize the device, and stops ? and no Linux drivers exists. So I figure I could use the USB CD/DVD-ROM, as I think this will be a valid device for Anaconda. I need specific instructions to create floppies to get a successful Fedora 8 installation. Can anyone help ? Thank you. Denis No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.16.8/1154 - Release Date: 11/27/07 11:40 AM -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhhb2304 at quicknet.nl Tue Nov 27 18:35:53 2007 From: dhhb2304 at quicknet.nl (dhhb2304) Date: Tue, 27 Nov 2007 19:35:53 +0100 Subject: ASUS M6000: dual head & upgrade to fedora 8: Solution?! In-Reply-To: <47457D98.3070103@quicknet.nl> References: <4745418D.6040609@quicknet.nl> <47456B85.10000@hambrecht.org> <47457D98.3070103@quicknet.nl> Message-ID: <474C6389.6090104@quicknet.nl> dhhb2304 schreef: > Kai-Thorsten Hambrecht schreef: >> Hello, >> >>> 2. I have downloaded fedora 8, burned this on a disk and used the disk >>> to install on a desktop. No problem. I took the same disk to my Asus >>> (dual boot with Windows XP) and started up from the disk and chose the >>> option "upgrade an existing system". the system began collecting >>> installed packages end thereafter checking dependencies. about 40% >>> through this the system hangs completely (no mouse action either) and >>> only using the on/off button of the laptop gives any result. >> >> maybe you should see Redhat Bugzilla: >> https://bugzilla.redhat.com/show_bug.cgi?id=372011 >> >> but in F8 there is also an issue with dual-head on ATI cards. See: >> https://bugzilla.redhat.com/show_bug.cgi?id=374901 >> >> Kai. >> >> >> >> > Thanks. After reading through the items posted for bug 372011 > (=upgrade to F8), I decided to stick with F7 and wait for a new > iso-image (or F9...). > Especially since the dual-head problem seems as yet unresolved, also > in F8. > B. > My statement here above was after all not satisfactory to me, so I tried to find a solution anyhow. Success obviously is the joint effort of inspiration and transpiration... A. Upgrade: I got it working! The reason nothing happened at first when I gave, after hitting the ESC-key, the boot command: updates=http://katzj.fedorapeople.org/updates-f8-yumloop.img was simple: as usual I relied on the wireless connection. But at start-up of the F8 DVD there is no wireless connection yet. After plugging in the Ethernet cable and again booting the DVD the upgrade started and after about 2 hours was complete. A few personal settings were lost in the upgrade, but it definitely is less work than installing completely new and then apply the personal settings. B. Dual head: I got it working also by using the right items in /etc/X11/xorg.conf after installing the necessary driver by the command: yum install kmod-fglrx My copy of xorg.conf is: ========= # Xorg configuration created by system-config-display Section "ServerLayout" Identifier "Multihead layout" Screen 0 "Screen0" LeftOf "Screen1" Screen 1 "Screen1" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Synaptics" "CorePointer" Option "Xinerama" "on" Option "Clone" "off" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "XkbModel" "pc105" Option "XkbLayout" "us" Option "XkbVariant" "intl" EndSection Section "InputDevice" Identifier "Synaptics" Driver "synaptics" Option "Device" "/dev/input/mice" Option "Protocol" "auto-dev" Option "Emulate3Buttons" "yes" EndSection Section "ServerFlags" Option "RandR" "on" EndSection Section "Monitor" Identifier "Monitor1" VendorName "Monitor Vendor" ModelName "LCD Panel 1024x768" HorizSync 31.5 - 48.0 VertRefresh 56.0 - 65.0 Option "dpms" EndSection Section "Device" Identifier "Videocard0" Driver "fglrx" VendorName "Monitor Vendor" BoardName "ATI Technologies RV350 [Mobility Radeon 9600 M10]" BusID "PCI:1:0:0" Screen 0 EndSection Section "Device" Identifier "Videocard1" Driver "fglrx" VendorName "Monitor Vendor" BoardName "ATI Technologies RV350 [Mobility Radeon 9600 M10]" BusID "PCI:1:0:0" Screen 1 EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1280x800" "1280x720" "1152x864" "1152x768" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "Screen" Identifier "Screen1" Device "Videocard1" Monitor "Monitor1" DefaultDepth 24 SubSection "Display" Viewport 0 0 Depth 24 Modes "1024x768" "800x600" "640x480" EndSubSection EndSection =============== The desktop is stretched now over the two monitors, which was my aim. The only thing still bothering me is the resolution of the second monitor: 800x600, even though 1024x768 is mentioned in xorg.conf. Altering the resolution should be possible by using xrandr, but so far I have not been able to make the xorg server "see" xrandr. If I succeed therein, I will let you know. Hope that somebody beats me to it! B. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mansour77 at yahoo.com Tue Nov 27 20:36:30 2007 From: mansour77 at yahoo.com (Mansour) Date: Tue, 27 Nov 2007 16:36:30 -0400 Subject: Wireless Broadcom BCM93411MCG wlan mini-pci In-Reply-To: <1196146272-27751.00013.00255-smmsdV2.1.6@saluki-mailhub.siu.edu> References: <1196146272-27751.00013.00255-smmsdV2.1.6@saluki-mailhub.siu.edu> Message-ID: <474C7FCE.9080901@yahoo.com> willhs at siu.edu wrote: > I have a compaq presario c500 running fedora core 8 (with > automatic updates already installed) with a "Broadcom > Corparation BCM93411MCG wlan mini-pci" card. It shows up in > network configuration under hardware as an ethernet card and not > a wireless connection. I tried to delete it as an ethernet and > set it up as a wireless, yet "Broadcom Corparation BCM93411MCG > wlan mini-pci" does not show up under "select wireless device" or > "adapter type". Yet when I add it as an ethernet connection it > shows up under "adapter type" or "select ethernet connection" yet > if I install it, it has a status of 'ok', yet does not function > or activate. > > Drivers? > Yes, it looks like it's a driver issue. We need more info to be able to help. post the output of these commands: /sbin/lspci | grep -i broad /sbin/lsmod | sort uname -a > Any ideas? > > > _______________________________________________ > Fedora-laptop-list mailing list > Fedora-laptop-list at redhat.com > http://www.redhat.com/mailman/listinfo/fedora-laptop-list > > From willhs at siu.edu Thu Nov 29 01:24:13 2007 From: willhs at siu.edu (willhs at siu.edu) Date: Wed, 28 Nov 2007 19:24:13 -0600 Subject: Wireless Broadcom BCM93411MCG wlan mini-pci In-Reply-To: <474C7FCE.9080901@yahoo.com> Message-ID: <1196299453-7572.00019.00802-smmsdV2.1.6@saluki-mailhub.siu.edu> Here are the outputs: [root at ws150219 ~]# /sbin/lspci | grep -i broad 06:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01) [root at ws150219 ~]# /sbin/lspci | sort 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03) 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 01) 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 01) 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 (rev 01) 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 (rev 01) 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 (rev 01) 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 (rev 01) 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e1) 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 01) 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 01) 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller (rev 01) 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus Controller (rev 01) 06:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan mini-PCI (rev 01) 08:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) [root at ws150219 ~]# From mansour77 at yahoo.com Thu Nov 29 01:42:49 2007 From: mansour77 at yahoo.com (Mansour) Date: Wed, 28 Nov 2007 21:42:49 -0400 Subject: Wireless Broadcom BCM93411MCG wlan mini-pci In-Reply-To: <1196299453-7572.00019.00802-smmsdV2.1.6@saluki-mailhub.siu.edu> References: <1196299453-7572.00019.00802-smmsdV2.1.6@saluki-mailhub.siu.edu> Message-ID: <474E1919.8080006@yahoo.com> Hello: You sent me only the first output I asked for. I was expecting you to run /sbin/lsmod and not /sbin/lspci. The first and second output you gave me are the same except the second one is a sorted list for all the pci devices you have. We need to find out what models are loaded. So that we can decide if it's a configuration issue or a driver. You can list the models that are loaded by invoking "/sbin/lsmod" and then sort them for better view. Just execute "/sbin/lsmod | sort" and send me the output. willhs at siu.edu wrote: > Here are the outputs: > > [root at ws150219 ~]# /sbin/lspci | grep -i broad > 06:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan > mini-PCI (rev 01) > [root at ws150219 ~]# /sbin/lspci | sort > 00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, > 943/940GML and 945GT Express Memory Controller Hub (rev 03) > 00:02.0 VGA compatible controller: Intel Corporation Mobile > 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) > 00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS, > 943/940GML Express Integrated Graphics Controller (rev 03) > 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High > Definition Audio Controller (rev 01) > 00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI > Express Port 1 (rev 01) > 00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI > Express Port 3 (rev 01) > 00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) > USB UHCI Controller #1 (rev 01) > 00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) > USB UHCI Controller #2 (rev 01) > 00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) > USB UHCI Controller #3 (rev 01) > 00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) > USB2 EHCI Controller (rev 01) > 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge > (rev e1) > 00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC > Interface Bridge (rev 01) > 00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE > Controller (rev 01) > 00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7 > Family) SATA AHCI Controller (rev 01) > 00:1f.3 SMBus: Intel Corporation 82801G (ICH7 Family) SMBus > Controller (rev 01) > 06:00.0 Network controller: Broadcom Corporation BCM94311MCG wlan > mini-PCI (rev 01) > 08:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL-8139/8139C/8139C+ (rev 10) > [root at ws150219 ~]# > > > > From willhs at siu.edu Thu Nov 29 02:00:10 2007 From: willhs at siu.edu (willhs at siu.edu) Date: Wed, 28 Nov 2007 20:00:10 -0600 Subject: Wireless Broadcom BCM93411MCG wlan mini-pci In-Reply-To: <474E1919.8080006@yahoo.com> Message-ID: <1196301610-7572.00023.00809-smmsdV2.1.6@saluki-mailhub.siu.edu> B43 has to do with Broadcom... B43-fwcutter... b43 shows up in lines b43 , rfkill, input_polldev, mac80211, and ssb sorted output: /sbin/lsmod | sort 8139cp 21697 0 8139too 24513 0 ac 8133 0 ahci 22597 2 arc4 5953 2 ata_piix 16709 1 autofs4 20421 2 b43 129637 0 battery 14025 0 blkcipher 9029 1 ecb bluetooth 49317 4 rfcomm,l2cap button 10321 0 cdrom 33889 1 sr_mod cfg80211 10441 1 mac80211 dm_mirror 21569 0 dm_mod 46209 11 dm_multipath,dm_snapshot,dm_zero,dm_mirror dm_multipath 18249 0 dm_snapshot 17765 0 dm_zero 5825 0 drm 67029 3 i915 ecb 6721 2 ehci_hcd 31693 0 ext3 110665 3 i2c_core 21825 1 i2c_i801 i2c_i801 12113 0 i915 23745 2 input_polldev 7369 1 b43 ip6table_filter 6337 1 ip6_tables 15109 2 ip6t_ipv6header,ip6table_filter ip6t_ipv6header 6209 2 ip6t_REJECT 8257 2 iptable_filter 6465 1 ip_tables 14213 1 iptable_filter ipt_REJECT 7617 2 ipv6 245989 14 nf_conntrack_ipv6,ip6t_REJECT iTCO_vendor_support 7109 1 iTCO_wdt iTCO_wdt 13797 0 jbd 52457 1 ext3 joydev 11649 0 l2cap 25537 9 rfcomm libata 99633 2 ata_piix,ahci loop 16581 0 mac80211 112461 1 b43 mbcache 10177 1 ext3 mii 8385 2 8139too,8139cp Module Size Used by nf_conntrack 51977 3 nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state nf_conntrack_ipv4 11717 2 nf_conntrack_ipv6 18769 2 nfnetlink 8281 3 nf_conntrack_ipv4,nf_conntrack_ipv6,nf_conntrack nls_utf8 5825 1 ohci_hcd 21445 0 output 6977 1 video pcspkr 6593 0 rfcomm 36825 0 rfkill 9297 1 b43 scsi_mod 119757 4 sg,sr_mod,libata,sd_mod sd_mod 27329 3 serio_raw 9029 0 sg 31965 0 snd 43461 11 snd_hda_intel,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_hwdep snd_hda_intel 274529 1 snd_hwdep 10309 1 snd_hda_intel snd_mixer_oss 16705 1 snd_pcm_oss snd_page_alloc 11337 2 snd_hda_intel,snd_pcm snd_pcm 63685 2 snd_hda_intel,snd_pcm_oss snd_pcm_oss 37569 0 snd_seq 44849 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 10061 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_seq_dummy 6725 0 snd_seq_midi_event 9793 1 snd_seq_oss snd_seq_oss 29889 0 snd_timer 20549 2 snd_seq,snd_pcm soundcore 9633 1 snd sr_mod 17509 1 ssb 30021 1 b43 sunrpc 140765 1 uhci_hcd 23633 0 video 19921 0 x_tables 14277 7 ipt_REJECT,ip_tables,xt_state,xt_tcpudp,ip6t_ipv6header,ip6t_REJECT,ip6_tables xt_state 6081 4 xt_tcpudp 6977 8 From mansour77 at yahoo.com Thu Nov 29 06:00:38 2007 From: mansour77 at yahoo.com (Mansour) Date: Thu, 29 Nov 2007 02:00:38 -0400 Subject: Wireless Broadcom BCM93411MCG wlan mini-pci In-Reply-To: <1196301610-7572.00023.00809-smmsdV2.1.6@saluki-mailhub.siu.edu> References: <1196301610-7572.00023.00809-smmsdV2.1.6@saluki-mailhub.siu.edu> Message-ID: <474E5586.1020200@yahoo.com> can you do a scan? try something like: /sbin/iwlist wlan0 scan replace wlan0 with your wireless interface. If you don't know try /sbin/ifconfig -a willhs at siu.edu wrote: > B43 has to do with Broadcom... B43-fwcutter... b43 shows up in > lines b43 , rfkill, input_polldev, mac80211, and ssb > > > > sorted output: > > /sbin/lsmod | sort > 8139cp 21697 0 > 8139too 24513 0 > ac 8133 0 > ahci 22597 2 > arc4 5953 2 > ata_piix 16709 1 > autofs4 20421 2 > b43 129637 0 > battery 14025 0 > blkcipher 9029 1 ecb > bluetooth 49317 4 rfcomm,l2cap > button 10321 0 > cdrom 33889 1 sr_mod > cfg80211 10441 1 mac80211 > dm_mirror 21569 0 > dm_mod 46209 11 > dm_multipath,dm_snapshot,dm_zero,dm_mirror > dm_multipath 18249 0 > dm_snapshot 17765 0 > dm_zero 5825 0 > drm 67029 3 i915 > ecb 6721 2 > ehci_hcd 31693 0 > ext3 110665 3 > i2c_core 21825 1 i2c_i801 > i2c_i801 12113 0 > i915 23745 2 > input_polldev 7369 1 b43 > ip6table_filter 6337 1 > ip6_tables 15109 2 ip6t_ipv6header,ip6table_filter > ip6t_ipv6header 6209 2 > ip6t_REJECT 8257 2 > iptable_filter 6465 1 > ip_tables 14213 1 iptable_filter > ipt_REJECT 7617 2 > ipv6 245989 14 nf_conntrack_ipv6,ip6t_REJECT > iTCO_vendor_support 7109 1 iTCO_wdt > iTCO_wdt 13797 0 > jbd 52457 1 ext3 > joydev 11649 0 > l2cap 25537 9 rfcomm > libata 99633 2 ata_piix,ahci > loop 16581 0 > mac80211 112461 1 b43 > mbcache 10177 1 ext3 > mii 8385 2 8139too,8139cp > Module Size Used by > nf_conntrack 51977 3 > nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state > nf_conntrack_ipv4 11717 2 > nf_conntrack_ipv6 18769 2 > nfnetlink 8281 3 > nf_conntrack_ipv4,nf_conntrack_ipv6,nf_conntrack > nls_utf8 5825 1 > ohci_hcd 21445 0 > output 6977 1 video > pcspkr 6593 0 > rfcomm 36825 0 > rfkill 9297 1 b43 > scsi_mod 119757 4 sg,sr_mod,libata,sd_mod > sd_mod 27329 3 > serio_raw 9029 0 > sg 31965 0 > snd 43461 11 > snd_hda_intel,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer,snd_hwdep > snd_hda_intel 274529 1 > snd_hwdep 10309 1 snd_hda_intel > snd_mixer_oss 16705 1 snd_pcm_oss > snd_page_alloc 11337 2 snd_hda_intel,snd_pcm > snd_pcm 63685 2 snd_hda_intel,snd_pcm_oss > snd_pcm_oss 37569 0 > snd_seq 44849 5 > snd_seq_dummy,snd_seq_oss,snd_seq_midi_event > snd_seq_device 10061 3 snd_seq_dummy,snd_seq_oss,snd_seq > snd_seq_dummy 6725 0 > snd_seq_midi_event 9793 1 snd_seq_oss > snd_seq_oss 29889 0 > snd_timer 20549 2 snd_seq,snd_pcm > soundcore 9633 1 snd > sr_mod 17509 1 > ssb 30021 1 b43 > sunrpc 140765 1 > uhci_hcd 23633 0 > video 19921 0 > x_tables 14277 7 > ipt_REJECT,ip_tables,xt_state,xt_tcpudp,ip6t_ipv6header,ip6t_REJECT,ip6_tables > xt_state 6081 4 > xt_tcpudp 6977 8 > > > > From willhs at siu.edu Fri Nov 30 06:07:56 2007 From: willhs at siu.edu (willhs at siu.edu) Date: Fri, 30 Nov 2007 00:07:56 -0600 Subject: Wireless Broadcom BCM93411MCG wlan mini-pci In-Reply-To: <474E5586.1020200@yahoo.com> Message-ID: <1196402876-4039.00018.00223-smmsdV2.1.6@saluki-mailhub.siu.edu> [root at localhost ~]# /sbin/iwlist wlan0 scan wlan0 Interface doesn't support scanning : Network is down [root at localhost ~]# /sbin/ifconfig -a eth0 Link encap:Ethernet HWaddr 00:16:D4:A1:87:99 inet addr:131.230.150.219 Bcast:131.230.150.255 Mask:255.255.255.128 inet6 addr: fe80::216:d4ff:fea1:8799/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:22561 errors:0 dropped:0 overruns:0 frame:0 TX packets:16293 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:25176694 (24.0 MiB) TX bytes:2133263 (2.0 MiB) Interrupt:20 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:5345 errors:0 dropped:0 overruns:0 frame:0 TX packets:5345 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:3523876 (3.3 MiB) TX bytes:3523876 (3.3 MiB) wlan0 Link encap:Ethernet HWaddr 00:1A:73:00:19:E8 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) wmaster0 Link encap:UNSPEC HWaddr 00-1A-73-00-19-E8-A8-4C-00-00-00-00-00-00-00-00 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) From mansour77 at yahoo.com Fri Nov 30 14:56:41 2007 From: mansour77 at yahoo.com (Mansour) Date: Fri, 30 Nov 2007 10:56:41 -0400 Subject: Wireless Broadcom BCM93411MCG wlan mini-pci In-Reply-To: <1196402876-4039.00018.00223-smmsdV2.1.6@saluki-mailhub.siu.edu> References: <1196402876-4039.00018.00223-smmsdV2.1.6@saluki-mailhub.siu.edu> Message-ID: <475024A9.3060909@yahoo.com> I think you will need to install the correct firmware. http://linuxwireless.org/en/users/Drivers/b43#devicefirmware You need version 4. willhs at siu.edu wrote: > [root at localhost ~]# /sbin/iwlist wlan0 scan > wlan0 Interface doesn't support scanning : Network is down > > [root at localhost ~]# /sbin/ifconfig -a > eth0 Link encap:Ethernet HWaddr 00:16:D4:A1:87:99 > inet addr:131.230.150.219 Bcast:131.230.150.255 > Mask:255.255.255.128 > inet6 addr: fe80::216:d4ff:fea1:8799/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:22561 errors:0 dropped:0 overruns:0 frame:0 > TX packets:16293 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:25176694 (24.0 MiB) TX bytes:2133263 (2.0 MiB) > Interrupt:20 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > inet6 addr: ::1/128 Scope:Host > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:5345 errors:0 dropped:0 overruns:0 frame:0 > TX packets:5345 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:3523876 (3.3 MiB) TX bytes:3523876 (3.3 MiB) > > wlan0 Link encap:Ethernet HWaddr 00:1A:73:00:19:E8 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > wmaster0 Link encap:UNSPEC HWaddr > 00-1A-73-00-19-E8-A8-4C-00-00-00-00-00-00-00-00 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > >