001-centos7安装 笔记本 联想G510

2023-11-06 23:10

本文主要是介绍001-centos7安装 笔记本 联想G510,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

一.准备前提

1.联想G510AT

  用winpe进入笔记本电脑,找到一个分区,删除即可

2.使用U盘安装

  2.1.准备一个8G 的U盘,格式化ntfs。

  2.2.在window下,下载UltraISO,一般最新版即可,用户名:王涛;注册码:7C81-1689-4046-626F

  2.3.下载centos,一般下载dvd版本,即可,

  2.4.使用UltralSO装载centos,启动-》写入磁盘映像,即可

3.U盘启动

  启动电脑,进入bios,设置Legacy support,first;

  待电脑重启,进入Install Centos 后,

  按tab建,将命令修改为:>vmlinuz initrd=initrd.img linux dd quiet

  根据提示 ctrl+ X 重启,后可查看u盘系统。abd4 或者其他,修改命令:>vmlinuz initrd=initrd.img inst.stage2=hd:/dev/sdc4 quiet

4.进入系统安装界面。

  软件安装可以选择,gnone,磁盘设置swap 为内存1-2倍

  其他使用默认即可。安装完毕即可使用

二.安装网卡

1.先使用网线连接,确定网卡类型Broadcom:lspci | grep Broadcom

  确认为:BCM43142

2.使用教程

  https://elrepo.org/tiki/wl-kmod

  基础步骤【以下只是重复url内容】:  

wl-kmod
Source RPMs for Broadcom drivers
Please note: The current Broadcom closed-source Linux drivers when built according to the instructions provided here have provided functional wireless capability to some users, but have failed for other users.Broadcom Corp. provides closed-source IEEE 802.11a/b/g/n Linux drivers for use with Broadcom's BCM4311, BCM4312, BCM4313, BCM4321, BCM4322, BCM4331, BCM4352, BCM4360, BCM43142, BCM43224, BCM43225, BCM43227 and BCM43228 wireless chipsets. We (ELRepo) cannot create and redistribute binary RPMS for these drivers due to the Broadcom licensing restrictions (i.e., liability issues). However, we do make available no-source SRPMS (.nosrc.rpm) which contain the framework required to build the binaries, but lack the proprietary code and are not subject to Broadcom's licensing restrictions.These no-source SRPMS can be used by the end user to build kABI-compatible binary drivers for local use. These kABI-compatible binaries should be usable after future kernel updates, so there is no need to recompile them for each new kernel. Please note that the nosrc.rpm package does not build kmod-wl for kernel-xen and kmod-wl cannot be built on a system running kernel-xen.To build a kmod-wl binary, you will need to (1) configure a build tree, (2) download the wl-kmod*nosrc.rpm for your EL release, (3) download the closed-source tarball from Broadcom for your architecture (i.e., 32-bit vs 64-bit) into the build tree and (4) initiate the kmod-wl build. For convenience, the kernel development package for the running kernel will be used in the build process, as opposed to our normal policy of building against an older kernel development package.The kmod-wl package can be built on any system running the same EL release/architecture as the target system. If you are building on the target system and lack network connectivity, then the downloads can be made onto a USB flash drive and copied onto your system.Below are the detailed instructions on how to build the binary packages from our no-source SRPM. If you are already familiar with using rpmbuild to build packages, then this process should only take you 5-10 minutes to complete.Kmod-wl Usability Across EL Point Releases (or ″Why doesn′t my wireless work after the last point release update?″):If you are only interested in building kmod-wl for the latest kernel, then you do not really need to read this section, but it would not hurt to understand the underlying issues.The EL6 and EL7 kmod-wl binaries are typically only functional within a range of EL point releases (e.g., 6.8-6.9, 7.4) due to changes in the wireless stack-related kernel API of the EL 6 and EL 7 kernels. RHEL backports (external link) components of recent kernels so that more modern kernel features and security fixes are available to the user. These backports become most notable when a new point release becomes available.Our kmods continue to work after updating the kernel as long as the Kernel Application Binary Interface (kABI) remains unchanged with respect to our packages. EL point releases sometime break this compatibility. For the kmod-wl package, we make changes to the wl-kmod srpm to accommodate these changes. One down side is that the newly built kmod-wl only works within the newest RHEL point release after a wl-kmod srpm update. To maintain backward compatibility of the wl-kmod srpm, we craft it to build slightly different kmod-wl packages depending on the point release kernel used to build it.If your interest is to only use the newest kernel, then you can just boot to the newest kernel and follow the instructions (below) to build a usable kmod-wl. However, if you need to continue using an older kernel, then you can use the updated wl-kmod srpm to build a kmod-wl package that works with the older kernel.How to do that: If you build kmod-wl from the updated srpm after booting the latest kernel, then you can save that kmod-wl for use with the latest kernel. Likewise, you can build kmod-wl from the updated srpm after booting an older point release kernel and then save that kmod-wl for use with the older point release kernel. (For users familiar with using rpmbuild, you can also use the " --define 'kversion TARGET-KVERSION ' " option to avoid booting different kernels.) Unfortunately, you can only have one of those kmod-wl packages installed at a time, so save both kmod-wl packages, but only install one of them. Note that they have exactly the same version (i.e., their rpm names are identical), so save them in separate folders.For example, you can build kmod-wl under an EL 7.2 kernel and use it with EL 7.2 kernels, but it will not function when you boot EL 7.1 or EL 7.3 kernels. Likewise, you can build kmod-wl under an EL 7.3 kernel and use it with EL 7.3 kernels, but it will not function when you boot EL 7.1 or EL 7.2 kernels.If you need a kmod-wl package that works within one of the following ranges, then boot a kernel in that range and build/install kmod-wl as described below.Supported EL 6 Point Release Ranges: (1) 6.3 - 6.4, (2) 6.5 - 6.6, (3) 6.7, (4) 6.8 - 6.9Supported EL 7 Point Release Ranges: (1) 7.0, (2) 7.1, (3) 7.2, (4) 7.3, (5) 7.4Build and install kmod-wl for EL6/7Please note:If your current kmod-wl package works with an older kernel and wireless networking is your only Internet access method,then boot the older kernel and download the new srpm and Broadcom source before proceeding.1) Install needed tools/packages:1a) EL6:# yum groupinstall 'Development Tools'# yum install redhat-lsb kernel-abi-whitelists# yum install kernel-devel-$(uname -r)EL 6.4 - 6.6 Note: Due to a bug in redhat-rpm-config-9.0.3-42.el6, a modification is required to fix thekabi-whitelist target in /usr/lib/rpm/redhat/find-requires.ksyms before you build kmod-wl.Please run as root (as a single copy/paste):[[ $(rpm -q redhat-rpm-config|grep 9.0.3-42|wc -l) -gt 0 ]] && sed -i \'s@/lib/modules/kabi/kabi_whitelist@/lib/modules/kabi-current/kabi_whitelist@g' \/usr/lib/rpm/redhat/find-requires.ksymsThe above modification is not needed for EL 6.7 or later.1b) EL7:# yum group install 'Development Tools'# yum install redhat-lsb kernel-abi-whitelists# yum install kernel-devel-$(uname -r)EL 7.0 Note: Due to a bug in redhat-rpm-config-9.1.0-63.el7, a modification is required to fix thekabi-whitelist target in /usr/lib/rpm/redhat/find-requires.ksyms before you build kmod-wl.Please run as root (as a single copy/paste):[[ $(rpm -q redhat-rpm-config|grep 9.1.0-63|wc -l) -gt 0 ]] && sed -i \'s@/lib/modules/kabi/kabi_whitelist@/lib/modules/kabi-rhel70/kabi_whitelist@g' \/usr/lib/rpm/redhat/find-requires.ksymsThe above modification is not needed for EL 7.1 or later.2) As a regular user (not as root), configure a build tree and minimal .rpmmacros:$ mkdir -p ~/rpmbuild/{BUILD,RPMS,SPECS,SOURCES,SRPMS}$ echo -e "%_topdir $(echo $HOME)/rpmbuild\n%dist .el$(lsb_release -s -r|cut -d"." -f1).local" >> ~/.rpmmacros3) Download wl-kmod*nosrc.rpmFor EL6: http://elrepo.org/linux/elrepo/el6/SRPMS/wl-kmod-6_30_223_271-3.el6.elrepo.nosrc.rpm (external link)For EL7: http://elrepo.org/linux/elrepo/el7/SRPMS/wl-kmod-6_30_223_271-4.el7.elrepo.nosrc.rpm (external link)4) Download the Broadcom driver matching your architecture (i.e., 32-bit vs 64-bit):from:   http://www.broadcom.com/support/802.11 (external link) (scroll down to "Linux® STA 32-bit (or 64-bit) drivers")to:      ~/rpmbuild/SOURCES/5) Build kmod-wl as a regular user (not as root):$ rpmbuild --rebuild --define 'packager <your-name>' /<path-to-nosrc.rpm>/wl-kmod*nosrc.rpm...Wrote: /home/<user>/rpmbuild/RPMS/x86_64/kmod-wl-<version>.x86_64.rpm...+ exit 06) If ndiswrapper is installed and is no longer needed, then remove it:# yum remove \*ndiswrapper\*7) Install kmod-wl:Note for EL7: Recent hardware is often shipped with an Unified Extensible Firmware Interface (UEFI) in which Secure Boot is enabled. If you wish to continue using Secure Boot in combination with EL7/kmod-wl, then you will need to sign the kmod-wl.rpm you have created using your own private Secure Boot key and install the corresponding public key on your system as explained in Signing Kernel Modules for Secure Boot (external link). Otherwise, you can disable Secure Boot in the UEFI configuration to avoid this issue.# rpm -Uvh /path-to-rpm/kmod-wl*rpmOR# yum --nogpgcheck localinstall /path-to-rpm/kmod-wl*rpmPlease note: It is recommended, but is not critical, that you uninstall any older version of kmod-wl (i.e., rpm -e kmod-wl) before installing the new kmod-wl package.8) Reboot or to start wireless now:8a) EL6:# modprobe -r b43 b43legacy ssb wl lib80211# modprobe -r bcma (Note: needed for EL 6.4 and later)# modprobe lib80211_crypt_tkip# modprobe wl8b) EL7:# modprobe wl9) Store kmod-wl*rpm for safe keeping10) Optional - Remove the build tree:$ rm -rf ~/rpmbuild
View Code

安装基础包

  yum install kernel-headers kernel-devel gcc

下载驱动:http://www.broadcom.com/support/802.11/linux_sta.php

 三.切换命令行与图型化切换

  命令行:

  systemctl set-default multi-user.tartget

  图形化:

  systemctl set-default graphical.target

  reboot重启校验即可。

四.显卡驱动

  amd 安装,目前由于系统使用的是centos7。4 ,故,暂时无法安装XServer。Xserver 版本过高。。

  

转载于:https://www.cnblogs.com/bjlhx/p/7788422.html

这篇关于001-centos7安装 笔记本 联想G510的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/359613

相关文章

Zookeeper安装和配置说明

一、Zookeeper的搭建方式 Zookeeper安装方式有三种,单机模式和集群模式以及伪集群模式。 ■ 单机模式:Zookeeper只运行在一台服务器上,适合测试环境; ■ 伪集群模式:就是在一台物理机上运行多个Zookeeper 实例; ■ 集群模式:Zookeeper运行于一个集群上,适合生产环境,这个计算机集群被称为一个“集合体”(ensemble) Zookeeper通过复制来实现

CentOS7安装配置mysql5.7 tar免安装版

一、CentOS7.4系统自带mariadb # 查看系统自带的Mariadb[root@localhost~]# rpm -qa|grep mariadbmariadb-libs-5.5.44-2.el7.centos.x86_64# 卸载系统自带的Mariadb[root@localhost ~]# rpm -e --nodeps mariadb-libs-5.5.44-2.el7

Centos7安装Mongodb4

1、下载源码包 curl -O https://fastdl.mongodb.org/linux/mongodb-linux-x86_64-rhel70-4.2.1.tgz 2、解压 放到 /usr/local/ 目录下 tar -zxvf mongodb-linux-x86_64-rhel70-4.2.1.tgzmv mongodb-linux-x86_64-rhel70-4.2.1/

Centos7安装JDK1.8保姆版

工欲善其事,必先利其器。这句话同样适用于学习Java编程。在开始Java的学习旅程之前,我们必须首先配置好适合的开发环境。 通过事先准备好这些工具和配置,我们可以避免在学习过程中遇到因环境问题导致的代码异常或错误。一个稳定、高效的开发环境能够让我们更加专注于代码的学习和编写,提升学习效率,减少不必要的困扰和挫折感。因此,在学习Java之初,投入一些时间和精力来配置好开发环境是非常值得的。这将为我

安装nodejs环境

本文介绍了如何通过nvm(NodeVersionManager)安装和管理Node.js及npm的不同版本,包括下载安装脚本、检查版本并安装特定版本的方法。 1、安装nvm curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash 2、查看nvm版本 nvm --version 3、安装

计算机毕业设计 大学志愿填报系统 Java+SpringBoot+Vue 前后端分离 文档报告 代码讲解 安装调试

🍊作者:计算机编程-吉哥 🍊简介:专业从事JavaWeb程序开发,微信小程序开发,定制化项目、 源码、代码讲解、文档撰写、ppt制作。做自己喜欢的事,生活就是快乐的。 🍊心愿:点赞 👍 收藏 ⭐评论 📝 🍅 文末获取源码联系 👇🏻 精彩专栏推荐订阅 👇🏻 不然下次找不到哟~Java毕业设计项目~热门选题推荐《1000套》 目录 1.技术选型 2.开发工具 3.功能

SWAP作物生长模型安装教程、数据制备、敏感性分析、气候变化影响、R模型敏感性分析与贝叶斯优化、Fortran源代码分析、气候数据降尺度与变化影响分析

查看原文>>>全流程SWAP农业模型数据制备、敏感性分析及气候变化影响实践技术应用 SWAP模型是由荷兰瓦赫宁根大学开发的先进农作物模型,它综合考虑了土壤-水分-大气以及植被间的相互作用;是一种描述作物生长过程的一种机理性作物生长模型。它不但运用Richard方程,使其能够精确的模拟土壤中水分的运动,而且耦合了WOFOST作物模型使作物的生长描述更为科学。 本文让更多的科研人员和农业工作者

K8S(Kubernetes)开源的容器编排平台安装步骤详解

K8S(Kubernetes)是一个开源的容器编排平台,用于自动化部署、扩展和管理容器化应用程序。以下是K8S容器编排平台的安装步骤、使用方式及特点的概述: 安装步骤: 安装Docker:K8S需要基于Docker来运行容器化应用程序。首先要在所有节点上安装Docker引擎。 安装Kubernetes Master:在集群中选择一台主机作为Master节点,安装K8S的控制平面组件,如AP

衡石分析平台使用手册-单机安装及启动

单机安装及启动​ 本文讲述如何在单机环境下进行 HENGSHI SENSE 安装的操作过程。 在安装前请确认网络环境,如果是隔离环境,无法连接互联网时,请先按照 离线环境安装依赖的指导进行依赖包的安装,然后按照本文的指导继续操作。如果网络环境可以连接互联网,请直接按照本文的指导进行安装。 准备工作​ 请参考安装环境文档准备安装环境。 配置用户与安装目录。 在操作前请检查您是否有 sud

mac安装brew 与 HomeBrew

/bin/zsh -c "$(curl -fsSL https://gitee.com/cunkai/HomebrewCN/raw/master/Homebrew.sh)" curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install.sh >> brew_install BREW_REPO="