Re: [Cooker] Mdk 9.0 Recompiling Kernel for Athlon
Serge Pluess wrote: Hi there today I thought I would look into recompiling the kernel. First thing I wanted to try is to just change the processor type to Athlon (Got a 1Ghz Athlon Thunderbird). I have an 1.3 Ghz Athlon Duron and the kernel compiles without any problems. Works great. The commands I issued were: make dep make clean bzImage modules make modules_install install The only difference is in the make clean. Good luck. William
[Cooker] Wireless and MDK 9 (repeat post)
I'm using a Netgear MA301 with MA401 on a desktop (that is the card with a PCMCIA-PCI adapter). With beta 4 everything worked perfectly (autodetected and working). Since RC3 (I skipped RC1 and RC2) though, it doesn't work anymore (except during installation where the card is detected, the network is brought up, traffic is generated to check for updates, etc.). After installation, nothing works anymore. Below is the output from the various commands/programs I ran while trying to figure this out: HardDrake: Vendor: Netgear Bus: PCI Identification bus: 1385:4100 Location on the bus: 0:8:0 Description: 802.11b Wireless Adapter (MA301) Module: orinoco_plx Media class: NETWORK_OTHER I noticed that there is no mention of the MA401 PCMCIA adapter card. dmesg: eth0: Station identity 001f:0003::0008 eth0: Looks like an Intersil firmware version 0.08 eth0: Ad-hoc demo mode supported eth0: IEEE standard IBSS ad-hoc mode supported eth0: WEP supported, 104-bit key eth0: MAC address XX:XX:XX:XX:XX:XX eth0: Station name "Prism I" eth0: ready eth0: error -5 reading info frame. Frame dropped. iwconfig: eth0IEEE 802.11-DS ESSID:"Wireless" Nickname:"home-william.themannfam.com" Mode:Managed Frequency:2.422GHz Access Point: 00:00:00:00:00:00 Bit Rate:11Mb/s Tx-Power=15 dBm Sensitivity:1/3 Retry min limit:8 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0/92 Signal level:134/153 Noise level:134/153 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Obviously something changed between beta 4 and release regarding wireless management. My other desktop still has beta 4 and the wireless is working flawlessly. I installed the release version on my laptop (no PCI-PCMCIA adapter) and everything worked perfectly so it seems to be a problem with the PCMCIA adapter card. I just don't understand why it works during install but doesn't afterwards. Any help would be appreciated. Thanks. William
Re: [Cooker] LM 9.0 Final Impressions!
Mario Vazquez wrote: > 1) Supermount is very buggy. While it was broken in some betas/RC, I > found that RC3 supermount work very well, but Final 9.0 simply forgot > that a CD is inserted after 1 or 2 minutes after CD insertion. I have > to eject and reinsert the CD to access its data again. I only have > time to install one or two RPM's at a time before resorting to this > "workaround" . I found the same problem although in my case doing an ls on the mount point I get lots of error messages about files not being found (the name is shown however) while some files are still accessible. Ejecting and reinserting the CD fixes it (for another few minutes). I have to copy programs to install to the hard drive. William
[Cooker] Broken Wireless
I'm using a Netgear MA301 with MA401 on a desktop (that is the card with a PCMCIA-PCI adapter). With beta 4 everything worked perfectly (autodetected and working). Since RC3 though, it doesn't work anymore (except during installation where the card is detected, the network is brought up, traffic is generated to check for updates, etc.). After installation, nothing works anymore. Below is the output from the various commands/programs I ran while trying to figure this out: HardDrake: Vendor: Netgear Bus: PCI Identification bus: 1385:4100 Location on the bus: 0:8:0 Descrizione: 802.11b Wireless Adapter (MA301) Modulo: orinoco_plx Media class: NETWORK_OTHER I noticed that there is no mention of the MA401 PCMCIA adapter card. dmesg: eth0: Station identity 001f:0003::0008 eth0: Looks like an Intersil firmware version 0.08 eth0: Ad-hoc demo mode supported eth0: IEEE standard IBSS ad-hoc mode supported eth0: WEP supported, 104-bit key eth0: MAC address XX:XX:XX:XX:XX:XX eth0: Station name "Prism I" eth0: ready eth0: error -5 reading info frame. Frame dropped. iwconfig: eth0IEEE 802.11-DS ESSID:"Wireless" Nickname:"home-william.themannfam.com" Mode:Managed Frequency:2.422GHz Access Point: 00:00:00:00:00:00 Bit Rate:11Mb/s Tx-Power=15 dBm Sensitivity:1/3 Retry min limit:8 RTS thr:off Fragment thr:off Encryption key:off Power Management:off Link Quality:0/92 Signal level:134/153 Noise level:134/153 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 Obviously something changed between beta 4 and release regarding wireless management. My other desktop still has beta 4 and the wireless is working flawlessly (same on my laptop). I'll be installing the release version on the laptop today just to see if the wireless card works because I think the problem has to do with the PCMCIA adapter card. I just don't understand why it works during install but doesn't afterwards. Any help would be appreciated. Thanks. William
[Cooker] Netgear Wireless Problem
I use the Netgear MA301/MA401 solution on my desktop with a Netgear access point. With MDK9 beta 4 everything worked perfectly; however, I just installed the RC3 and have noted the following: 1. During install the card is recognized and configured (Managed mode and any ESSID), the network is started for CUPS installation (I logged on to my router from another computer to check if the card was assigned an IP address and it was) and the installation terminated. 2. After reboot the wireless card can no longer be brought up. Perusing the dmesg output I have verified that the card is recognized and it's capabilities are listed. The last message is an error: "eth0: error -5 reading information frame. Frame dropped". 3. The iwconfig output shows that there is no link (0/96) but there are values for signal strength and noise levels. Obviously the installation program does something differently but I can't figure it out. Is this a configuration problem or has the wireless support (I'm using the orinoco_plx driver) been broken? William Mann
