Re: Broadcom
The downgrade failed, It kept saying that it could not find the older packages. Then I decided to do a fresh install of Etch, erasing the partion with Linux and reinstalling. Then I downloaded and installed the 2.6.21 kernel. On reboot it hung again at Uniforn CDROM Revision 3.20 after detecting the hard drive and the CDROM. I tried running update-initramfs -u -v here is the I am mystified. Your theory is that there is some bug in the 2.6.21 kernel which causes a failure when the CDROM is identified. And that it works on my 1501 because different versions of the Dell Inspiron 1501 have slightly different hardware. I guess that's possible, but it seems like a bit of a stretch. I think it's more likely that there is some difference between our two installations. Perhaps a different BIOS setting or some other configuration difference. Send an lspci and we can check if your hardware differs from mine in this regard. However I'd be surprised if this were really the problem. At least, unless someone else on the list has had some similar experience ... ? --Barak. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom
this is the output of lspci: Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 10) 00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge 00:05.0 PCI bridge: ATI Technologies Inc Unknown device 5a37 00:06.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge 00:12.0 IDE interface: ATI Technologies Inc SB600 Non-Raid-5 SATA 00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0) 00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1) 00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2) 00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3) 00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4) 00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI) 00:14.0 SMBus: ATI Technologies Inc SB600 SMBus (rev 13) 00:14.1 IDE interface: ATI Technologies Inc SB600 IDE 00:14.2 Audio device: ATI Technologies Inc SB600 Azalia 00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge 00:14.4 PCI bridge: ATI Technologies Inc SB600 PCI to PCI Bridge 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTra nsport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Con troller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscella neous Control 01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200 M] 05:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PC I Card (rev 01) 08:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) 08:01.0 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSP ro Host Adapter (rev 19) 08:01.1 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 01) Does the 2.6.21 kernel create a log even though it failed to complete the boot? I could try to locate it and see if there are any possible errors. do these systems give the bios configuration in an accessible form? Cavan On 7/9/07, Barak A. Pearlmutter [EMAIL PROTECTED] wrote: The downgrade failed, It kept saying that it could not find the older packages. Then I decided to do a fresh install of Etch, erasing the partion with Linux and reinstalling. Then I downloaded and installed the 2.6.21 kernel. On reboot it hung again at Uniforn CDROM Revision 3.20 after detecting the hard drive and the CDROM. I tried running update-initramfs -u -v here is the I am mystified. Your theory is that there is some bug in the 2.6.21 kernel which causes a failure when the CDROM is identified. And that it works on my 1501 because different versions of the Dell Inspiron 1501 have slightly different hardware. I guess that's possible, but it seems like a bit of a stretch. I think it's more likely that there is some difference between our two installations. Perhaps a different BIOS setting or some other configuration difference. Send an lspci and we can check if your hardware differs from mine in this regard. However I'd be surprised if this were really the problem. At least, unless someone else on the list has had some similar experience ... ? --Barak.
Re: Broadcom
The references to locale are due I believe to my having installed libc6 2.5-5 from testing to run a program. It also required a different tzdata. It might have been a good idea to say that you were not running a standard system earlier. You can try to downgrade your libc. But DO NOT try to remove then reinstall it, that would (if the package manager allows it) render your system unusable. The downgrade command would be apt-get install libc6/stable tzdata/stable However if it turns out that you have other packages from testing installed as well, you might need to deal with them too. After that you can try this: update-initramfs -u -v and then see if your system can boot the 2.6.21 kernel. (Be sure to save the output of the entire transcript, just in case.) --Barak. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom
True. Ok ill try that downgrade process. thanks Cavan On 7/8/07, Barak A. Pearlmutter [EMAIL PROTECTED] wrote: The references to locale are due I believe to my having installed libc6 2.5-5 from testing to run a program. It also required a different tzdata. It might have been a good idea to say that you were not running a standard system earlier. You can try to downgrade your libc. But DO NOT try to remove then reinstall it, that would (if the package manager allows it) render your system unusable. The downgrade command would be apt-get install libc6/stable tzdata/stable However if it turns out that you have other packages from testing installed as well, you might need to deal with them too. After that you can try this: update-initramfs -u -v and then see if your system can boot the 2.6.21 kernel. (Be sure to save the output of the entire transcript, just in case.) --Barak.
Re: Broadcom
Hello again, The downgrade failed, It kept saying that it could not find the older packages. Then I decided to do a fresh install of Etch, erasing the partion with Linux and reinstalling. Then I downloaded and installed the 2.6.21 kernel. On reboot it hung again at Uniforn CDROM Revision 3.20 after detecting the hard drive and the CDROM. I tried running update-initramfs -u -v here is the output: localhost:~# update-initramfs -u -v Keeping /boot/initrd.img-2.6.21-2-amd64.dpkg-bak update-initramfs: Generating /boot/initrd.img-2.6.21-2-amd64 Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/usb/host/ehci- hcd.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/usb/host/ohci- hcd.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/usb/host/uhci- hcd.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/hid/hid.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/usb/input/usbhid.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/ide/ide-core.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/scsi/scsi_mod.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/usb/storage/usb-storage .ko Adding module /lib/modules/2.6.21-2-amd64/kernel/fs/mbcache.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/fs/ext2/ext2.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/fs/jbd/jbd.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/fs/ext3/ext3.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/fs/isofs/isofs.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/fs/jfs/jfs.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/net/sunrpc/sunrpc.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/fs/nfs_common/nfs_acl.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/fs/lockd/lockd.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/fs/nfs/nfs.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/fs/reiserfs/reiserfs.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/fs/xfs/xfs.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/mii.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/3c59x.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/8139cp.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/8139too.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/8390.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/b44.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/bnx2.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/defxx.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/dl2k.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/e1000/e1000.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/e100.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/epic100.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/eql.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/fealnx.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/forcedeth.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/hp100.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/base/firmware_class.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/myri10ge/myri10ge.k o Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/natsemi.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/ne2k-pci.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/netconsole.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/ns83820.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/pcnet32.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/qla3xxx.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/r8169.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/s2io.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/sis900.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/skge.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/slhc.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/starfire.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/sundance.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/sungem_phy.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/sungem.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/sunhme.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/tg3.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/tulip/de2104x.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/tulip/de4x5.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/tulip/dmfe.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/tulip/tulip.ko Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/tulip/winbond- 840.k o Adding module /lib/modules/2.6.21-2-amd64/kernel/drivers/net/tulip/xircom_cb.ko Adding module
Re: Broadcom
hey can you tell me what the function is of wpa supplicant? No luck with 1390 card yet. Thanks On 7/5/07, Hans-J. Ullrich [EMAIL PROTECTED] wrote: Am Donnerstag 05 Juli 2007 schrieben Sie: Couple more questions :-) What would be the correct entry in /etc/network/interfaces? Also I've seen references in modconf and elsewhere to bcm43xx in connection with Broadcom. Are these modules also necessary? Thanks ill try your suggestion Cavan Hi ! Depending on your network, the entries are like a normal ethernet device. The device is as seen as ethX, were X is the number of your device, if you have more than one. You can test the name of the device with the command iwconfig. It should recognize the card and tell you the name of your device. The format of /etc/network/interfaces is well documentated in the man pages. Using google you will find a lot of examples. To verify, that eth0 is always the wired card, and eth1 is always the wlan card (or if you wish any other combination), you should take a look to /etc/udev/rules.d/z25-persistent-net.rules. In this file you can point to the devicename according to the MAC-address. The file is self explaining. The module bcm43xx is not necessary, it is the module for cards with bcm4300 chipsets. If there are more problems, just ask. Good luck ! Hans On 7/5/07, Hans-J. Ullrich [EMAIL PROTECTED] wrote: Am Donnerstag 05 Juli 2007 schrieben Sie: Hi Cavan, o.k., your wlan-card is a broadcom bcm1390, see below: this is the output of lspci: Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 10) 00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge 00:05.0 PCI bridge: ATI Technologies Inc Unknown device 5a37 00:06.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge 00:12.0 IDE interface: ATI Technologies Inc SB600 Non-Raid-5 SATA 00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0) 00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1) 00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2) 00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3) 00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4) 00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI) 00:14.0 SMBus: ATI Technologies Inc SB600 SMBus (rev 13) 00:14.1 IDE interface: ATI Technologies Inc SB600 IDE 00:14.2 Audio device: ATI Technologies Inc SB600 Azalia 00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge 00:14.4 PCI bridge: ATI Technologies Inc SB600 PCI to PCI Bridge 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTra nsport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Con troller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscella neous Control 01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200 M] snip -- 05:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PC I Card (rev 01) This describes your chipset. -- 08:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) 08:01.0 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSP ro Host Adapter (rev 19) 08:01.1 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 01) Any ideas? This chipset is natively supported by the kernel-module ipw2200, which is already in the kernel or can be installed as kernel-module with module-assistant. With the kernel-module installed and the correct entry in /etc/network/interfaces it should work. If not, you will find some description regarding to ipw2200, which is welkl known. Good luck ! Hans On 7/4/07, Hans-J. Ullrich [EMAIL PROTECTED] wrote: Am Mittwoch 04 Juli 2007 schrieb Gnu_Raiz: On Wednesday 04 July 2007, Hans-J. Ullrich wrote: Am Mittwoch 04 Juli 2007 schrieb Cavan Mejias: Has anybody had success changing the supplied broadcom wireless card in a Dell 1501 for another brand? The driver supplied in Etch doesn't work and i cant get Nidis wrapper to function yet. Thanks Which chipset ??? Check with lspci. Regards Hans When you mean supplied what exactly do you mean, a mini-pci card, or another card. I have had lots of success changing out the mini-pci card on a Dell 600M, it even has it's own antenna you just unscrew the cover and carefully remove the card. Of course these are all Intel based wifi cards, I changed out the 802.11b Intel card for a 802.11g card that would work better with my mimo AP. http://www.intel.com/network/connectivity/products/wireless/prowireless_m ob
Re: Broadcom
Thanks ill try this! Cavan On 7/7/07, Barak A. Pearlmutter [EMAIL PROTECTED] wrote: I have a shiny new Dell Inspiron 1501 running Debian amd64 stable. The easy way to make the Broadcom WiFi stuff work is: (a) You need a newer kernel than the 2.6.18 in stable, so echo deb http://www.backports.org/debian etch-backports main /etc/apt/sources.list apt-get update apt-get install linux-image-amd64/etch-backports This kernel includes a reverse-engineered free driver, bcm43xx, which should load automatically at boot time. (b) Unfortunately the free (as in speech) driver needs a proprietary firmware image to initialize the device. This needs to be fetched. The distasteful process is, however, automated. Make sure you have contrib in the sources.list line for the main Debian mirror, then go apt-get install bcm43xx-fwcutter this will download material from broadcom and extract the actual firmware into a bunch of files in /lib/firmware/. If it doesn't, invoke dpkg-reconfigure bcm43xx-fwcutter and answer y when it asks if it should download the firmware. Or if that doesn't work, read /usr/share/doc/bcm43xx-fwcutter/README.Debian (c) Reboot into your new = 2.6.21 kernel. Everything should work (d) ... except that the wireless interface will stop working upon resumption from hibernation because the firmware needs to be reloaded. Fix by adding two lines to /etc/hibernate/common.conf UnloadModules bcm43xx and DownInterfaces eth1 If you have a problem, be sure you're booting into the newer kernel and do dmesg|less and search for bcm. It should have cheerful messages about 4 cores and firmware revision and radio off and stuff like that, rather than sad messages about not loading firmware. Also when you invoke iwconfig eth1 it should look all happy. -- Barak A. Pearlmutter Hamilton Institute Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland http://www.bcl.hamilton.ie/~barak/
Re: Broadcom
I have a shiny new Dell Inspiron 1501 running Debian amd64 stable. The easy way to make the Broadcom WiFi stuff work is: (a) You need a newer kernel than the 2.6.18 in stable, so echo deb http://www.backports.org/debian etch-backports main /etc/apt/sources.list apt-get update apt-get install linux-image-amd64/etch-backports This kernel includes a reverse-engineered free driver, bcm43xx, which should load automatically at boot time. (b) Unfortunately the free (as in speech) driver needs a proprietary firmware image to initialize the device. This needs to be fetched. The distasteful process is, however, automated. Make sure you have contrib in the sources.list line for the main Debian mirror, then go apt-get install bcm43xx-fwcutter this will download material from broadcom and extract the actual firmware into a bunch of files in /lib/firmware/. If it doesn't, invoke dpkg-reconfigure bcm43xx-fwcutter and answer y when it asks if it should download the firmware. Or if that doesn't work, read /usr/share/doc/bcm43xx-fwcutter/README.Debian (c) Reboot into your new = 2.6.21 kernel. Everything should work (d) ... except that the wireless interface will stop working upon resumption from hibernation because the firmware needs to be reloaded. Fix by adding two lines to /etc/hibernate/common.conf UnloadModules bcm43xx and DownInterfaces eth1 If you have a problem, be sure you're booting into the newer kernel and do dmesg|less and search for bcm. It should have cheerful messages about 4 cores and firmware revision and radio off and stuff like that, rather than sad messages about not loading firmware. Also when you invoke iwconfig eth1 it should look all happy. -- Barak A. Pearlmutter Hamilton Institute Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland http://www.bcl.hamilton.ie/~barak/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom
Dear Barak, should uname -r after reboot show: 2.6.18-4-amd64? thats what i get. Also iwconfig gives: localhost:~# iwconfig lono wireless extensions. eth0 no wireless extensions. Also lspci gives: 05:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card (rev 01) 08:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) the install went ok, i think. Any ideas? Sincerely, Cavan On 7/7/07, Barak A. Pearlmutter [EMAIL PROTECTED] wrote: That echo command is just to add the given text to the end of the file. You can do it with a text editor instead, or in synaptic menu Settings - Repositories - Add. After it is added, you can use some other package installation thing, like synaptic, to find install the package linux-image-amd64 from the etch-backports repository. In synaptic, once you find the package, if you look in the Versions tab you'll see that there are multiple versions available. It will default to the version in stable so you need to force the version. When you view the available version in synaptic, it should give you a little blurb telling you how to force a non-default version. Enjoy, --Barak.
Re: Broadcom
Dear Barak, should uname -r after reboot show: 2.6.18-4-amd64? thats No. You should be running 2.6.21, although 2.6.18 should still be available. Check in the directory /boot to be sure the 2.6.21 kernel is installed. (a) If not, try again using the command line: apt-get install linux-image-amd64/etch-backports (b) If it was, then for some reason the system booted into the incorrect available kernel. Assuming you are using grub, which by default you will be, when the machine boots up you have a brief window to choose which kernel of the available kernels it will use. --Barak. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom
Ok im using Grub. Ill give it a try. Cavan On 7/7/07, Barak A. Pearlmutter [EMAIL PROTECTED] wrote: Dear Barak, should uname -r after reboot show: 2.6.18-4-amd64? thats No. You should be running 2.6.21, although 2.6.18 should still be available. Check in the directory /boot to be sure the 2.6.21 kernel is installed. (a) If not, try again using the command line: apt-get install linux-image-amd64/etch-backports (b) If it was, then for some reason the system booted into the incorrect available kernel. Assuming you are using grub, which by default you will be, when the machine boots up you have a brief window to choose which kernel of the available kernels it will use. --Barak.
Re: Broadcom
hey, when i repeat the operation now i get the following: debian:~# apt-get upgrade linux-image-amd64/etch-backports Reading package lists... Done Building dependency tree... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. debian:~# apt-get install linux-image-amd64/etch-backports Reading package lists... Done Building dependency tree... Done Selected version 2.6.21+8~bpo.1 (Backports.org archive:etch-backports) for linux-image-amd64 linux-image-amd64 is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. But when i check /boot all i see is a deb package: initrd.img-2.6.18-4-amd64, vmlinuz-2.6.18-4-amd64, a text file config-2.6.18-4-amd64 and System.map-2.6.18-4-amd64. i assume removing anything would cause a crash right? Can config be edited? uname -r still gives 2.6.18-4-amd64. Grub just offers a choice of single user mode and regular login both with the old kernel. Can the kernel be downloaded in an ordinary manner? Sorry for bugging you all this time. thanks very much for the help. Sincerely, Cavan On 7/7/07, Cavan Mejias [EMAIL PROTECTED] wrote: Ok im using Grub. Ill give it a try. Cavan On 7/7/07, Barak A. Pearlmutter [EMAIL PROTECTED] wrote: Dear Barak, should uname -r after reboot show: 2.6.18-4-amd64? thats No. You should be running 2.6.21, although 2.6.18 should still be available. Check in the directory /boot to be sure the 2.6.21 kernel is installed. (a) If not, try again using the command line: apt-get install linux-image-amd64/etch-backports (b) If it was, then for some reason the system booted into the incorrect available kernel. Assuming you are using grub, which by default you will be, when the machine boots up you have a brief window to choose which kernel of the available kernels it will use. --Barak.
Re: Broadcom
i assume removing anything would cause a crash right? Can config be
edited?
You are correct: it would be a bad idea to remove the 2.6.18 kernel
without first installing a different one, and it does no harm to have
multiple old kernels available. So don't try to do that. Editing the
kernel config file would do nothing; that file is actually just
documentation.
Anyway I tried to be a little too clever by half. This should fix the
problem:
apt-get install linux-image{,-2.6,-2.6.21-2}-amd64/etch-backports
This explicitly installs the correct kernel package, instead of trying
to let version dependencies pull in the right one.
--Barak.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom
I got to download the kernel image (18MB) but maybe it got
corrupted during the download or there was an error during the installation.
Grub shows 2 kernel editions and I chose the newer one, but the boot process
halts after detecting the hard drive(Hitachi) or the dvd drive(TSST Corp). I
tried moving the drives around in the bios. I just see a command prompt
blinking away. Can I use apt-get to remove the new kernel? Or Synaptic? Or
can I reinstall the downloaded package? The old kernel boots ok and there
are 2 kernels in /boot.
Cavan
On 7/7/07, Barak A. Pearlmutter [EMAIL PROTECTED] wrote:
i assume removing anything would cause a crash right? Can config be
edited?
You are correct: it would be a bad idea to remove the 2.6.18 kernel
without first installing a different one, and it does no harm to have
multiple old kernels available. So don't try to do that. Editing the
kernel config file would do nothing; that file is actually just
documentation.
Anyway I tried to be a little too clever by half. This should fix the
problem:
apt-get install linux-image{,-2.6,-2.6.21-2}-amd64/etch-backports
This explicitly installs the correct kernel package, instead of trying
to let version dependencies pull in the right one.
--Barak.
Re: Broadcom
If the installation had a problem then you could try this: dpkg --configure --pending dpkg-reconfigure linux-image-2.6.21-2-amd64 (The first line is just for safety, probably won't do anything.) Save the transcript and send it if you still can't boot that kernel. --Barak. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom
No luck with new install. Hangs at the same spot. Here's the output: debian:/home/cavan# dpkg --configure --pending debian:/home/cavan# dpkg-reconfigure linux-image-2.6.21-2-amd64 perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = en_US.UTF-8 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = en_US.UTF-8 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = en_US.UTF-8 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = en_US.UTF-8 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). Running depmod. Finding valid ramdisk creators. Using mkinitramfs-kpkg to build the ramdisk. Not updating initrd symbolic links since we are being updated/reinstalled (2.6.21-5~bpo.1 was configured last, according to dpkg) Not updating image symbolic links since we are being updated/reinstalled (2.6.21-5~bpo.1 was configured last, according to dpkg) Running postinst hook script /sbin/update-grub. You shouldn't call /sbin/update-grub. Please call /usr/sbin/update-grub instead! Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /boot/vmlinuz-2.6.21-2-amd64 Found kernel: /boot/vmlinuz-2.6.18-4-amd64 Updating /boot/grub/menu.lst ... done The references to locale are due I believe to my having installed libc6 2.5-5 from testing to run a program. It also required a different tzdata. I dont think the program is installed any more. However can I remove libc6 2.5-5 safely and install the earlier libc6 2.3.6 since so many programs depend on it (like open office and acpi)? I dont mean that exact version 2.5-5, but the library generally. If that is affecting the install? It does look like that might be the problem. Sincerely Cavan On 07/07/07, Barak A. Pearlmutter [EMAIL PROTECTED] wrote: If the installation had a problem then you could try this: dpkg --configure --pending dpkg-reconfigure linux-image-2.6.21-2-amd64 (The first line is just for safety, probably won't do anything.) Save the transcript and send it if you still can't boot that kernel. --Barak.
Re: Broadcom
this is the output of lspci: Host bridge: ATI Technologies Inc RS480 Host Bridge (rev 10) 00:01.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge 00:05.0 PCI bridge: ATI Technologies Inc Unknown device 5a37 00:06.0 PCI bridge: ATI Technologies Inc RS480 PCI Bridge 00:12.0 IDE interface: ATI Technologies Inc SB600 Non-Raid-5 SATA 00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0) 00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1) 00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2) 00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3) 00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4) 00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI) 00:14.0 SMBus: ATI Technologies Inc SB600 SMBus (rev 13) 00:14.1 IDE interface: ATI Technologies Inc SB600 IDE 00:14.2 Audio device: ATI Technologies Inc SB600 Azalia 00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge 00:14.4 PCI bridge: ATI Technologies Inc SB600 PCI to PCI Bridge 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTra nsport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Con troller 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscella neous Control 01:05.0 VGA compatible controller: ATI Technologies Inc RS482 [Radeon Xpress 200 M] 05:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN Mini-PC I Card (rev 01) 08:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02) 08:01.0 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSP ro Host Adapter (rev 19) 08:01.1 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 01) Any ideas? On 7/4/07, Hans-J. Ullrich [EMAIL PROTECTED] wrote: Am Mittwoch 04 Juli 2007 schrieb Gnu_Raiz: On Wednesday 04 July 2007, Hans-J. Ullrich wrote: Am Mittwoch 04 Juli 2007 schrieb Cavan Mejias: Has anybody had success changing the supplied broadcom wireless card in a Dell 1501 for another brand? The driver supplied in Etch doesn't work and i cant get Nidis wrapper to function yet. Thanks Which chipset ??? Check with lspci. Regards Hans When you mean supplied what exactly do you mean, a mini-pci card, or another card. I have had lots of success changing out the mini-pci card on a Dell 600M, it even has it's own antenna you just unscrew the cover and carefully remove the card. Of course these are all Intel based wifi cards, I changed out the 802.11b Intel card for a 802.11g card that would work better with my mimo AP. http://www.intel.com/network/connectivity/products/wireless/prowireless_mob ile.htm Now Gnu/linux support might not be exactly what you want, but they might be better than a broadcom chipset. What I would do is go buy yourself a usb ralink card, I have one based on the rt71 chipset, not only is it great under Debian, it is portable. http://3btech.net/chrart80wius.html I usually get good reception as the card hangs out of the usb port, for the price it seems to be a good deal compared to some windows only card. Gnu_Raiz No, what I mean is: What chipset has your card ? Broadcom is just the manufacturer. Some broacom cards are native supported by the kernel. You have to find out, which chipset your broadcom card has. Otherwise, I cannot help you. regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom
Am Mittwoch 04 Juli 2007 schrieb Cavan Mejias: Has anybody had success changing the supplied broadcom wireless card in a Dell 1501 for another brand? The driver supplied in Etch doesn't work and i cant get Nidis wrapper to function yet. Thanks Which chipset ??? Check with lspci. Regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom
On Wednesday 04 July 2007, Hans-J. Ullrich wrote: Am Mittwoch 04 Juli 2007 schrieb Cavan Mejias: Has anybody had success changing the supplied broadcom wireless card in a Dell 1501 for another brand? The driver supplied in Etch doesn't work and i cant get Nidis wrapper to function yet. Thanks Which chipset ??? Check with lspci. Regards Hans When you mean supplied what exactly do you mean, a mini-pci card, or another card. I have had lots of success changing out the mini-pci card on a Dell 600M, it even has it's own antenna you just unscrew the cover and carefully remove the card. Of course these are all Intel based wifi cards, I changed out the 802.11b Intel card for a 802.11g card that would work better with my mimo AP. http://www.intel.com/network/connectivity/products/wireless/prowireless_mobile.htm Now Gnu/linux support might not be exactly what you want, but they might be better than a broadcom chipset. What I would do is go buy yourself a usb ralink card, I have one based on the rt71 chipset, not only is it great under Debian, it is portable. http://3btech.net/chrart80wius.html I usually get good reception as the card hangs out of the usb port, for the price it seems to be a good deal compared to some windows only card. Gnu_Raiz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom
Am Mittwoch 04 Juli 2007 schrieb Gnu_Raiz: On Wednesday 04 July 2007, Hans-J. Ullrich wrote: Am Mittwoch 04 Juli 2007 schrieb Cavan Mejias: Has anybody had success changing the supplied broadcom wireless card in a Dell 1501 for another brand? The driver supplied in Etch doesn't work and i cant get Nidis wrapper to function yet. Thanks Which chipset ??? Check with lspci. Regards Hans When you mean supplied what exactly do you mean, a mini-pci card, or another card. I have had lots of success changing out the mini-pci card on a Dell 600M, it even has it's own antenna you just unscrew the cover and carefully remove the card. Of course these are all Intel based wifi cards, I changed out the 802.11b Intel card for a 802.11g card that would work better with my mimo AP. http://www.intel.com/network/connectivity/products/wireless/prowireless_mob ile.htm Now Gnu/linux support might not be exactly what you want, but they might be better than a broadcom chipset. What I would do is go buy yourself a usb ralink card, I have one based on the rt71 chipset, not only is it great under Debian, it is portable. http://3btech.net/chrart80wius.html I usually get good reception as the card hangs out of the usb port, for the price it seems to be a good deal compared to some windows only card. Gnu_Raiz No, what I mean is: What chipset has your card ? Broadcom is just the manufacturer. Some broacom cards are native supported by the kernel. You have to find out, which chipset your broadcom card has. Otherwise, I cannot help you. regards Hans -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom/Serverworks chipsets (was Re: a few simple questions about AMD64 version of Debian)
On Thu, Dec 21, 2006 at 09:14:07AM -0800, Freddie Cash wrote:
Has someone experience with k8 Broadcom/Serverworks chips?
Excellent question. I'd be interested in hearing from people that
have used/tried motherboards using this chipset. It appears to be
the only other choice in server boards if once avoids nForce boards.
You're supposedly talking about HT1000 and the like? SuperMicro's H8SSL
motherboard series is based on this chipset, and there's a 640+ node
cluster based on this board at U Wisconsin Milwaukee (and soon here
too). What do you want to know?
Yes, the HT1000 and similar ServerWords chipsets. These are the only
other non-nForce server chipsets out there (other than Intel, but we
prefer Opterons to Xeons).
How's the Linux support, Debian specifically? We're using Tyan boards for
For Linux support, look at http://lsc-group.phys.uwm.edu and proceed to
the Nemo cluster. They have set up quite a lot of documentation.
While Nemo is running FC4, we @AEI decided to install Debian (Etch) onto
our cluster which is still in an early test phase (only about 1/8 of the
hardware being delivered). Basically, if you build your own kernels (we had
to to have support for Areca RAID controllers, and the Gilgal eth chip on
one of the headnodes [purchased separately]) you're fine. We've been using
FAI to diagnose and install three different types of hardware, and it went
smoothly (OK, three years of FAI experience before...)
all our servers, but have been notified that the S2882 boards we love may
be phased out in 2007, so we're looking for possible replacements. Are
Everything that works will soon be end-of-life.
all the onboard devices detected and usable? Starting with which version
of the kernel? Specifically, the NICs. Also, how is the hardware
management (SMBus, I2C, temperature monitoring, etc)? Is there remote
management (inband or out-of-band) available for the motherboard?
NICs are tg3, kernel 2.6.17 has recent drivers.
For health monitoring, we use IPMI (which conflicts with lm_sensors).
Also IPMI can do remote power on/off/whatever, serial-over-LAN etc.
And, finally, does all of the above work with the 64-bit version of
Debian?
We never tried i386 :-)
S
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom/Serverworks chipsets (was Re: a few simple questions about AMD64 version of Debian)
On Wed, Dec 20, 2006 at 01:47:51PM -0800, Freddie Cash wrote:
On Wednesday 20 December 2006 12:44 pm, Marco Maske wrote:
Has someone experience with k8 Broadcom/Serverworks chips?
Excellent question. I'd be interested in hearing from people that have
used/tried motherboards using this chipset. It appears to be the only
other choice in server boards if once avoids nForce boards.
You're supposedly talking about HT1000 and the like? SuperMicro's H8SSL
motherboard series is based on this chipset, and there's a 640+ node cluster
based on this board at U Wisconsin Milwaukee (and soon here too).
What do you want to know?
S
--
Steffen Grunewald * MPI Grav.Phys.(AEI) * Am Mühlenberg 1, D-14476 Potsdam
Cluster Admin * http://pandora.aei.mpg.de/merlin/ * http://www.aei.mpg.de/
* e-mail: steffen.grunewald(*)aei.mpg.de * +49-331-567-{fon:7233,fax:7298}
No Word/PPT mails - http://www.gnu.org/philosophy/no-word-attachments.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom/Serverworks chipsets (was Re: a few simple questions about AMD64 version of Debian)
On Wed, Dec 20, 2006 at 01:47:51PM -0800, Freddie Cash wrote: Has someone experience with k8 Broadcom/Serverworks chips? Excellent question. I'd be interested in hearing from people that have used/tried motherboards using this chipset. It appears to be the only other choice in server boards if once avoids nForce boards. I'm running a K8SSA (S3870), it is completely supported by the kernel but it is not as stable as I hoped. There are occasional lockups that appear to be related to the (s)ata controller (still running 2.6.16.x) I specifically got this board for it's legacy PCI slots, but not all PCI cards will work (can't get firewire or cardbus to work). I have no idea if that is a kernel problem (most likely for the cardbus controller) or with the systemboard (IOMMU related I guess). The TARO/SAS expansion is kind of supported since 2.6.19, but the rc releases didn't have support for SATA on the SAS controller (AIC9140). I hoped to use this relatively cheap controller to drive lots of disks. -- When you do things right, people won't be sure you've done anything at all. Daniel Tryba -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom/Serverworks chipsets (was Re: a few simple questions about AMD64 version of Debian)
On Thursday 21 December 2006 03:37 am, Steffen Grunewald wrote: On Wed, Dec 20, 2006 at 01:47:51PM -0800, Freddie Cash wrote: On Wednesday 20 December 2006 12:44 pm, Marco Maske wrote: Has someone experience with k8 Broadcom/Serverworks chips? Excellent question. I'd be interested in hearing from people that have used/tried motherboards using this chipset. It appears to be the only other choice in server boards if once avoids nForce boards. You're supposedly talking about HT1000 and the like? SuperMicro's H8SSL motherboard series is based on this chipset, and there's a 640+ node cluster based on this board at U Wisconsin Milwaukee (and soon here too). What do you want to know? Yes, the HT1000 and similar ServerWords chipsets. These are the only other non-nForce server chipsets out there (other than Intel, but we prefer Opterons to Xeons). How's the Linux support, Debian specifically? We're using Tyan boards for all our servers, but have been notified that the S2882 boards we love may be phased out in 2007, so we're looking for possible replacements. Are all the onboard devices detected and usable? Starting with which version of the kernel? Specifically, the NICs. Also, how is the hardware management (SMBus, I2C, temperature monitoring, etc)? Is there remote management (inband or out-of-band) available for the motherboard? And, finally, does all of the above work with the 64-bit version of Debian? -- Freddie Cash, LPIC-2 CCNT CCLP Network Support Technician School District 73 (250) 377-HELP [377-4357] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom bcm43xx problems
- How can I force to use eth0 for the wlan-card, and eth1 for the hardwired-card ? I use udev, so sometimes theezh0 and eth1 changes at starting. Hardwired shall have a fixed IP, wlan shall get the ip with dhcp. i think something like this was discussed earlier... this won't allow you to have it eth0 and eth1, however this shouldn't matter: http://www.debianhelp.co.uk/udev.htm regards, -- Lubos [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Broadcom bcm43xx problems
On Fri, 2006-02-24 at 17:02 +0100, Hans wrote: Hello all, I am looking for two solutions with wireless cards. I have a Broadcom bcm4318 and a realtek rtl8169. - How can I force to use eth0 for the wlan-card, and eth1 for the hardwired-card ? I use udev, so sometimes theezh0 and eth1 changes at starting. Hardwired shall have a fixed IP, wlan shall get the ip with dhcp. Use ifrename for resolve your problem! - How can I force to use 11MBit on the wlan-card. The wlan-card originally always is using 54MBit. This my entry in /etc/network/interfaces, but this does not work: # The primary network interface auto eth0 eth1 iface eth0 inet dhcp wireless-essid myssid wireless-channel 6 wireless-key X wireless-mode managed wireless-rate 11M--- This should change the rate iface eth1 inet static address xxx.xxx.xxx.y netmask yyy.yyy.yyy.z network xxx.xxx.xxx.0 broadcast xxx.xxx.xxx.255 gateway xxx.xxx.xxx.x Best regards Hans -- .''`. ** Debian GNU/Linux ** | Francesco Cecconi ' |BrAnD| ' : :' : The Universal O.S.| [EMAIL PROTECTED] `. `'` | GPG Key ID: 11F6E468 `-| JID [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
