Re: Problems after a yum upgrade from F10 to F11
stan gr...@q.com writes: On Wed, 29 Jul 2009 23:28:57 +0200 lars.bjorn...@broadpark.no (Lars Bjørndal) wrote: I tried that too, without any difference - sorry. Perhaps you could try some of the other vga options - 0x312, etc. It has been years since I set this up, don't have a list of them anymore. Maybe someone else will give you a better answer. I found the key: Put 'nomodeset' at the kernel line in /etc/grub.conf. Lars -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Problems after a yum upgrade from F10 to F11
Hope someone can help me with the following two issues. I've used yum to upgrade from Fedora 10 to Fedora 11. The computer is an Lenove X61S laptop. Output from 'uname -rv' is: '2.6.29.6-213.fc11.i686.PAE #1 SMP Tue Jul 7 20:59:29 EDT 2009'. 1. Text mode I prefere to use the console, e.g. text only mode, and so I've set the system to start up in runlevel 3. Output from 'runlevel' is 'N 3'. The problem is that I get 48 lines and many more columns than the usual 80 (don't remember exactly how many). In /etc/grub.conf, I have added the vga=normal paramtere, as follows: title Fedora (2.6.29.6-213.fc11.i686.PAE) root (hd0,2) kernel /vmlinuz-2.6.29.6-213.fc11.i686.PAE ro root=/dev/vg/root0 initrd /initrd-2.6.29.6-213.fc11.i686.PAE.img vga=normal In the /var/log/messages, I see a line like this: Jul 29 12:45:03 lapx kernel: Console: colour VGA+ 80x25 Even thoug, after logging in on the console, I have too many lines and columns. Also, I can see that the environment variables LINES and COLUMNS are set to the amount of lines/columns that are displayed. What has changed from Fedora 10 to Fedora 11, that could cause this behaviour, and what can I do to fix it? 2. The wireless network will not start at boot time The wpa_supplicant service is activated, and also the network sercice. NetworkManager however, is disabled. The /etc/sysconfig/network-scripts/ifcfg-wlan0 looks like this: # Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection DEVICE=wlan0 BOOTPROTO=dhcp HWADDR=00:1f:3b:ad:eb:13 PEERDNS=yes ONBOOT=yes Anyway, the computer hangs for a long time while looking for IP information for wlan0, and the process ends with som unsuccess on ping to the dhcp's IP address. Doing 'ifup wlan0' after logging in, works. Also this issue occured after upgrading the system. What can I do to fix this problem? Regards, Lars -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Problems after a yum upgrade from F10 to F11
On Wed, 29 Jul 2009 14:56:19 +0200 lars.bjorn...@broadpark.no (Lars Bjørndal) wrote: Hope someone can help me with the following two issues. I've used yum to upgrade from Fedora 10 to Fedora 11. The computer is an Lenove X61S laptop. Output from 'uname -rv' is: '2.6.29.6-213.fc11.i686.PAE #1 SMP Tue Jul 7 20:59:29 EDT 2009'. 1. Text mode I prefere to use the console, e.g. text only mode, and so I've set the system to start up in runlevel 3. Output from 'runlevel' is 'N 3'. The problem is that I get 48 lines and many more columns than the usual 80 (don't remember exactly how many). In /etc/grub.conf, I have added the vga=normal paramtere, as follows: title Fedora (2.6.29.6-213.fc11.i686.PAE) root (hd0,2) kernel /vmlinuz-2.6.29.6-213.fc11.i686.PAE ro root=/dev/vg/root0 initrd /initrd-2.6.29.6-213.fc11.i686.PAE.img vga=normal In the /var/log/messages, I see a line like this: Jul 29 12:45:03 lapx kernel: Console: colour VGA+ 80x25 Even thoug, after logging in on the console, I have too many lines and columns. Also, I can see that the environment variables LINES and COLUMNS are set to the amount of lines/columns that are displayed. What has changed from Fedora 10 to Fedora 11, that could cause this behaviour, and what can I do to fix it? I think the vga=normal is supposed to be on the kernel line. At least that is where I always put my similar command vga=0x317, which creates a console identical to the one you don't want. :-) 2. The wireless network will not start at boot time The wpa_supplicant service is activated, and also the network sercice. NetworkManager however, is disabled. The /etc/sysconfig/network-scripts/ifcfg-wlan0 looks like this: # Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection DEVICE=wlan0 BOOTPROTO=dhcp HWADDR=00:1f:3b:ad:eb:13 PEERDNS=yes ONBOOT=yes Anyway, the computer hangs for a long time while looking for IP information for wlan0, and the process ends with som unsuccess on ping to the dhcp's IP address. Doing 'ifup wlan0' after logging in, works. Also this issue occured after upgrading the system. What can I do to fix this problem? I recall someone saying something on the list about another setting, that ONBOOT doesn't really start the network on boot, there is share network connection or some other parameter you have to set to yes. Regards, Lars -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Problems after a yum upgrade from F10 to F11
stan gr...@q.com writes: On Wed, 29 Jul 2009 14:56:19 +0200 lars.bjorn...@broadpark.no (Lars Bjørndal) wrote: Hope someone can help me with the following two issues. I've used yum to upgrade from Fedora 10 to Fedora 11. The computer is an Lenove X61S laptop. Output from 'uname -rv' is: '2.6.29.6-213.fc11.i686.PAE #1 SMP Tue Jul 7 20:59:29 EDT 2009'. 1. Text mode I prefere to use the console, e.g. text only mode, and so I've set the system to start up in runlevel 3. Output from 'runlevel' is 'N 3'. The problem is that I get 48 lines and many more columns than the usual 80 (don't remember exactly how many). In /etc/grub.conf, I have added the vga=normal paramtere, as follows: title Fedora (2.6.29.6-213.fc11.i686.PAE) root (hd0,2) kernel /vmlinuz-2.6.29.6-213.fc11.i686.PAE ro root=/dev/vg/root0 initrd /initrd-2.6.29.6-213.fc11.i686.PAE.img vga=normal In the /var/log/messages, I see a line like this: Jul 29 12:45:03 lapx kernel: Console: colour VGA+ 80x25 Even thoug, after logging in on the console, I have too many lines and columns. Also, I can see that the environment variables LINES and COLUMNS are set to the amount of lines/columns that are displayed. What has changed from Fedora 10 to Fedora 11, that could cause this behaviour, and what can I do to fix it? I think the vga=normal is supposed to be on the kernel line. At least that is where I always put my similar command vga=0x317, which creates a console identical to the one you don't want. :-) I tried that too, without any difference - sorry. 2. The wireless network will not start at boot time The wpa_supplicant service is activated, and also the network sercice. NetworkManager however, is disabled. The /etc/sysconfig/network-scripts/ifcfg-wlan0 looks like this: # Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection DEVICE=wlan0 BOOTPROTO=dhcp HWADDR=00:1f:3b:ad:eb:13 PEERDNS=yes ONBOOT=yes Anyway, the computer hangs for a long time while looking for IP information for wlan0, and the process ends with som unsuccess on ping to the dhcp's IP address. Doing 'ifup wlan0' after logging in, works. Also this issue occured after upgrading the system. What can I do to fix this problem? I recall someone saying something on the list about another setting, that ONBOOT doesn't really start the network on boot, there is share network connection or some other parameter you have to set to yes. Hmm. Do you know the exact parameter name? Let me add that I also tried without wpa_supplicant enabled, and exactly the same happened. Lars -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Problems after a yum upgrade from F10 to F11
On Wed, 29 Jul 2009 23:28:57 +0200 lars.bjorn...@broadpark.no (Lars Bjørndal) wrote: I tried that too, without any difference - sorry. Perhaps you could try some of the other vga options - 0x312, etc. It has been years since I set this up, don't have a list of them anymore. Maybe someone else will give you a better answer. Hmm. Do you know the exact parameter name? Let me add that I also tried without wpa_supplicant enabled, and exactly the same happened. No, I use network daemon for a hard wired connection, just remembered seeing this for use with NM (with exactly that amount of detail). -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Problems after a yum upgrade from F10 to F11
On 07/29/2009 06:14 PM, stan wrote: On Wed, 29 Jul 2009 23:28:57 +0200 lars.bjorn...@broadpark.no (Lars Bjørndal) wrote: I tried that too, without any difference - sorry. Perhaps you could try some of the other vga options - 0x312, etc. It has been years since I set this up, don't have a list of them anymore. Maybe someone else will give you a better answer. I'm not sure how accurate this is (some of the x24 and x32 modes aren't in the kernel's list for me in F10/F11), but there is a list of mode ids at: http://en.wikipedia.org/wiki/VESA_BIOS_Extensions -- Kevin J. Cummings kjch...@rcn.com cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us Registered Linux User #1232 (http://counter.li.org) -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Problems after a yum upgrade from F10 to F11
On Wed, 29 Jul 2009 18:56:26 -0400 Kevin J. Cummings cummi...@kjchome.homeip.net wrote: On 07/29/2009 06:14 PM, stan wrote: On Wed, 29 Jul 2009 23:28:57 +0200 lars.bjorn...@broadpark.no (Lars Bjørndal) wrote: I tried that too, without any difference - sorry. Perhaps you could try some of the other vga options - 0x312, etc. It has been years since I set this up, don't have a list of them anymore. Maybe someone else will give you a better answer. I'm not sure how accurate this is (some of the x24 and x32 modes aren't in the kernel's list for me in F10/F11), but there is a list of mode ids at: http://en.wikipedia.org/wiki/VESA_BIOS_Extensions I tried one of those and it didn't work. But that brought up a message saying I just had to hit enter to see the available modes on my machine. So try vga=795 on the kernel line (which was invalid here), and you should be able to hit enter for a list of all modes available on your machine. I saw 80x25 on my list. Because the wikipedia pages says there are no standards anymore for this, it probably depends on your hardware what is available. My guess is that normal went away as a definition (or was changed) between F10 and F11. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Problems after a yum upgrade from F10 to F11
stan wrote: I tried one of those and it didn't work. But that brought up a message saying I just had to hit enter to see the available modes on my machine. So try vga=795 on the kernel line (which was invalid here), and you should be able to hit enter for a list of all modes available on your machine. I saw 80x25 on my list. Because the wikipedia pages says there are no standards anymore for this, it probably depends on your hardware what is available. My guess is that normal went away as a definition (or was changed) between F10 and F11. Even easier - use vga=ask - it works on all systems. Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup! signature.asc Description: OpenPGP digital signature -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Problems after a yum upgrade from F10 to F11
On Wednesday 29 July 2009, Kevin J. Cummings wrote: On 07/29/2009 06:14 PM, stan wrote: On Wed, 29 Jul 2009 23:28:57 +0200 lars.bjorn...@broadpark.no (Lars Bjørndal) wrote: I tried that too, without any difference - sorry. Perhaps you could try some of the other vga options - 0x312, etc. It has been years since I set this up, don't have a list of them anymore. Maybe someone else will give you a better answer. I'm not sure how accurate this is (some of the x24 and x32 modes aren't in the kernel's list for me in F10/F11), but there is a list of mode ids at: http://en.wikipedia.org/wiki/VESA_BIOS_Extensions That is probably a complete list when it was compiled, Kevin, but many of the more recent LCD monitors operate best at 1680x1050. Perhaps that list needs updated? -- Kevin J. Cummings kjch...@rcn.com cummi...@kjchome.homeip.net cummi...@kjc386.framingham.ma.us Registered Linux User #1232 (http://counter.li.org) -- Cheers, Gene There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order. -Ed Howdershelt (Author) The NRA is offering FREE Associate memberships to anyone who wants them. https://www.nrahq.org/nrabonus/accept-membership.asp Professional certification for car people may sound like an oxymoron. -The Wall Street Journal, page B1, Tuesday, July 17, 1990. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
